Thanks, I will give it another try. I was using the scripts provided in the Windows Automated Installation document and the information is not being imported into the agent properly. Will review the script and the test system to see if I can find where the problem may be.
Thanks for your help and the quick response. Karl From: "dan (ddp)" <[email protected]> To: [email protected] Date: 03/15/2012 09:59 AM Subject: Re: [ossec-list] Exporting Encryption Keys Sent by: [email protected] The exported key is encoded (base64?), the client.keys entries are raw. If you look at the keys file on a configured agent it will look more like the client.keys entries than the exported version. On Thu, Mar 15, 2012 at 9:55 AM, <[email protected]> wrote: > > If I open the client.keys files it shows me the ID Name IP address Key, > but the key listed is much different than the key that is exported via the > command line. Are you saying that I should just drop the client.keys file on > each system? > > > Karl > > > Daniel Cid ---03/15/2012 09:43:08 AM---Hi Karl, The keys are just simple > text files inside client.keys. You just need > > From: Daniel Cid <[email protected]> > To: [email protected] > Date: 03/15/2012 09:43 AM > Subject: Re: [ossec-list] Exporting Encryption Keys > Sent by: [email protected] > > ________________________________ > > > > Hi Karl, > > The keys are just simple text files inside client.keys. You just need > one of each file for each > agent, which you can mass deploy via AD... That would be the simplest > approach. > > thanks, > > -- > Daniel B. Cid > http://dcid.me > > On Wed, Mar 14, 2012 at 6:38 PM, <[email protected]> wrote: > > I am need to do a mass deployment of the OSSEC agent to Windows systems. > > I > > have followed the instructions in the Windows Installation Mass > > Deployment > > via Active Directory, the problem I am having is that it is not > > installing > > the encryption key for the system when I run the .msi installer. Is > > there a > > script that can dump all the encryption keys or is there another way to > > get > > the keys out of the OSSEC server? I can manually pull them out one by > > one > > but with over 500 systems I would rather not. Running the latest version > > of > > OSSEC with the 2.6 agent. > > > > Thanks for any help on this one. > > > > Karl > > > > The information transmitted is intended only for the person or entity to > > which it is addressed and may contain confidential and/or privileged > > material. Any review, retransmission, dissemination or other use of, or > > taking of any action in reliance upon this information by persons or > > entities other than the intended recipient is prohibited. If you > > received > > this in error, please contact the sender and destroy any copies of this > > document. > > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and destroy any copies of this > document. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this document.
<<inline: graycol.gif>>
