We are in the process of migration between an old domain (which has SCCM in it) and a new domain (which does not have SCCM), if we use the ADMT tool to migrate the computer objects will SCCM still work when the computer is in the new domain. We were told that System Center products have a heavy tie into Active Directory and schema - we want to know if the existing SCCM will still patch the clients.

Is it possible? Sure.... but I suspect you'll want to heavily research the documentation around managing Workgroup clients. I know... those clients are in a domain; but it's not the same domain/forest as the ConfigMgr server, so a lot of the documentation around managing workgroup computers applies. If I were you, I'd definitelyget started on the project to stand up a new ConfigMgr Server, do NOT use the same site code or servername, in the new domain. And then migrate those clients to the new ConfigMgr server.Standardize. Simplify. Automate.

Thanks for the reply - So it might be definitely possible, I thought SCCM extends the schema, how would the new domain know that SCCM exist if no schema exists. That is why I am posting this question. Would the client know the discovery points in the new domain? Any more information would be helpful to determine if this is possible or just will not work.

hi, yes it does have a heavy tie with ad and schema with regards to publishing information about itself as a site server or server locator point, and that way clients can easily be assigned to it. would you be installing a new sccm in the new domain? if yes you can follow this steps for ease of administration leave the old site server as it is 1) Create a new ConfigMgr server (in the new domain) and add it as a child site to the existing server. 2) This will replicate all packages, task sequences, collections, advertisements etc down to the new server. 3) Once the replication is done, I would make the new server a parent server. This will upload all client data. 4) Finally run a script/package to reassign the clients to the new site. There are various ways of implementing what you plan to do for further details u can follow this thread which is similar to your scenario http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/48afaf39-08a8-43c7-ac22-20ee7a002152 Hope this helps! PS: guess i was replying while u typed already. i believe if there is a trust relationship between the two domains u should do just fine using the steps above to move!

In my question NO new SCCM in the new domain - we would use the existing SCCM for a while in the old domain, then eventually build a new SCCM in the new domain. My question is during this transition period will the old SCCM be able to patch clients in the new domain. It is still not clear to me whether this configuration will work or not.

i'm positive it would work but the exact way is how to manage it . what security mode does your current sccm run (native/mixed)?

The main thing that we need to know to be able to accuratly give you helpful information is whether or not the new domain is in the same forest as the old one? If so then no problem. If not my suggestion would be to create a child primary site in the new forest. Once all of the computers have been migrated over to the new forest break the parent child relationship or simply. My next suggestion would be to create a new site in the new forest, uninstall the sccm client before migration, then reinstall after migration. Which way you go would depend upon what your goals are. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

We are mixed mode I think. Different forests with a two way trust between them. I guess we could add a client to the new domain and see if SCCM can assign it as a client and patch/manage it.

different forests means you need a primary site in each unless you want to manage clients as if they are workgroup clients. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Hi John, i guess they need to run that setting temporarily till they set up a new sccm site server in the new domain so maybe the workgroup clients stuff might be the way out just as mentioned earlier by Sherri. in that case you might want to view http://social.technet.microsoft.com/Forums/en/configmgrsum/thread/31ec1ebd-8be1-4a91-a4df-5b002a71cfc0 http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/b24b5427-dc61-4963-9866-116b7ef3f3e9 here is a link to setup switches just in case u need them http://technet.microsoft.com/en-us/library/bb680980.aspx

My recommendation would not be to attempt to manage them as workgroup clients. I would setup the new sccm in the new domain prior to migrating clients. Problem with using the setup switches you mention is that these machines are already SCCM clients. They are already assigned to a site etc. The link that would actually be relevant is http://technet.microsoft.com/en-us/library/bb694003.aspx John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Thanks everyone for all the feedback.