New domain woes and configuration manager




I have a dilemma with a customer which I hoping I can get some advice from the forum here...


They have a large user base and are moving/migrating from one AD domain to another within the same AD forest. This is to address some issues around them making the move to the cloud with their old domain name.


They use MECM current branch but have had issues using this whilst migrating to the new domain.


They cannot connect to a device in the new domain such as using the remote tools “Remote Control” or “Remote Assistance”


They cannot deploy App-v applications through MECM to new domain user/group collection(s)


It seems the service accounts are not working within MECM Administration > Hierarchy Configuration > Active Directory Forest > Discovery & Publishing


Looking at this a few things pop into my mind.


  1. Making sure appropriate client push and network accounts are configured for new domain.
  2. Understanding how the AD forest/domain trust, would MECM need two way trust?
  3. Would it be worth creating a new MECM server for new domain?
  4. Would a CMG help with this?
  5. If using same AD could boundary groups and AD discovery help with separating management for devices/users? Would AD sites and services need to be used to create that separation?

I was thinking maybe for new devices if they move to Intune and embrace new devices there.


Could really do with some expert guidance on this one as I am not sure what would be the best approach here.


Many Thanks

2 Replies


did you check the side boundarys ?

any kind on error on the local client logs ?

what happen when you try on the local client to search for the SCCM Side (control panel)

is the configuration inside the AD right 

any kind of firewall between the Server and the client ? 

can you try to connect from the server to the Client by using the Admin$ Share ?




Thanks Klaus I will take this points on board when performing a review of the customers environment. I will report back.