Maverick...
The DLP agent is not like the Symantec AV agents. There is NO unique ID that is associated to the DLP agents.
The DLP agents register themselves with the Endpoint Servers that are defined when the agent is first installed. The agent registers itself with the Endpoint Servers using its HOSTNAME. So if the imaged OS connects to an Endpoint Server it will use the Hostname at that time. If you change the hostname afterwards, you will see 2 new registered agents in the UI. So this means if there is ever 2 hostnames that are the same you will have some issues.
So if you install the agent as part of the image, just make sure you go through the process of initiating the Windows OS and change the hostname. Pretty straight forward.
Keep in mind that this is very easy AS long as every agent is going to connect to the same ENDPOINT SERVER. If you plan on customizing whch Endpoint Server the agent will communicate with you can do this in 2 different ways.
- Change the hostname of the endpoint and let it connect to the default Endpoint Server. Then go to the Enforce UI and change the Endpoint Server from the agent overview page.
- The other option is to use the Agent tools to try and change the Endpoint Servers using a customized command.
I would try and do option 1 when possible. You can have an Endpoint Server that you use just for staging this newly imaged endpoints, then move them to the production Endpoint Servers.
Another option is to use locally resolved DNS to just have all endpoints point to "endpointDLP.domain.com" and this name automatically is resolved to the closest Endpont Server via DNS.
If this answeres your question, please marked this as solved