You experience installation errors and compatibility problems when you install Windows Server 2003 management tools on a Windows Vista-based computer

After you install the Windows Server 2003 Administration Tools Pack on a Windows Vista-based computer, the Windows Server 2003 management tools are unavailable. Additionally, you may experience either of the following symptoms:

• You receive the following error message:
  MMC could not create the snap-in.
• Shortcuts for the Windows Server 2003 management tools are not created on the Start menu.

Microsoft Management Console (MMC) could not create the snap-in

This issue occurs because the Administration Tools Pack is not installed by a user who has administrative user rights. New security enhancements in Windows Vista require elevated user rights when a .dll file is registered. Therefore, Windows Vista security enhancements require that certain snap-ins are installed only by a user who has local administrative user rights.

The Windows Server 2003 management tools shortcuts are not created in the Start menu

This issue occurs because the Administration Tools Pack is installed on a different account than the current account.

The following information helps you resolve issues that may occur when you install the Windows Server 2003 Administration Tools Pack on a Windows Vista-based computer. For more information about a specific tool, see the "More Information" section.

MMC could not create the snap-in

To resolve this issue, register the Windows Server 2003 management tools on a domain user account. To do this, follow these steps:

1. Log on to Windows Vista as a user who has local administrator permissions.
2. Create the RegisterAdminPak.cmd script. To do this, follow these steps:
   1. Start Notepad, and then open a blank document.
   2. Paste the following code to the document in Notepad:

      @echo off
      
      REM RegisterAdminPak.cmd
      REM (c) 2006 Microsoft Corporation.  All rights reserved.
      
      set filelist=adprop.dll azroles.dll azroleui.dll ccfg95.dll
      set filelist=%filelist% certadm.dll certmmc.dll certpdef.dll certtmpl.dll
      set filelist=%filelist% certxds.dll cladmwiz.dll clcfgsrv.dll clnetrex.dll
      set filelist=%filelist% cluadmex.dll cluadmmc.dll cmproxy.dll cmroute.dll
      set filelist=%filelist% cmutoa.dll cnet16.dll debugex.dll dfscore.dll
      set filelist=%filelist% dfsgui.dll dhcpsnap.dll dnsmgr.dll domadmin.dll
      set filelist=%filelist% dsadmin.dll dsuiwiz.dll imadmui.dll lrwizdll.dll
      set filelist=%filelist% mprsnap.dll msclus.dll mstsmhst.dll mstsmmc.dll
      set filelist=%filelist% nntpadm.dll nntpapi.dll nntpsnap.dll ntdsbsrv.dll
      set filelist=%filelist% ntfrsapi.dll rasuser.dll rigpsnap.dll rsadmin.dll
      set filelist=%filelist% rscommon.dll rsconn.dll rsengps.dll rsjob.dll
      set filelist=%filelist% rsservps.dll rsshell.dll rssubps.dll rtrfiltr.dll
      set filelist=%filelist% schmmgmt.dll tapisnap.dll tsuserex.dll vsstskex.dll
      set filelist=%filelist% w95inf16.dll w95inf32.dll winsevnt.dll winsmon.dll
      set filelist=%filelist% winsrpc.dll winssnap.dll ws03res.dll
      
      for %%i in (%filelist%) do (
      	echo Registering %%i ...
      	regsvr32 /s %%i 
      )
      
      echo.
      Echo Command Completed
      
      

   3. On the File menu, click Save.
   4. In the Save as type box, click All Files, type C:\Users\UserAccountName\RegisterAdminPak.cmd in the File name box, and then click Save.
      
      Notes
      UserAccountName represents the folder name of the user who is currently logged in.
      
      You must run this script in Windows Vista only.
3. Run RegisterAdminPak.cmd from an elevated command prompt. To do this, follow these steps:
   1. Click Start
      Collapse this imageExpand this image

      
      , click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
      
      
      Collapse this imageExpand this image

      
      If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
   2. At the command prompt, type the following command, and then press ENTER.
      
      Note If you are running a 64-bit version of Windows Vista, type cd %systemroot%\syswow64 before you run the following command.
      C:\Users\UserAccountName\RegisterAdminPak.cmd
      For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site:
      http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx?mfr=true (http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx?mfr=true)

The Windows Server 2003 management tools shortcuts are not created in the Start menu

To resolve this issue, use one of the following methods:

• On an account that is a member of the local Administrator group, install the Administration Tools Pack.
• Start the Windows Server 2003 management tools. To do this, follow these steps:
  1. Click Start
     Collapse this imageExpand this image

     
     , click All Programs, click Accessories, and then click Command Prompt.
  2. At the command prompt, type the command of the tool that you want to run, and then press ENTER.
  
  
  
  Collapse this imageExpand this image

  
  If you are prompted for an administrator password or confirmation, type your password, or click Continue.
• Add the tools that you want by using MMC.

This behavior is by design.

Known issues

When you install the Windows Server 2003 Administration Tools Pack on a Windows Vista-based computer, the following issues occur.

Context-sensitive help

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.

• Iisapp.vbs
• Iisback.vbs
• Iiscnfg.vbs
• Iisftp.vbs
• Iisftpdr.vbs
• Iisvdir.vbs

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: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:

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:
  1. Click Start
     Collapse this imageExpand this image

     
     , type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator.
     
     
     Collapse this imageExpand this image

     
     If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
  2. At the command prompt, type <drive>:\Program Files\CMAK\CMAK, and then press ENTER.
     
     For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site:
     http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx?mfr=true (http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx?mfr=true)
• Right-click the CMAK command or icon, and then click Run as Administrator.

DHCP Server Administration (dhcpmgmt.msc)

An administrator cannot view existing IPv4 scopes and IPv4 super-scopes by using the Administration Tools Pack on a Windows Vista-based computer to connect to a Windows Server 2003 Service Pack 1-based computer. Additionally, an administrator cannot create new IPv4 scopes on a Windows Server 2003 Service Pack 1-based computer.

Note If you do not see the scope information, apply hotfix 935988. For more information about hotfix 935988, click the following article number to view the article in the Microsoft Knowledge Base: