pburger01

Owen, I have had limited success in deploying ESET to View Desktops. I had to DNS poison the master image so that when it tries to check in for a GUID it could not get one. Gave it a DNS entry for our management server of 127.0.0.1 in the hosts file Installed the ESET agent. Installed the ESET AV client Installed I turned off the agent service (did not disable or change the startup state in anyway) Removed the DNS poison and, with the ERA service still stopped. we turned off the image and prepped it for use. This allowed for each server spun up off this image to receive a unique GUID. However it met with limited success and this method does not allow for updates to be performed on the master image without having to redo the entire DNS poisoning again method every time we need which includes uninstalling and reinstalling the agent. I am presently looking to find out what this cloned agent task actually does on each cloned host so I can replicate this process within a script that will then run on power-on for each desktop spun up. These are my assumptions: The task replaces the GUID from the registry. Removing the current GUID will cause the agent to no longer start (I've tried). The agent calls on a dll or other resoure file to perform other tasks These other tasks must including requesting a new GUID which is used to replace the one it removes from the registry, thus allowing the agent to restart. The agent must first retrieve this new GUID and insert it into the registry before restarting the service. I am looking for ways of checking what changes are actually made to the registry and any other components. If anyone wants to help with this process I would welcome the assistance.