I have a Windows 2003 server with Terminal Services installed. It is also a Domain controller.
There is another DC (part of this domain) in another location (users do not access). This second server is really just for AD backup.
First question - off the bat - is it a bad idea to have a DC that is also a TS - and why?
Will I experience any issues because it is a TS and a DC?
Second - I am thinking of applying Loopback processing to the Server.
Because the server is part of the Domain Controllers OU - and therefore part of the Default Domain Controllers Policy - do I turn on GP Loopback Processing - in the Defaualt Domain Controllers Policy?
Or do I create a second policy and apply it to the Domain Controllers OU?
Or do I move the server out of the Domain Controllers OU to a new OU and then apply the policy that has the Loopback Processing enabled? (I'm thinking no on this last one - as I do not want to lose any of the Default Domain Controllers Policy settings).
Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units?
This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource.
Use Google, Bing, or other preferred search engine to locate trusted NTP …
This Micro Tutorial hows how you can integrate Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease.
The following video show how to bind OSX Mavericks to …