Excluding Servers from Domain-based NS Agent Deployment
We have two NS servers, a primary that is deploying NS agents to the Active Directory domain, and a secondary NS server that is apart of the same domain and has a newer version of RS integrated into it due to needing to back up newer OSes.
The secondary NS server has an Inventory Forwarding rule to the primary NS server. The primary NS server has a Resource Collection that identifies server based on name and OU to not deploy the Altiris Agents.
The problem I'm seeing is that even though the exclusion is in place, the primary NS server is still overwriting the Agents on the particular servers that are pointing to the secondary NS server.
Is there a good way to prevent this from happening? Not having the primary NS server deploy Agents to the domain is not a workable solution.
All the machines involved are running Windows.
Comments
You could ..
..move those servers to an OU and not import that OU with the AD tool. How are you setting up your exclusion, just adding that collection to the exclusion list?
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Or,,....
We do not allow NS agent install to go rouge on the network,. we turn off ALL discovery and us a GPO with a WMI filer to target workstation systems and secuirty group filter to install the agent. We have a vbs script that then checks if the agent is installed is the service is running, what version is the agent running and if not reinstall. Seems to work really well and we can keep our free license threshold a lot lower.
Would you like to reply?
Login or Register to post your comment.