Hi Dustin. Since OSSEC is installed onto another partition, and I suppose that it won't be overwritten when you recreate the C: partition, the OSSEC settings and the key will remain unaltered.
On the other hand, we are working on a Auth version for Windows clients, so you are able to request a new key to the manager when the system boots or if you find a connection issue. Regards. Victor. On Thursday, September 29, 2016 at 7:53:26 PM UTC+2, jose wrote: > > Hi Dustin > > You can use Wazuh API and one PowerShell script. > > > http://blog.wazuh.com/automatically-deploying-ossec-to-windows-using-wazuh-api/ > > And in our documentation you have the procedure to install Wazuh RESTful > API > > http://documentation.wazuh.com/en/latest/ossec_api.html > > I hope this helps. > > Regards > ----------------------- > Jose Luis Ruiz > Wazuh Inc. > [email protected] <javascript:> > > On September 29, 2016 at 12:55:19 PM, Dustin Church ([email protected] > <javascript:>) wrote: > > Victor, > > I currently have 78 servers that will be recreated nightly using a single > image. I understand that I can install OSSEC to a secondary partition, but > how do I handle the keys for each server that is created from the image, > and ensure proper communication after the image is built without having to > manually enter the server IP and key for the server at boot time? > > On Friday, September 23, 2016 at 4:22:59 AM UTC-6, Victor Fernandez wrote: >> >> You may follow these steps: >> >> 1. Run the OSSEC installer and click "Next" until you reach the >> screen "Choose the Install Location". >> 2. Select the directory where you want to install OSSEC in (another >> disk partition). >> 3. Finish the installation steps. >> 4. At this point, OSSEC has been installed into the partition that >> you chose, but it has be also registered a service on Windows. >> 5. Now create the Windows C: drive image (which now contains the >> OSSEC agent service). >> 6. You can configure the agents independently. >> >> Kind regards. >> Victor. >> >> >> >> On Thursday, September 22, 2016 at 12:00:29 PM UTC+2, Eero Volotinen >> wrote: >>> >>> How about modifying the installation package? >>> >>> Eero >>> >>> 2016-09-22 12:56 GMT+03:00 Victor Fernandez <[email protected]>: >>> >>>> Hi, >>>> >>>> when you run the OSSEC installer for Windows, you can choose the >>>> location where OSSEC will be installed. This shouldn't be a problem. >>>> >>>> Since OSSEC registers a background service on Windows, you should first >>>> install OSSEC into another partition and then create the C:\ drive image. >>>> >>>> Hope it helps. >>>> Best regards. >>>> >>>> Victor. >>>> >>>> >>>> >>>> On Thursday, September 22, 2016 at 10:13:30 AM UTC+2, vikas wrote: >>>>> >>>>> Hello all, >>>>> >>>>> We have a group of servers where the C:/ drive gets re-imaged daily >>>>> with a standard image. Since its going to be same image that all the >>>>> servers use, not sure how to make OSSEC part of that image and avoid >>>>> agent-server registration issues. So we wanted to install it on a >>>>> different >>>>> drive to avoid the complications, but couldn't find an option to specify >>>>> custom path for installation. Is it possible? >>>>> >>>>> Thank you for your help! >>>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "ossec-list" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
