You cannot use the Get-ADComputer Powershell cmdlets on a Windows 2003 Server; you can instead run it from a member Server running Windows 2008 R2 or above / client machines running Windows 7 or above
There are a series of steps to follow before you can achieve this
- Your Domain Controller running Active Directory on Windows 2003 should be minimum on SP2
- You will need to install Microsoft .NET Framework 3.5 SP1 on your windows 2003 Server
- Download and Install the Active Directory Management Gateway Service
- When installing if you locate below error in log file you will need to download and install a hotfix
- Possible Error Message when installing Active Directory Managment Gateway Service (C:\WINDOWS\Assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\3.5.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll is Less Than 3.5.30729.4126)
- Link to Hotfix for correcting above mentioned error
- Restart the Windows 2003 Server
- Once the server is restarted; proceed to services and ensure the Active Directory Web Services is started. Change the startup to Automatic

Remotely Running Get-AdComputer Powershell Commands from Windows 7 Client
- Download and Install Install the Remote Server Administration Tool for Windows 7
- Once Installed; proceed to Control Panel -> Programs and Features -> Turn Windows Features on or off
- Enable the Active Directory Module for Windows Powershell as illustrated below

- You can now import the Active Directory Module in your Powershell Session within Windows 7 Client
import-module activedirectory
Remotely Running Get-AdComputer Powershell Commands from Windows 2008 R2 Member Server
- Open Server Manager – Features – Add Features
- Ensure that the Active Directory module for Windows Powershell is enabled as illustrated below

- You can now import the Active Directory Module in your Powershell Session within Windows 2008 R2 Member Server
import-module activedirectory