Here is a useful command that I’ve discovered.
\nImagine a situation where you have a domain called domain.local with multiple domain controllers DC0, DC1 etc.
\nFor some reason some clients are not working as expected or working slower. In my case it was when I tried to run gpresult \/r on some clients it was taking ages to provide full details. To find out if any of the domain controllers is having problems I wanted quickly to change the domain controller that the affected client is using.
\nBack in the day when Windows NT 4 ruled the world there was a command called setprfdc (set preferred domain controller) nltest does something similar.<\/p>\n
So first I wanted to find out what DC the client is using. Now there are many different ways but here is a command that I’ve used: DC: \\\\DC0.DOMAIN.local<\/a><\/em> This means that the client is using DC0. Now I wanted quickly to point the client to a diferent domain controller DC1. To do that write the following command:<\/p>\n
\nnltest \/dsgetdc:domain.local<\/strong><\/em>
\n
\nThe output was:<\/p>\n
\nAddress: \\\\10.10.10.1<\/a><\/em>
\nDom Guid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx<\/em>
\nDom Name: DOMAIN.local<\/em>
\nForest Name: DOMAIN.local<\/em>
\nDc Site Name: Default-First-Site-Name<\/em>
\nOur Site Name: Interxion<\/em>
\nFlags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST
\n<\/em>The command completed successfully<\/em><\/p>\n