Secondary ConfigMgr site in child domain

Question

question

BojanZivkovic-7448 asked Oct 25, '21 AllenLiu-MSFT edited Oct 29, '21

Secondary ConfigMgr site in child domain

Hi, currently we are in the process of decommissioning child domain and moving all servers/clients to parent domain. One of servers in child domain is hosting secondary Configuration Manager site (2103 version) - since it runs on very old hardware we are thinking of deploying new remote Distribution Point in parent domain which will physically be in remote site whose domain is being decommissioned. Having done that, current secondary site would be removed altogether and CM clients pointed to new DP to pull content from.

Is this good way of handling this situation? Should we uninstall/install CM clients having moved all servers/client to parent domain since current server hosting secondary site is listed as proxy management point for all clients in child domain? Is there something more to be done?

This is something not frequently performed so I need an trustworthy answer. Thank you very much in advance.

mem-cm-general

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2021-10-26T07:11:04.21Z

AllenLiu-MSFT answered Oct 26, '21

Hi, @BojanZivkovic-7448
Thank you for posting in Microsoft Q&A forum.

Based on my experience, it's feasible to do.
After remove the secondary site, you just need to adjust your boundary groups accordingly so that clients will use the new Distribution Point and Management Point.
The Proxy MP means the MP in the secondary site that the client agent is using if it's within the scope of a secondary site.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2021-10-26T11:32:56.433Z

BojanZivkovic-7448 answered Oct 26, '21 AllenLiu-MSFT commented Oct 27, '21

But after removing secondary site only new remote DP will be there so no proxy MP anymore?

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AllenLiu-MSFT · Oct 27, 2021 at 01:56 AM

The proxy MP only exist when the client is part of a secondary site server, it's not a required configuration.
Just make sure the assigned management point is specified.

0 ·

Answer 3 · 2021-10-27T11:57:38.717Z

BojanZivkovic-7448 answered Oct 27, '21 AllenLiu-MSFT edited Oct 29, '21

Hmm still some things worrying me:

How removing secondary ConfigMgr site would affect ConfigMgr clients installed on servers/desktops/laptops in child domain?
Can new remote DP in parent domain be used as content repository for systems in both parent/child domain during transition period - we will gradually unjoin systems from child domain and join to parent domain so they must be patched all the time?
How domain change of system affects its ConfigMgr client? Is reinstallation required?

I would like to get some steps not to skip anything important because for us ConfigMgr is considered as critical part of our infrastructure. Thx in advance.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AllenLiu-MSFT · Oct 29, 2021 at 09:43 AM

It depends on how do you configure your boundary groups, domain change do not require the client to reinstall.
Hope MVP @Jason-MSFT can provide some more precise advice.

0 ·

question