Add Virtual Machines to an Active Directory Domain
1. Add the Virtual Machine to the domain in the virtual operating system
2. Configure the domain in the CloudShare portal
Overview
The following walkthrough provides a step-by-step guide on configuring an active directory domain in CloudShare. A simplified guide of these steps is provided in our Community Help area.
1. Add the Virtual Machine to the domain in the virtual operating system
1. View the AD machine (click 'View Machine').
2. Copy the Domain administrator password:
Click the 'more details' link in the upper right side of the page and copy the domain name, administrator name, password, see below:
For example in this case the user name is: ad2008r2\Administrator and the password is: Dm1l0Y32AL. This means that the domain name for this domain is AD2008R2.LOC. This information will be used to add the VM to the domain.
3. Go to the VM networking configuration and add the domain controller internal IP as the first DNS option (leave the original DNS server IP as the alternate DNS server):
4. View the machine you want to add to the domain and adjust the DNS to point to the IP of your Domain Controller
5. Go to 'Computer', right-click and select properties.
6. Under Computer name, domain and workgroup settings, choose 'change setting':
7. Click the “Network ID” button and follow the wizard to join the VM to the account.
- As the domain name use the above name - AD2008R2.LOC (note, if you get an error in the following process, try removing '.LOC' from the Domain name.
- Use the Administrator user and password as copied from the above step - user: Administrator; passwordDm1l0Y32AL.
8. Click next and fill in the domain name with the same domain name as above (the computer name should not be changed.):
9. Add user, password and domain in the next popup windows (as in step #8 above)
10. Follow the next wizard’s steps and reboot the VM as wizard requires.
At this stage the domain membership is defined at the OS level, now we will need to configure the CloudShare portal.
2. Configure the domain in the CloudShare portal
1. After the VM reboots (logs in with the local user not the domain) , go to 'Edit environments > Edit domains
2. Click on the number of VMs in the domain and “add Machines”
3. Add the new domain machine
4. Confirm changes
5. Save changes
The VM has now been added to the domain in CloudShare
Comments
8 comments
Great instructions, just a couple of tweaks to make it work:
Part 1: After Step #4, you will need to repeat Step #3 on the client VM. This enables the client to connect to the correct DNS server in order to be added to the domain. Omitting this steps results in an error at Step #7. Additionally, if you receive an error in Step #8, try removing the ".LOC" from the domain name.
Part 2: If you have a SharePoint server that is also a DC, you may see two domains. You must first remove a VM from one domain before you can add it to another.
Thanks for the tweaks Carolyn! I've updated them in the walkthrough.
Clear as mud. Where is the network ID button? Please start making some youtube videos already.
Hi Greg, sorry you're not seeing the Network ID button, I've added a screenshot for you under point 7. YouTube videos are a great idea and we have some out there, but we're always trying to add more. We'll get one for adding a machine to a domain on our list as yes - it would definitely help!
Mind you, that first step is a standard Windows process so I'm sure there's something out there. It's not until step 2. that we get to the nitty gritty CloudShare stuff.
Hello,
How to connect a virtual machine to the domain controller in our own datacenter? Is that possible? I want to run a lync server on cloudshare which will take the domain controller hosted in our own datacenter and uses that.
So, basically setting up a VPN to your datacenter?
Hi Scott
Setting up the VPN so i can have our local domain extended to the CloudShare domain is what I need.
Can I get some help doing this? I´m not much into this world of router/VPN setup..
spc
One tweak was required in my environment. The SharePoint 2010 template that I was using for my domain did not have the DNS service installed. After installing the DNS service the domain could be discovered during the change.
Thanks for the nice instructions.
Please sign in to leave a comment.