Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm setting up a Active Directory lab environment on a Windows 8.1 laptop. I now have a Windows Server Core 2012 domain controller running inside a VM. I installed Server Manager for Windows 8.1 and have set things up so I can manage everything from the Win8.1 host machine.

Well, everything except Active Directory Administrative Center (ADAC). When started it produces an error: Your account or computer is not joined to any domain. Join to a domain and try again. All other AD-related management tools work just fine.

Is it impossible to run ADAC outside an AD domain or am I still missing some configuration? I do not want to join the host machine to the lab domain.

share|improve this question

2 Answers 2

up vote 1 down vote accepted

Is it impossible to run ADAC outside an AD domain or am I still missing some configuration?

Yes. Most of the built-in tools to manage things relating to your domain require that they are being run as a domain user. That necessitates the machine they are running from be joined to that domain.

That said, there are 3rd party tools that can be used to manage a domain. For example, any LDAP browser can manipulate objects in the directory. You just don't get a lot of the GUI niceties like check boxes and radio buttons for certain properties.

share|improve this answer
    
Maybe I should extend my environment with an OS version that actually has a GUI then (or stick with Powershell). Thanks for the answer. –  rwwilden Feb 27 at 12:32
    
Yeah. If your DC is going to be the only permanent machine in your lab domain, it makes sense to install the full GUI version rather than Core. –  Ryan Bolger Feb 27 at 18:32
    
I intend to run multiple machines so I'm a little concerned about footprint (especially memory). I'm assuming Core takes less resources than the GUI version. –  rwwilden Feb 27 at 20:12

I am a little late to your party here, but I am a full time consultant who logs into many different domains. In my RSAT tools, I use a line like this:

runas /netonly /user:domain\userid dsac.exe

The domain is the domain of my client, or your lab.

This works great, except it throws an error, unable to connect to the domain. It still opens the console though. Once open, I am able to connect to the domain that I need. If I find the way to connect it to the domain, I will post that here as well. If you don't have it already, here is what I use for most of the other shortcuts, just change the mmc it is opening:

%systemroot%\System32\runas.exe /netonly /user:domain\userid "mmc dsa.msc /domain=other.domain"
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.