I am unable to promote my newly installed Windows Server 2012 machine to a domain controller.
Joining the domain as a server that is a member of the domain worked fine.
Possible Duplicate:
Can you help me with my software licensing issue?
I am designing a network and I've come to the point of specifying out the number of CALs required for this network. Microsoft licensing has always confused me, it's just not always clear to me.
I have several networks which are isolated from one another apart from one of the networks hosting the primary domain controller.
My situation is as follows:
I have a Windows 2003 Domain Controller which is also my DNS server. I have 10 Windows XP Pro PC's which all login to domain accounts. I am about the forward my DNS requests to OPENDNS so I can regulate web access but I have (2) PC's that I would like to keep unregulated.
I'm migrating servers from colo locations to Amazon's VPC EC2 instances. If anyone hasn't worked with Amazon VPC before, VPN is a pain in the arse!
Anyways, I setup a new server that acts as the domain controller for our Amazon VPC.
I have 4 servers running windows server 2012.
I have one of the setup as my domain controller, for let's say domain.local
Obviously when I installed this it added the DNS server and this was as expected. I then proceeded in joining my other servers to the domain and all went well, I also set the DNS to only respond to requests coming in on the internal network's NIC.
If my machine has Windows 7 and connect to domain, what happens when domain controller is unavailable ?
How do I exactly log in when domain controller is unavailable ?
I mean normally it should use Kerberos, and it should fall back to NTLM.
Does that mean domain account and password hash are stored in SAM ?
Here's a quick summary of the environment I support: we have a domain (domain A) that has about 20 client computers. The domain server for this domain and all the clients sit within the network infrastructure of a larger domain (domain B). All the computers get their network settings via DHCP from domain B's servers.
I'm using this guide to add my linux (10.04 lucid) ubuntu machine to domain.
First I tried using likewise, but couldn't do this apparently due to some compatibility issues with 10.04 kernel. I had downloaded the 25 Mb size centrify agent. I run the command using this command: ./install-express.sh Everything works fine.