2003 administrative tools xp

Where interoperability problems exist between operating systems, perform administrative tasks from a server that has Terminal Server or Terminal Services enabled and that is running the same operating system as the remote computer that is being administered. Use command-line tools and scripts to locally and remotely administer computers that are running Windows Server , Windows XP, or Windows Where interoperability problems exist between operating systems, perform administrative tasks on the console of the target computer or on a designated computer for administrative tasks that is running the same operating system as the remote computer that is being administered.

However, the tools are not guaranteed to work correctly in this scenario. Tools that are known to have issues include the following:. If you want to run these tools against a Windows Server SP2-based computer, we recommend that you run them from a computer that is running Windows Server SP2.

To make the remote management of your servers easier, Microsoft has included typically used graphical administrative tools in a self-extracting file that is named Adminpak. Note On bit versions of Windows Server , this file is called Wadminpak. Most of the tools in the Windows Adminpak can remotely administer Windows in addition too the bit and bit versions of Windows XP Professional and the bit and bit versions of Windows Server 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.

Note 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. For more information, click the following article number to view the article in the Microsoft Knowledge Base:. You cannot install the Windows Adminpak.

These tools no longer work on these operating systems and are not supported. If you try to install the Windows Server Administration Tools Pack on a Windows based computer, you receive the following error message:. 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:. Complete this upgrade, and then immediately install the Windows Server Administration Tools Pack by running the Adminpak.

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

The original-release version of the Windows Server Adminpak. You can install the Service Pack 1 version of the Windows Server Administration Tools Pack on computers that are running the following operating systems:.

You can install the Service Pack 2 version of the Windows Server Administration Tools Pack on computers that are running the following operating systems:. Note 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. To do this, visit the following Microsoft Web site:. Remove earlier versions of the Administration Tools Pack.

You must remove earlier versions of the Administration Tools Pack before you can install a later version, including the final release. Install the Administration Tools Pack. 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:.

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 The information gathered may enable Pearson but not the third party web trend services to link information with application and system log data.

Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services. This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising.

Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site. Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time. If a user's personally identifiable information changes such as your postal address or email address , we provide a way to correct or update that user's personal data provided to us.

This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service informit. Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT.

If you choose to remove yourself from our mailing list s simply visit the following page and uncheck any communication you no longer want to receive: www. While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest pearson.

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services. This web site contains links to other sites.

Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site. Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way.

Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

This chapter covers the wealth of tools and options available to administrators in Windows Server , including many enhancements to tools that existed in previous versions of the system. This chapter is from the book. The default level of encryption for remote sessions The default level of encryption for remote sessions is bidirectional bit.

Preventing Eavesdropping For security purposes, when you are using the console mode of remote administration, the physical console of the server is automatically locked to prevent eavesdropping. Overview Pearson Education, Inc. Collection and Use of Information To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including: Questions and Inquiries For inquiries and questions, we collect the inquiry or question, together with name, contact details email address, phone number and mailing address and any other additional information voluntarily submitted to us through a Contact Us form or an email.

Surveys Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Contests and Drawings Occasionally, we may sponsor a contest or drawing. Newsletters If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information informit.

Service Announcements On rare occasions it is necessary to send out a strictly service related announcement. Customer Service We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information Application and System Logs Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Web Analytics Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. Cookies and Related Technologies This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising.

Security Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure. Children This site is not directed to children under the age of Marketing Pearson may send or direct marketing communications to users, provided that Pearson will not use personal information collected or processed as a K school service provider for the purpose of directed or targeted advertising.

Such marketing is consistent with applicable law and Pearson's legal obligations. 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.

You can configure the remote access policy administration model in the Remote Access Policies node of the Routing and Remote Access snap-in when the domain is configured in Windows native mode or a later version. Or, log on to the console of a Windows Server based computer or of a Windows based computer to configure these settings directly. Windows XP-based computers that are joined to Windows based domain controller domains do not support the enhanced functionality to select multiple users and to make bulk edits for attributes such as the home folder and the profile path.

The multiple-select functionality is supported in forests where the schema version is 15 or later versions. Because of extensive schema changes, you cannot use Windows XP Professional-based clients to administer Windows based computers, and you cannot use Windows based clients to administer Windows Server based computers. To administer Windows Server based computers, perform remote administration from the console or from a Terminal Services session on the destination computer, or use Windows based clients to manage Windows Server-based computers and Windows XP-based and Windows Server based clients.

We do not recommend cross-version administration from Windows to Windows Server because this does not produce Windows XP profiles. To work around this problem, access the DNS server through a host name instead of through an IP address. This issue applies to the original-release version of the Windows Server Administration Tools Pack. The original release version of Windows Server Adminpak. By default, a warning dialog box is presented when you try to perform a drag-and-drop operation.

You can dismiss the warning dialog box for the session. However, the dialog box will appear again the next time that you start the snap-in. You can disable drag-and-drop capabilities by setting the first part of the DisplaySpecifiers attribute to 0 zero in the configuration naming context in Active Directory.

Because this is a forest-wide setting, drag-and-drop capabilities will be disabled for every domain in the forest.