SCCM 2002 server not in a good place for co-management
I am currently working with a customer who has 2002 and want to move to co-management as they move to Modern device management. They are currently moving from one AD domain to another (they have a two way trust setup), the new domain is configured with Azure Cloud and Azure AD Connect to sync AD identities to the cloud.
The SCCM server sits in the old domain however there are some issues with the current environment and it’s not in a healthy state. Examples include:
1. Remote control tools do not work for machines configured in the new AD Domain. work fine in the old domain.
2. Task sequence smsts logs not reporting/coping back to MECM server on completion of build.
3.Deployment of user virtual apps in SCCM fail in new domain, work fine in old domain.
The issue occurring is due to in the past the SCCM server was built from a golden image containing duplicate SIDs, when they only had one domain, everything worked as expected however introducing the new domain, certain functionality of SCCM no longer works on new machines. The login is invalid as the authentication attempt contains a SiD that references multiple machines in the target domain meaning the domain controller cannot return valid credentials. The customer believes that re sysprepping the SCCM server could resolve this issue however the problem is the server will still remain in the old domain and they are looking to move all their environment to the new domain eventually and dispose of the old domain.
Before we enable co-management and cloud enable SCCM on 2006 we have asked the client to resolve these issues. My thoughts are to build a new SCCM server in their new domain and perform a backup of configMgr DB and other data and just restore that onto a new server, this means no other windows server specific config like SIDs will move across and it should mean a nice tidy clean environment. My question is what impact could this have with the existing estate. Would the same server name need to be used for clients to connect or is further config required to make it work by restoring ConfigMgr to new server.
Is there any good documentation around that assists with moving SCCM to a new server?
Many Thanks, happy to provide more detail if required.
Answers ( 5 )
Has anyone used this option to migrate from one SCCM to another?
The easiest option is to do a side by side migration. This will help to carry forward the unwanted packages, Updates, etc to the new SCCM environment.
Once the new server environment is ready to migrate the clients to the new Primary server………
Is there any documentation on how this can be achieved? Thats what I am struggling with.
When you say unwanted packages, what do you mean by that, as I assume all existing packages, updates would all need to be moved to new environment. Can you be selective during migration phase?
Is this the side by side migration method which you discussed back in one of your blog posts suitable for my case?
This is not exactly the same scenario because backup and restore won’t work/not support if you are changing the domain.
What I meant is to build a new SCCM environment in the target domain and migrate workloads one by one using migration jobs option available in the SCCM console.