> > Santiago, > To be clear, you're effectively saying that the Agent (Windows) interface is only for configuration purposes --- that an admin can config the service [sic, OSSEC ] to start the moment the user logs in, and that the object of importance is in effect, the client key that is generated by the OSSEC [server], correct?
so to configure an agentless I could do something like this (correct?):::: 1> generate key via server 2> install agent a> enter IP/key information (save config info & close agent GUI) 3> restart OSSEC (server) a> restart the service (Windows) ^ at which point admin could configure appropriate domain/login information to have service start at logon. my apologies for any confusion. :) -- --- 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.
