Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SetADOrganizationalUnitForComputer - AD Site for installed computer #14

Open
Unwillingly473 opened this issue Sep 20, 2018 · 1 comment

Comments

@Unwillingly473
Copy link

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!

@Yevrag35
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants