Scott, That's not very explicit in the documentation. You can refer to the following links: http://www.ossec.net/doc/programs/ossec-authd.html#ossec-authd http://www.ossec.net/doc/programs/agent-auth.html
You need to have the ossec-authd daemon running on your server first. Once it is setup, you can register your clients with agent-auth. Be aware you will have to install openssl-devel before the compilation of your server/client. Without it, you will get an error message like wan't compile with SSL. -Stephane Rossan On 8/11/11 11:49 AM, "ScottyMace" <[email protected]> wrote: >Cool, were is that documented? Can't seem to find any info on it. > >On Aug 11, 12:48 pm, Stephane Rossan <[email protected]> wrote: >> Ossec 2.6 comes with an auto-registration mechanism. I tested it with >> Linux systems, works great. >> However, I have no idea with windows client. >> >> On 8/11/11 8:54 AM, "ScottyMace" <[email protected]> wrote: >> >> >> >> >> >> >> >> >Any ideas on bulk deployment and the issues with key management? 3 >> >scenarios: >> >1. 1500+ servers of a mix of physical and virtual, Windows server, >> >various Linux distros, and AIX. >> >2. 200 workstations, mix of XP and 7 (32 and 64 bit) that are our >> >employees machines >> >3. 200+ WinXP, Win7 lab machines that get re-imaged after being used >> >for several week at a time. Imaging is not done all at the same time, >> >usually a few here, a few there from a common image. >> >> >Obviously having to manage the keys and hosts within the manage_agents >> >applet is going to take forever, not to mention the keys on the agents >> >themselves on the individual boxes. >
