Yes, that is exactly how it works. I packaged it that way so that the client would not have to try to find it on the network to decrease the chances of failure. The keys file is deleted after everything has run successfully leaving a client.keys file on the machine with just the one line that particular agent needs to connect.
On Oct 25, 12:46 pm, "Jefferson, Shawn" <[email protected]> wrote: > Hi Phil, > > Thanks for posting that! Just so that I understand correctly how the > client.keys file is handled with your process: is it packaged up into the > MSI, and then there is a client side script that grabs out the proper line > for that client? Afterward the whole client.keys file is deleted, of course. > > Or, did I misunderstand? > > > > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of PhilS > Sent: October 22, 2010 11:22 PM > To: ossec-list > Subject: [ossec-list] Windows Automated Installation - Mass Deployment via > Active Directory - Part 3 > > OK, here we go, now we are getting to where all this reading, > planning, building and coding pay off. > > <snip>
