📎 AI Summary:
The original poster is experiencing difficulties changing permissions on the "CN=Computers" group when setting up LAPS, as their command works on Organizational Units but not on the common "Computers" container. A respondent suggests temporarily joining the computers to the relevant group, while another advises creating a process to move the computers out of the "Computers" container, since it is not an organizational unit. Overall, the thread centers on addressing permission management challenges within Active Directory for proper LAPS configuration.

techboss77

New Member
Member details
Joined
Apr 20, 2022
Messages
1
Thread Author #1
I am currently having an issue with changing permissions on our networks CN=Computers. When setting up LAPS you must run a command on the organizational units that have your workstations in them. Well our network has been setup where our Headquarter's Computers sit within the CN=Computers group and our branches workstations are within an OU. When attempting to change permissions for our OU the command runs perfectly. This powershell command... set-admpwdcomputerselfpermission -OrgUnit "my ou" works but since all out other workstations at sitting in CN=Computer that command doesnt work. Is there a command that is something like..set-admpwdcomputerselfpermission -ComName "my ou" so that the permissions change be changed on a common name group also?

Thanks!
 

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
You will need to create a process to move them out of 'Computers' since it is a container and not an OU
 
Solution