up vote 0 down vote favorite
share [g+] share [fb]

My company is in the process of building a new AD Domain for our VDI environment. Once the VDI rollout is complete, we will be migrating everything out of our existing domains into this new domain.

I want to use this opportunity to correct the many errors that my predecessor made when setting up Group Policy for users and computers in our existing domain by starting from a clean slate. Are there any recommended best practices for using Group Policy to configure settings on servers that host SQL or Exchange? Are there any settings that I should avoid changing?

link|improve this question
Why don't you give us an example of the errors you think your predecessor made? – joeqwerty Aug 30 '11 at 17:50
The errors my predecessor made were more on the user and workstation side since he didn't apply any group policy to any of our servers. I updated the question to reflect that. What I am looking to do in the new domain is apply Group Policy to manage all of my servers, and I want to know if there are any group policy objects that shouldn't be applied to Exchange or SQL Servers. – smassey Aug 30 '11 at 20:59
If it's working fine, then don't go fiddling with it. Change what you need. Personally, my servers have very few GPO's applied to them - WSUS settings, logon scripts and maybe a couple of other minor tweaks, but certainly nothing like the amount of GPO's our desktops get. – Ben Pilbrow Aug 30 '11 at 21:03
@Ben: Thanks. That answers my question. – smassey Sep 1 '11 at 3:30
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.