Ima Bum
asked on
How to create an Azure Lab with two VM's Windows Server 2012 R2 or later and a Win 10 workstation so that I can join the Win 10 workstation to the domain
In Azure, I set up two VM's, a Win2012 R2 DC and a Win10 workstation, both VM's in the same subnet 10.0.0.0/24.
When attempting to add the Win 10 workstation it says it cannot find a DC? I deleted the VM's and am about to try again, as I was getting pretty burnt out and frustrated. Figured I'd ask before I begin again. Is this a feasible lab scenario?
When attempting to add the Win10 workstation to the Domain, the message I was getting was that the win 10 workstation could not find a domain controller in the domain. I went with Test.Com as my domain vs Test.local Maybe that was part of my problem? This is my first Lab using Azure.
Is there an article on how to build this lab environment? It's possible that I misconfigured something fundamental with DNS and or the IP stack on the workstation?
My goal is to have a Windows Domain Controller and a Win10 Pro or Enterprise workstation so that I can test GPO's and login scripts.
Then, my plan is to connect a Firewall to another location and set up additional workstations, but for now, I just want to get the single Azure domain up and running with just the two nodes.
Feedback appreciated.
R
When attempting to add the Win 10 workstation it says it cannot find a DC? I deleted the VM's and am about to try again, as I was getting pretty burnt out and frustrated. Figured I'd ask before I begin again. Is this a feasible lab scenario?
When attempting to add the Win10 workstation to the Domain, the message I was getting was that the win 10 workstation could not find a domain controller in the domain. I went with Test.Com as my domain vs Test.local Maybe that was part of my problem? This is my first Lab using Azure.
Is there an article on how to build this lab environment? It's possible that I misconfigured something fundamental with DNS and or the IP stack on the workstation?
My goal is to have a Windows Domain Controller and a Win10 Pro or Enterprise workstation so that I can test GPO's and login scripts.
Then, my plan is to connect a Firewall to another location and set up additional workstations, but for now, I just want to get the single Azure domain up and running with just the two nodes.
Feedback appreciated.
R
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Look at your network setup. Make sure the DNS server address given to your client can resolve the domain name.
ASKER
Thanks, I am going to "re-create" the DC with AD Domain Services. I think I'm going to go with Windows 2016 Server this time.
ASKER
@Jeff Glover I'm not following what you're saying. Can you re-phrase it or give an example.
ASKER
I've discovered that DHCP Servers in Azure are not supported, locally or to WAN facing clients. It seems that I'm going to have to manually assign IP addresses to the workstations if I want to join them to the domain.
I'm getting closer to figuring this out. It's definitely a learning experience involving a bit of reading and the usual trial and error. While I'm liking Azure it's definitely "different".
I now have the Login prompt to the domain but I still haven't added the Win10 workstation yet as I still need to try out a few more things before I isolate the "actual" problem.
This is by no means a typical Client ~ Server domain model. At least with VM's outside of Azure, if you set up a DHCP server the server will hand out addresses to clients. I've not concluded just yet, but I'm finding this a little difficult to believe that DHCP in Azure running on a Windows Server doesn't work. According to various articles in reputable forums, I'm pretty sure that this is in fact the case. I would certainly like to see if someone else has actually managed to get DHCP working aside from joining a Win10 workstation to a Windows 2012 R2 or higher domain.
More info. to follow.
I'm getting closer to figuring this out. It's definitely a learning experience involving a bit of reading and the usual trial and error. While I'm liking Azure it's definitely "different".
I now have the Login prompt to the domain but I still haven't added the Win10 workstation yet as I still need to try out a few more things before I isolate the "actual" problem.
This is by no means a typical Client ~ Server domain model. At least with VM's outside of Azure, if you set up a DHCP server the server will hand out addresses to clients. I've not concluded just yet, but I'm finding this a little difficult to believe that DHCP in Azure running on a Windows Server doesn't work. According to various articles in reputable forums, I'm pretty sure that this is in fact the case. I would certainly like to see if someone else has actually managed to get DHCP working aside from joining a Win10 workstation to a Windows 2012 R2 or higher domain.
More info. to follow.
Make sure you have DNS installed on the DC. Make sure the zone looks correct and has SRV records published. (the DC should point to itself for DNS since it is the only one). Make sure the client DNS is set manually to the DC address. By default, Azure sets things up so you can get to the Internet but not necessarily to each other unless you install and configure Azure AD services (which kind of defeats the purpose of the lab). Run IPconfig /all on the client to make sure it is set correctly.
ASKER
I isolated my problem down to the following.
1. AZURE's lack of DHCP forced me to use a static address.
2. I had to create a static A record in DNS
3. I had to use the FQDN for the Domain Name when adding the Win 10 workstation.
Once I created the aforementioned, in that order, I was able to add my Win10 workstation to my Azure Domain. I'll wait for comments before I conclude.
Thanks to all that helped.
1. AZURE's lack of DHCP forced me to use a static address.
2. I had to create a static A record in DNS
3. I had to use the FQDN for the Domain Name when adding the Win 10 workstation.
Once I created the aforementioned, in that order, I was able to add my Win10 workstation to my Azure Domain. I'll wait for comments before I conclude.
Thanks to all that helped.
Not that experienced with azure but if your new vm does not know where the dc is i wonder if DNS and GC are setup and second, how does your win10 machine should obtain an ip address? Did you setup some kind of DHCP?
Cheers