Xp admin tools 2003

Additionally, the table summarizes the operating systems that the Adminpaks from these sources can remotely administer. If you want to remotely administer Windows Server or Windows member-based computers and domain controllers from Windows Server based clients or from Windows XP Professional-based clients, note the following installation issues:. You must remove earlier beta versions of the Windows Server Administration Tools Pack before you install the final release version. In some limited cases, servers must be administered from clients that are running the same operating system.

For example, some remote administration operations against Windows based servers can be performed only from Windows based clients. Similarly, some operations against Windows Server based computers can be performed only from Windows Server based clients or from Windows XP-based clients.

This article documents these limitations or restrictions for each tool that is included in the Administration Tools Pack. If you do not uninstall earlier versions of the Administration Tools Pack Adminpak. You cannot install the Windows Adminpak. These tools no longer work on these operating systems and are not supported. Service pack level mismatch. Obtain the Administration Tools Pack that matches the service pack level of your operating system.

Such a mismatch or error may occur if you copy the utilities to a Windows based computer. If you try to install the Windows Administration Tools Pack on a Windows Server based computer, you receive the following error message:. Windows Administration Tools are incompatible with Windows Server operating systems. Most Windows Server administration tools work the same as their Windows counterparts. Sometimes, the Windows Server administration tools offer increased functionality with regard to their Windows counterparts.

For example, the new drag-and-drop feature of the Windows Server Users and Computers snap-in is fully functional against Windows based domain controllers. In other cases, increased functionality in Windows Server administration tools is not turned on or is not supported when you administer Windows based computers. For example, features in the administration tools that depend on functionality in Windows Server , such as the "Saved query for last logon time" functionality, are not supported against Windows Server-based computers because earlier-version servers do not have the required server-side support.

In rare cases, Windows Server administration tools are incompatible with Windows Server-based computers and are unsupported for managing those computers. Similarly, in rare cases, Windows administration tools are incompatible with Windows Server based computers. When a Windows based computer that has the Windows Adminpak installed is upgraded to Windows Server or to Windows XP, the System Compatibility Report that is displayed in the upgrade process reports that the Windows administration tools are incompatible with Windows Server or with Windows XP.

If you click Details , you receive the following error message: Setup has detected Windows Administration Tools on your computer. Use one of the following methods:. If the Windows administration tools were left in place when the Windows based computer was upgraded to Windows Server , do not try to remove the Windows Administration Tools icon that appears in the Add or Remove Programs item in Control Panel.

If you try to remove the Windows administration tools by using the Add or Remove Programs tool, you may receive the following error message:. Ignore this error message.

You can install the original-release version of the Windows Server Administration Tools Pack on computers that are running the following operating systems:. You can install the Service Pack 1 version of the Windows Server Administration Tools Pack on computers that are running the following operating systems:. The version of Adminpak that is included in the I folder of the installation media for the bit versions of Windows Server is called Wadminpak.

The Wadminpak. Similarly, you can install Wadminpak. You must remove earlier versions of the Administration Tools Pack before you can install a later version, including the final release. To install the Administration Tools Pack, right-click the.

Alternatively, by using Group Policy, you can use Active Directory to remotely install or to publish the file to a Windows XP-based computer or to a Windows Server based computer when a user logs on to the computer. For more information about how to remotely install the Administration Tools Pack, click the following article numbers to view the articles in the Microsoft Knowledge Base: How to use Group Policy to remotely install software in Windows Server When you upgrade a Windows based server to Windows Server , the system compatibility check in Windows Server Winnt You may safely ignore this message and continue with the upgrade process from Windows to Windows Server Before you contact Microsoft Customer Support Services CSS , see the known compatibility issues that are described in this article, and note the release date of their resolution.

You must remove earlier versions of Adminpak. Confirm that you are using the latest supported version of the Adminpak. You can use the APVer. To do this, change to the folder where you expanded Adminpak. See the known compatibility issues that are described in this article to determine whether the issue is known. Windows Server Winnt You can safely ignore this warning in Winnt After the upgrade is complete, install the Windows Server version of Adminpak.

If you use a Windows based computer to administer Windows Server based domains, you do not see advanced user interface UI features that are supported by Windows Server based domains. For example, you do not see domain and forest functionality or advanced trusts.

The Schema may be modified on this Domain Controller check box has been removed from the Change Schema Master dialog box. By default, schema updates are enabled on Windows Server based domain controllers. Additionally, you receive the following error message:.

Windows cannot find gpedit. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

There are no known issues when Windows based forests are administered from Windows Server based clients or from Windows XP Professional-based clients. Start Active Directory Users and Computers from the console of a Windows Server based computer or of a Windows based computer.

To manage dial-in properties on the user account, use the remote access policy administration model. The remote access policy administration model was introduced in Windows to address the limitations of the earlier dial-in account permission model. The remote access policy administration model uses Windows groups to manage remote access permissions.

Customers who use the recommended administration model that is named "remote access policy administration model," can use the administration package from Windows XP to manage remote access permission for users in Active Directory.

Settings on the Dial-in tab are not typically used for VPN or wireless deployments. There are several exceptions. For example, administrators who deploy dial-up networks may use callback number.

In these cases, use Terminal Services or Remote Desktop to access a Windows Server based or Windows based computer, or log on to the console of a Windows Server based computer or of a Windows based computer to manage the Dial-in tab.

Administrators who manage dial-in permission must also have access to the whole user account. The user account has many more security properties.

In the policy administrative model, a separate group can be created to grant dial-in permissions. Additionally, permissions to manage access to that group can be granted to a different administrator. Most Microsoft Windows programs use groups for access control. Groups reduce the additional attempt of managing separate permissions network access. You can use the same groups for controlling access to dial-up, VPN, wireless network, or file shares.

There are many challenges that are introduced when you are deploying more than one access technology at the same time. The permissions and the settings for dial-up, VPN, and wireless technologies may be different. For example, contractors may be permitted to access wireless networks but may not be permitted to connect from home by VPN. Wireless may require different security settings with regard to VPN and dial-up connections.

Callback settings may be useful when you are connecting from a local area code. However, you may want to disable callback when the user is connecting from an international telephone number. What is your meaning of ''? Till now, there is no Exchange server and Windows Windows 7 itself does not support these tools, but, while not perfect, you still you can run a lot of incompatible bit apps in Windows 7 XP Mode with Virtual PC. I have never tried with the Exchange Administration Tools, but I have done so with games for our children with bit Vista.

The look and feel is that these two environments are quite integrated. I would at least give it a try. Office Office Exchange Server.

Not an IT pro? Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums.