The AdminPak (Windows Server 2003 SP1 Administrators Tool Pack) can be installed on Windows Vista, but following installation it is necessary to register some DLLs in order to get the MMC snap-ins to work.
At the end of this narrative you will find the content to copy and paste into a text file which can be renamed to a BAT file.
To install the AdminPak on a Vista machine please do the following.
1. Download and install the executable containing the AdminPak.msi file from: http://download.microsoft.com/download/6/8/1/681c9ba7-380f-4756-ac85-a3323437e6c3/windowsserver2003-kb304718-administrationtoolspack.exe
2. Run the executable and install the Administrative Tools.
3. Run RegisterAdminPak.cmd from an elevated command prompt. To do this, follow these steps:
Click Start , click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
At the command prompt, type C:\Users\UserAccountName\RegisterAdminPak.cmd, and then press ENTER.For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site:
When you install the Windows Server 2003 Administration Tools Pack on a Windows Vista-based computer, the following issues occur.
When you click the ? icon in a property dialog box for all the tools that are included in the Administration Tools Pack, context-sensitive help does not appear.
Cluster administration tools are not supported
Administration of Windows Server 2003 clusters is not supported when you use the Windows Server 2003 management tools directly from a Windows Vista-based computer. This is caused by the network transport protocol that is used by failover clustering in Windows Vista. Windows Server 2003 uses remote procedure call (RPC) over User Datagram Protocol (UDP). Windows Vista uses RPC over TCP. No supported workaround is available.
User interface issues that affect Active Directory directory service snap-ins
The following user interface (UI) issues affect Active Directory snap-ins:
The icons in the results pane disappear after you click the pane.
The icons in the results pane are displayed as rectangles.
These UI issues affect the following snap-ins:
Active Directory Users and Computers (Dsa.msc)
Active Directory Sites and Services (Dssite.msc)
Active Directory Domains and Trusts (Domain.msc)
Additional issues that affect the Active Directory Users and Computers (Dsa.msc) snap-in
You cannot use the drag-and-drop feature in the Active Directory Users and Computers snap-in or in the Active Directory Sites and Services snap-in. For example, if you create a computer object in the Users OU, and then you drag the object to the Computers OU, the operation fails.
The Properties dialog box for users is missing the Terminal Services Profile tab.
The Terminal Services Profile tab does not appear.
Certification Authority (Certsrv.msc)
The Certification Authority snap-in cannot display the Certificates Template node.
Microsoft Internet Information Services
The following Microsoft Internet Information Services (IIS) scripts are installed. However, they do not work.
For more information about how to configure IIS by using command-line tools, visit the following Web site:
Windows Internet Name Service (WINS) (Winsmgmt.msc)
When you create or edit a static mapping, you receive the following error message:
The stub received bad data
However, you can safely ignore this error message because the operation is successful.
Terminal Services Licensing (Licmgr.exe)
When you try to start a Terminal Server license server, you receive the following error message:
The License Server Activation Wizard cannot start. Close one or more programs, and then retry the operation.
Terminal Server Administrator (Tsadmin.exe)
The Terminal Server Administrator tool does not work on a Windows Vista-based computer because of an access violation. To work around this issue, run Remote Desktop from a Windows Vista-based computer, and connect to another computer that can use Tsadmin.exe. For example, connect to a Microsoft Windows XP-based or a Windows Server 2003-based computer that has the Administration Tools Pack installed.
Remote Storage Remote Administration tool
The Remote Storage Remote Administration tool (RSAdmin.msc) is not supported in Windows Vista.
The Connection Manager Administration Kit
In the Administration Tools Pack, you must start the Connection Manager Administration Kit (CMAK) by using one of the following methods:
Run CMAK from an elevated command prompt. To do this, follow these steps:
Click Start , type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator.If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
At the command prompt, type CMAK, and then press ENTER.For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site:
Right-click the CMAK command or icon, and then click Run as Administrator.
Note If you start CMAK from a non-elevated command prompt or by double-clicking the CMAK icon, you receive the following error message:
To continue you must have read/write permissions to the directory Program Files\CMAK\Profiles.
Copy and paste the following into a text file, and then save it as RegisterAdminPak.txt and then rename to RegisterAdminPak.cmd Then follow the instructions above.
regsvr32 /s adprop.dllregsvr32 /s azroles.dllregsvr32 /s azroleui.dllregsvr32 /s ccfg95.dllregsvr32 /s certadm.dllregsvr32 /s certmmc.dllregsvr32 /s certpdef.dllregsvr32 /s certtmpl.dllregsvr32 /s certxds.dllregsvr32 /s cladmwiz.dllregsvr32 /s clcfgsrv.dllregsvr32 /s clnetrex.dllregsvr32 /s cluadmex.dllregsvr32 /s cluadmmc.dllregsvr32 /s cmproxy.dllregsvr32 /s cmroute.dllregsvr32 /s cmutoa.dllregsvr32 /s cnet16.dllregsvr32 /s debugex.dllregsvr32 /s dfscore.dllregsvr32 /s dfsgui.dllregsvr32 /s dhcpsnap.dllregsvr32 /s dnsmgr.dllregsvr32 /s domadmin.dllregsvr32 /s dsadmin.dllregsvr32 /s dsuiwiz.dllregsvr32 /s imadmui.dllregsvr32 /s lrwizdll.dllregsvr32 /s mprsnap.dllregsvr32 /s msclus.dllregsvr32 /s mstsmhst.dllregsvr32 /s mstsmmc.dllregsvr32 /s nntpadm.dllregsvr32 /s nntpapi.dllregsvr32 /s nntpsnap.dllregsvr32 /s ntdsbsrv.dllregsvr32 /s ntfrsapi.dllregsvr32 /s rasuser.dllregsvr32 /s rigpsnap.dllregsvr32 /s rsadmin.dllregsvr32 /s rscommon.dllregsvr32 /s rsconn.dllregsvr32 /s rsengps.dllregsvr32 /s rsjob.dllregsvr32 /s rsservps.dllregsvr32 /s rsshell.dllregsvr32 /s rssubps.dllregsvr32 /s rtrfiltr.dllregsvr32 /s schmmgmt.dllregsvr32 /s tapisnap.dllregsvr32 /s tsuserex.dllregsvr32 /s uddi.mmc.dllregsvr32 /s vsstskex.dllregsvr32 /s w95inf16.dllregsvr32 /s w95inf32.dllregsvr32 /s winsevnt.dllregsvr32 /s winsmon.dllregsvr32 /s winsrpc.dllregsvr32 /s winssnap.dllregsvr32 /s ws03res.dll