Open Software Solutions

Back to the top

Back to the top

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.

Back to the top

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.

Back to the top

Back to the top

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: a. Start Notepad, and then open a blank document. b. Paste the following code to the document in Notepad: @echo offREM RegisterAdminPak.cmdREM (c) 2006 Microsoft Corporation. All rights reserved.set filelist=adprop.dll azroles.dll azroleui.dll ccfg95.dllset filelist=%filelist% certadm.dll certmmc.dll certpdef.dll certtmpl.dllset filelist=%filelist% certxds.dll cladmwiz.dll clcfgsrv.dll clnetrex.dllset filelist=%filelist% cluadmex.dll cluadmmc.dll cmproxy.dll cmroute.dllset filelist=%filelist% cmutoa.dll cnet16.dll debugex.dll dfscore.dllset filelist=%filelist% dfsgui.dll dhcpsnap.dll dnsmgr.dll domadmin.dllset filelist=%filelist% dsadmin.dll dsuiwiz.dll imadmui.dll lrwizdll.dllset filelist=%filelist% mprsnap.dll msclus.dll mstsmhst.dll mstsmmc.dllset filelist=%filelist% nntpadm.dll nntpapi.dll nntpsnap.dll ntdsbsrv.dllset filelist=%filelist% ntfrsapi.dll rasuser.dll rigpsnap.dll rsadmin.dllset filelist=%filelist% rscommon.dll rsconn.dll rsengps.dll rsjob.dllset filelist=%filelist% rsservps.dll rsshell.dll rssubps.dll rtrfiltr.dllset filelist=%filelist% schmmgmt.dll tapisnap.dll tsuserex.dll vsstskex.dllset filelist=%filelist% w95inf16.dll w95inf32.dll winsevnt.dll winsmon.dllset filelist=%filelist% winsrpc.dll winssnap.dll ws03res.dllfor %%i in (%filelist%) do ( echo Registering %%i ... regsvr32 /s %%i )echo.Echo Command Completed c. On the File menu, click Save. d. 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: a. 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. b. 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)

Back to the top

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, 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. 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.

Back to the top

Back to the top

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:

These UI issues affect the following snap-ins:

Additional issues that affect the Active Directory Users and Computers (Dsa.msc) snap-in

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:

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

Back to the top