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.

Can you manage a Windows 2003 functional domain with the AD powershell modules? I have read that you must install the AD management gateway service to do this, but what if you do not have any Windows 2008 domain controllers, just one single Windows 2003 domain controller?

Thank you

share|improve this question
add comment

3 Answers

up vote 3 down vote accepted

Aha!

Yes, you can manage a 2003 FL domain with the AD PowerShell Modules. (I do it myself... well, 2k3 R2... and check this [old] thread at PowerShell Community.)

However, the modules themselves are intended to be installed on Server 2k8 or Win7, and though I've seen reference to hacks to install it on XP or 2k3, that seems pretty foolish to me. Get a Win7 workstation and you can manage your 2k3 domain from it with the AD PowerShell Module you mention.

Also, as from that PS Community thread, you will require ADWS, which is available for Server 2003, and your DCs may also require some patches and updates to the .NET 3.5 framework. Two years later, I'd hope that's already the case in your environment, but you never know.

EDIT: And here's a technet blog about how to set it up, the important bits of which are posted below in case the link goes dead or whatever.

Required tools/patches:

  1. Remote Server Administration Tools (RSAT) for Windows 7
  2. Active Directory Management Gateway Service (ADMGS) (Active Directory Web Service for Windows Server 2003 and Windows Server 2008) and Install Guide
  3. Microsoft .NET Framework 3.5 Service Pack 1
  4. KB969166 - A hotfix rollup package for Active Directory Web Service is available for the .NET Framework 3.5 SP1
  5. KB969429 - Windows 7 clients cannot locate the Active Directory Management Gateway service that is installed on Windows Server 2003-based domain controllers
  6. KB967574 - Windows 7 clients cannot locate the Active Directory Management Gateway Service installed on Windows Server 2008-based domain controllers

[And as usual, you only want to install the hotfixes if you need them, and you have to hunt through the KB article and then go through the email-us-to-get-a-download-link junk to actually download them.]

Installation/Setup:

On your 2003 DC:

  1. Install .NET 3.5.1 (SP1 for .NET 3.5)
  2. Install hotfix KB 969166
  3. Install hotfix KB 969429
  4. Install the appropriate version of ADMGS KB 968934
  5. Go to Services and observe/ensure that the Active Directory Web Service is now installed and started.

On your Windows 7 workstation:

  1. Install Windows 7 RSAT.
  2. Add the Windows 7 RSAT features bolded below (Control Panel, Programs, Turn Windows features on or off):

    Remote Server Administration Tools

    • Role Administration Tools
      • AD DS and AD LDS Tools
        • Active Directory Module for Windows PowerShell
        • AD DS Tools
          • Active Directory Administrative Center
          • AD DS Snap-ins and Command-line Tools

Fire up PowerShell and punch in Import-Module ActiveDirectory. Sure beats VB or ADSI Edit, huh?

share|improve this answer
    
Thank you for your guidance. I am going to try and test this in my virt lab and see how it goes. Will post back here. –  floyd Jul 19 '12 at 0:55
    
Hello I can confirm that this works perfectly! Those two hotfixes however are crucial :). Have 2 vms: a 2k3 dc and a win7 client. AD modules installed on win7 client and are managing the 2k3 AD instance. –  floyd Jul 19 '12 at 2:27
    
Also if you happen to have any links for any hacks on getting those AD modules installed on W2k3 server I would appreciate it. –  floyd Jul 19 '12 at 2:28
    
Glad it was helpful. I'll check tomorrow (afternoon, probably) when I get to work and have access to my old work desktop. It's XP, and I ended up finding a way to force all kinds of tools on there that weren't supposed to run on XP, and I did manage AD with Powershell on it, so I should be able to figure out how I did it and give you instructions. (My shiny new Win7 machine arrived a few weeks after I started.) –  HopelessN00b Jul 19 '12 at 2:47
1  
@Floyd: Sorry, false alarm on actually installing the modules on XP/2k3. I couldn't get it done with the hacks and workarounds out at the time, so I used the free Quest approximation. A good alternative if you're somehow still unable to get your hands on a Win7 or Server 2008 host. (quest.com/powershell/activeroles-server.aspx) –  HopelessN00b Jul 19 '12 at 18:59
add comment

Nope. The MS-provided modules described here do require a 2008 R2 domain controller, and ADWS (Active Directory Web Services).

Now, you can still use PowerShell to call dsmod, dsadd, etc ; and there are 3rd-party AD modules as well.

share|improve this answer
    
You sure about that? I have a 2003 FL forest and domain that I manage with the AD Powershell Modules referenced there. Granted, we do have some 2k8 R2 DCs (haven't decommed all those yet), but I was under the impression that the requirement of the AD PowerShell Modules was to run it from Server 2k8 or Win7 and not related to the FL of the domain in question. I'll go check Google, but you could same me some effort if you knew the answer. –  HopelessN00b Jul 19 '12 at 0:08
    
@HopelessN00b did you READ the linked article? It clearly states that you are required to have at least one 2008 R2 DC in the domain to use the Powershell module. In your domain, you have met that requirement, the OP has not... why would you be decommissioning 2008 R2 DCs? –  Cheekaleak Jul 19 '12 at 0:46
    
@Cheekaleak... have you actually checked? See my edit for a technet blog which includes instructions on how to set this up in a domain with a single Server 2003 DC. Great that you can read the line saying it requires a 2008 R2 DC, but in the 2 and a half years since that article, people have successfully managed this without a 2008 DC, including the guy in the Powershell Community thread I linked. Lemme guess, though - you didn't READ what I linked. :/ -- "I'm running a Windows 2003 native AD environment on DCs with Windows 2003 SP2 (no R2 in my environment) and ADWS works great." –  HopelessN00b Jul 19 '12 at 0:58
    
I have confirmed in lab that the instructions I accepted do work. Have two vms a 2k3 DC and a Win7 client. AD modules installed on win7 client and are managing the 2k3 domain. I believe the only requirement is that the AD module code can only be installed on Win7/2k8 OS not what it can actually manage. –  floyd Jul 19 '12 at 2:31
    
@Floyd: Actually, I'm pretty sure that the original requirement for having a 2008 R2 DC relates to the original release of ADGWS/ADWS. As I recall, at first, it could only be installed on 2k8 R2. But now that there's a working version on 2k3 and 2k8 R1, none of the AD PowerShell Module prereqs require a Server 2k8 R2 DC. –  HopelessN00b Jul 19 '12 at 2:39
add comment

Promoting first Domain Controller on Windows server 2012 Core using PowerShell - http://winplat.net/post/2013/06/06/Promoting-first-Domain-Controller-on-Windows-server-2012-Core-using-PowerShell.aspx

share|improve this answer
1  
This is a terribly incomplete answer (check the FAQ for the reason), for an entirely different question than what was asked. You'll probably want to delete this, and lurk on the site just a little bit before posting. –  mfinni Jun 10 '13 at 18:09
add comment

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.