We have one production site that uses SUP to install clients and system discovery with specific OU's to detect client machines. We now have a separate test primary site with the same settings other than system discovery is only looking at one child OU in Active Directory to pick up our test client machine. The test client installed Configuration Manager, but is seeing production. It shows as a client in production and shows up in the test primary site, but it not a client. How can I ensure that our test primary site and our production primary site do not see the same clients? Thanks, Brit

HiYou can try with different boundary settings for each site.RegardsKarthikck V

I will pass this request on to our network area. I currently do not have a separate Active Directory site for our test Configuration Manager site. I removed the site boundaries in test and will add the new AD site to our test boundaries when it is created. Are there anyother suggestions or things to watch for?Thanks, Brit

HiThe only alternative I can think of is installing client using command line and then forefully pointing it to the required primary site should solve your issue.

I will go with the AD new site for boundaries. I did push the client from test to the test client, but it ended up seeing the production site as it's primary site and MP most likely due to my boundaries seeing all of our clients in AD. Hoepfully when we have a separate site for test clients in AD we can keep these site servers from seeing the same clients.Thanks, Brita

I will go with the AD new site for boundaries. That's the best solution. It's unsupported to have the same boundary on more than one site. (overlapping boundaries)John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Thanks for the reminder on that.