Add Virtual Machines to an Active Directory Domain

Comments

8 comments

  • Avatar
    Carolyn Clarke

    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.

  • Avatar
    Peter Franks

    Thanks for the tweaks Carolyn!  I've updated them in the walkthrough.  

  • Avatar
    Greg Gignac

    Clear as mud. Where is the network ID button? Please start making some youtube videos already.

  • Avatar
    Peter Franks

    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.  

  • Avatar
    Karthick P

    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.

  • Avatar
    Peter Franks

    So, basically setting up a VPN to your datacenter?  

  • Avatar
    Soeren Christensen

    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

  • Avatar
    Don Frederiksen

    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.