Migrate SCCM Clients from one child domain to another?
I currently have multiple child domains in my forest. We are in the process of planning a collapse of a few of the child domains to fall under one. To better explain we have 7 child domains, and we would like to collapse 3 of them into one of the other ones, so that woul leave 4 child domains. The three child domains, each have their own SCCM Primary site installations, so part of what i need to do is migrate the clients over to the rolled up child domain. I've added the new boundaries, and system discovery ldap but i can't see any of my test systems yet. I'm sure i'm missing something obvious.
July 5th, 2011 4:16pm

Sounds like you have overlapping boundaries, as you left the boundary active on the old siteserver, right? You would then have to assign the clients to the new site manually.Miguel Rodriguez
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 4:40pm

Boundaries have nothing to do with discovery, so that's not the cause. See adsysdis.log if the siteserver is able to resolve the names to an IP address (as this is a prerequisite for creating a DDR). I suppose you already updated the collection membership and refreshed the console? Torsten Meringer | http://www.mssccmfaq.de
July 5th, 2011 4:42pm

I excluded my test systems from the soon to be retired child domain, and added them to the rolled up domain.
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 5:04pm

I did modify the the collection membership and refreshed. I'll take a look at that log though.
July 5th, 2011 5:05pm

DDRs were created, so i went back and checked my All Systems collection, and the systems from the othe child domain are there. So the error appears to be in my collection for just that child system is the problem. I have created it the same way that i did for my other domain identified collection. System resource - OU Name = child domain test ou, i also added another for System resource - ad domain name = child domain. These were done as seperate queries. Nothing shows up in that collection.
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 5:24pm

Update the 'all systems' collection and refresh the console. Does the computer show up then? "System resource - OU Name" => You have to use "AD system GROUP discovery" in order to get OU information.Torsten Meringer | http://www.mssccmfaq.de
July 5th, 2011 5:35pm

I was clicking through my discovery methods and noticed the Network Discovery had a domains tab. This originally has the rollup domain as a member. Maybe i need to add the child domain as well? Also, should it be the fqdn or just the first section. For example rollup.domain.com vs just having rollup? i only ask because it seems to have a character limit of 15.
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 5:36pm

yes the all systems is updated. and yes i did the ad sys group discovery.
July 5th, 2011 5:38pm

There's no need for network discovery when AD System Discovery is active, unless you want to discover workgroup clients or routers...Miguel Rodriguez
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 5:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics