This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Dear Team,
We have the existing DPs in our environment which has PXE enabled since now we are replacing these DPs by configuring the new DPs so would that effect the current build if I enable PXE on new DPs?
Can we have multiple PXE enabled DPs in the same hierarchy without impacting the build on the working DPs?
Just for the reference - We have 1 CAS, 2 primary sites and we are planning to migrate the clients by adding a 3rd primary site into the hierarchy. Let's say from existing primary 1 which has site code ABC, the clients will migrate from ABC to new primary site CDE.During this migration activity, we will have a time where devices will be served from existing DPs and the new DPs. So, if we enable the PXE on the new DPs this shouldn't impact the builds from existing DPs from site ABC.
Please suggest.
Other Configuration Manager-related features and issues
If your network and IP adresses stay the same, and you just replace DP server from one to another, PXE service should work as is without any network change.
You also should be able to do, that your PXE responsive DP would be different from another one where all the content would be downloaded.
Thank you so much @Pavel yannara Mirochnitchenko for your response.
Let me put into this way, we have 1 CAS, 2 primary sites and we are planning to migrate the clients by adding a 3rd primary site into the hierarchy. Let's say from existing primary 1 which has site code ABC, the clients will migrate from ABC to new primary site CDE.
During this migration activity, we will have a time where devices will be served from existing DPs and the new DPs. So, if we enable the PXE on the new DPs this shouldn't impact the builds from existing DPs from site ABC.
Does that make more sense.
I'm not sure, I never worked with CAS and multiple Primary Sites. But I believe the DP is married to a site code, so if old DP is from ABC site and new DP is from CDE site, that swap will not be so simple. I might consider the scenario, where you would first move old DP from ABC to CDE and then later swap DPs. But I am not sure. It would be great if you would describe your CAS and multiple sites in first discription, since you are having more complex infra. Not everyone is playing with CAS because that is a requirement for more than 100.000 clients :)
Thanks again for the valuable response @Pavel yannara Mirochnitchenko . I updated the description per your suggestion.
I know this is complex environment and the current OS builds are done from primary site ABC with DP as you said married to ABC site.
Just wondering, if we enable the PXE on new DPs which will be pointing to new site CDE then would that effect current build?
In other words, will devices from ABC will not try to build from CDE DPs? That's the concern.
If in case, we enable the PXE for new site DPs post the migration would that be a good approach? Suggestion.
Well, site code ABS is assigned via client policies, locations, AD object etc. If you just replace DP ABC with DP CDE on the same network, it is possible that clients stay at ABS and will not communicate to new DP.
As from PXE point of view, if you are about to reinstall Client ABS, you delete computer account from CM, then PXE it up, client would be rebuilt to CDE site. Again, I am just assuming this and there is many factors which affect this behavior. Do you use GPOs to assign site code? Active Directory can contain multiple site codes, but still under same system container. Site Code could be assigned based on subnets?