Originally we had a 2008 print server. Another member on the network team created a 2019 server and made it a print server. He then populated the server with all the printer objects that the 2008 print server had - not sure what process he used.
When he spun up the 2019 server VM it was joined to the domain and left in the default built in container "Computers". It was not moved to our "Server" container where the rest of the physical and virtual servers reside.
We have recently implemented LAPS, and the LAPS GPO cannot be assigned to the built-in "Computers" container.
When I move the 2019 print server from "Computers" to "Servers" all printing functions stop and we get errors about group policy causing restrictions and the print server fails - no printing, can't add a new printer, can browse existing printers - everything stops working. To remedy this situation, I found a command that basically resets the group policy on the 2019 print server back to defaults. Once I run that command, the print server comes back to life. I've also noticed that the server is somehow moved back to "Computers" and is no longer located in "Servers". The command I ran is: RD /S /Q "%WinDir%\System32\GroupPolicyUsers" && RD /S /Q "%WinDir%\System32\GroupPolicy" followed up with a gpupdate /force
Does anyone know what group policy settings I might look for in my "Servers" container might be causing the print server to stop functioning? Does the 2019 server's print server install have some kind of tie into the "Computers" container and when its moved it causes everything to come to a halt?