sjl

###|-------- ###|##########|--- ###| ###|-------- ##############| ##############|------ ##############| ##############|------------------------ ####################################| ####################################|----- ##############################################| ##############################################|---- That is a bit of ours we also use WMI filters and Security filters to filter who gets the GPO applied.

7 and Y wrote: - I would agree with this - a more standard approach is to have all internal clients point to your internal DNS server then have that server set up with a forwarder to your external DNS - that way internet DNS requests are sent to your DNS server which then performs the query on your client’s behalf. This scenario has many advantages a big one is your internal DNS server will cache the queries for internet sites – speeding up name resolution and meaning you clients don’t have to leave the building for name resolution Cheers, Steve

In not too sure i understand this question: - So you have four other Domain Controllers set to act as GCs on your domain - Correct? You are looking at decommissioning one of your domain controllers which is set as a GC - Correct? Also - is Exchange installed on a Domain Controller or is it on a member server? If you decommission your Domain Controller (also one of your GCs) then Exchange and exchange clients will just automatically look to the other GCs that exist on your network. Remember to decommission that DC properly too - here is a Microsoft Guide: - Decommissioning a Domain Controller: Active Directory Just be certain that you have those other GCs on the network and move any other fsmo roles before throwing your server through the top window!. Cheers, steve.