|
I've been tasked with redoing our group policies at my company. I started by breaking up each department for things like printers, and drive mappings. I then went to muck around 2500+ options to make a new policy for the entire domain, WUS and the like. I ran into an issue that when I implemented the new policy it effectively broke all database connections. For the most part it was simple enough to fix, rebooted the servers (my boss wouldn't let me enforce the policy while we had the servers down to begin with), however, there were a few boxes that just died. Our encoders are proprietary hardware and the SID's turned to 0's, breaking the entire system. Is this normal and if I go to make further changes is there a way to avoid this? Also, we have 10 departments, so I have individual policies for each of those and then one for every day behavior. Is there a better way of making this happen? What special things besides WUS, security policies, etc, can I leverage to make our environment smooth like butter?
|
#
¿
Jun 11, 2010 20:44
|
|
|
|
| # ¿ Apr 25, 2024 11:25 |
|
|
skipdogg posted:You really shouldn't ever dick around with the default domain policy too often. That's the way I was going originally but my boss wanted it the other way. I do what he wants to stay employed, told him what would happen but he thought I was wrong. Then everything broke. I'm slowly going through now and applying specific things to our groups, waiting for our servers to break again.
|
|
#
¿
Jun 12, 2010 01:09
|
|