You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all: great work with all your blogposts and ConfigMgr related solutions. Appreciate the effort and dedication!
I have a question for the function SetADOrganizationalUnitForComputer and the other AD related functions..
Scenario: Installed computer is located in site A and the ConfigMgrWebService server is installed in site B. Both sites have another AD controller assigned. If the computer is freshly installed and joined to AD, it will contact AD controller in site A. If I would like to move this computer object with the web services, it will connect to the DC in site B. If replication hasn’t taken place, it won’t find the computer and can’t manipulate it.
Have you taken this in consideration or how would you best solve this issue? Thanks!
The text was updated successfully, but these errors were encountered:
My suggested pull request #17 begins addressing this exact thing. My hope would be for all of the AD functions to have the option to specify a specific DC to bypass potential replication delays.
Hi Nickolaj,
First of all: great work with all your blogposts and ConfigMgr related solutions. Appreciate the effort and dedication!
I have a question for the function SetADOrganizationalUnitForComputer and the other AD related functions..
Scenario: Installed computer is located in site A and the ConfigMgrWebService server is installed in site B. Both sites have another AD controller assigned. If the computer is freshly installed and joined to AD, it will contact AD controller in site A. If I would like to move this computer object with the web services, it will connect to the DC in site B. If replication hasn’t taken place, it won’t find the computer and can’t manipulate it.
Have you taken this in consideration or how would you best solve this issue? Thanks!
The text was updated successfully, but these errors were encountered: