Another permissions related gotcha is when performing the task under run as different user, I have notice the same failure when the user performing the action has sufficient rights via group membership on the target OU. When directly adding that user to the OU permissions, it allowed the creation of the computer object. Possibly some run-as activity isn't passing a full access token on the connections and the group membership is ignored?
Wednesday, March 20, 2024
New-ADComputer : A required attribute is missing
When trying to create a computer with this commandlet and you get this error, it may be a poorly worded exception. This error can come up if you don't have permissions to create computer objects on the OU you provided. If you follow the commandlet examples and provide what is required: samaccountname, name, and path; go check the OU permissions. If you had tried doing it with the older dsadd command, it will give an error that the modification was not permitted for security reasons. Once permissions are fixed, or a different set of properly delegated credentials are passed, it should work fine.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment