The Synch Domain scheduled task

[NickFerrar]

From reading the ePO product guide I got the impressino the Synch Domain task adds in computers it finds in the domain that aren't in the ePO and pushes the Agent to them (as well as remove PCs if the opposite is true).

However I just run a task as a test and it seems it also tries to push the Agent to any PCs already in the ePO if they haven't got it installed already. Is this true - if so it's a bad idea IMO, otherwise how can you prevent some systems having the Agent installed?

We have a couple of servers and test systems here we don't want the Agent or VS deployed to, so I created an exceptions group in the ePO and put them in here and set the group not to inherit or run any tasks.

Is there anyway to permanently exclude systems from getting the Agent installed to them yet also run scheduled Synch Domain tasks?

 

[simonjcook]

The Sync domain task gathers a list of hostnames from the network browse list.

It compares the list with the contents of a site folder by the domain name.

From my experience it does not take into account, nodes in sub-groups.

Those hostnames which do not exist in the Site level are added to the directory and the agent pushed to all nodes without an agent.

You are correct, there does not appear to be a mechanism to include an exception.

The lack of consideration of nodes in the subgroups is also major omission for those who have well structured ePO directories.

The Sync task is merely an automated form of the Update domain task from epo 2.x and older which allows the inclusion of credentials for multiple domains.