How do I administer Windows Server 2003 based computers?
To administer Windows Server 2003-based computers, perform remote administration from the console or from a Terminal Services session on the destination computer, or use Windows 2000-based clients to manage Windows 2000 Server-based computers and Windows XP-based and Windows Server 2003-based clients.
Can Windows Server 2003 administration tools run on Windows 2000?
The Windows Server 2003 Administration Tools package cannot be installed or run on Windows 2000-based computers. Similarly, the command-line utilities from the Windows Server 2003 Administration Tools package are designed to run on Windows XP and the Windows Server 2003 family only.
Where is the Windows Server 2003 administration tools pack located?
The Windows Server 2003 Administration Tools Pack is located in the I386 folder of the Windows Server 2003 CD and is available as a free download on www.microsoft.com.
What is Windows Server 2003 & Windows 2000 installation media?
Windows Server 2003 and Windows 2000 installation media contain command-line and graphical administrative tools that can be used to locally and in most cases remotely administer up-level and down-level operating systems with a high degree of interoperability.
Overview
This article describes how to remotely administer computers by using the Administration Tools Pack. Applies to: Windows 10 - all editions, Windows 7 Service Pack 1, Windows Server 2012 R2 See full list on learn.microsoft.com
Summary
This article describes options to administer computers that are running Windows Server 2003, Windows XP, or Microsoft Windows 2000. Additionally, this article discusses how to download the Windows Server 2003 Administration Tools Pack (Adminpak). This article also discusses the various compatibility issues that occur when you remotely administer Wi
Introduction
The following topics are discussed in this article: •Options to remotely administer computers that are running Windows Server 2003, Windows XP, or Windows 2000. •Download locations for the original-release (RTM), Service Pack 1, and Service Pack 2 versions of the Windows Server 2003 Administration Tools Pack •Issues that are specific to the administration of 64-bit versions of Windows •Compatibility issues that occur when Windows 2000 Professional-based computers that have Windows 2000 administration tools installed are upgraded to Windows XP. •Compatibility issues that occur when Windows 2000-based domain controllers are upgraded to Windows Server 2003-based domain controllers. See full list on learn.microsoft.com
More information
Known issues for the Windows Server 2003 original-release version of Adminpak.msi Installation and upgrade issues Windows Server 2003 Winnt32.exe and the Winnt32 /checkupgradeonly process on Windows 2000 domain controllers report that Adminpak.msi is installed when it was never installed or when it has already been removed. This issue occurs because the Active Directory Installation Wizard (Dcpromo.exe) in Windows 2000 uses an internal feature of the Windows 2000 version of Adminpak.msi to install menu shortcuts on domain controllers. You can safely ignore this warning in Winnt32.exe and continue the upgrade. After the upgrade is complete, install the Windows Server 2003 version of Adminpak.msi from the I386 folder of the installation media to make sure that you have the latest version of the domain administration tools. Active Directory Domains and Trusts •The original-release version of the Windows Server 2003 Administration Tools Pack introduces Lightweight Directory Access Protocol (LDAP) signing. Windows 2000 domain controllers that are being remotely administered by Windows 2000-based computers that are running Service Pack 4 (SP4), by Windows XP-based computers, or by Windows Server 2003-based computers that are using NTLM authentication must have Windows 2000 Service Pack 3 installed. If you use a Windows 2000-based computer to administer Windows Server 2003-based domains, you do not see advanced user interface (UI) features that are supported by Windows Server 2003-based domains. For example, you do not see domain and forest functionality or advanced trusts. Active Directory Schema •The original-release version of the Windows Server 2003 Administration Tools Pack introduces LDAP signing. Windows 2000 domain controllers that are being remotely administered by Windows 2000-based computers that are running Service Pack 4 (SP4), by Windows XP-based computers, or by Windows Server 2003-based computers that are using NTLM authentication must have Windows 2000 SP3 installed. •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 2003-based domain controllers. Active Directory Sites and Services •The original-release version of the Windows Server 2003 Administration Tools Pack includes LDAP signing. Windows 2000 domain controllers that are being remotely administered by Windows 2000-based computers that are running Service Pack 4 (SP4), by Windows XP-based computers, or by Windows Server 2003-based computers that are using NTLM authentication must have Windows 2000 SP3 installed. •There is no support for editing certificate templates. •When you click Show Services Node on the View menu, the Services Node enabled command has been removed on Windows XP clients. •When the Service Pack 1 version of Active Directory Sites and Services is started on 64-bit systems, it may not edit Group Policy. Additionally, you receive the following error message: Windows cannot find gpedit.msc. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search. Modify the syntax of your command line or shortcut to use the following syntax: %windir%syswow64mmc.exe %systemroot%system32dssite.msc -32 •There are no known issues when Windows 2000-based forests are administered from Windows Server 2003-based clients or from Windows XP Professional-based clients. Active Directory Users and Computers •The original-release version of the Windows Server 2003 Administration Tools Pack includes LDAP signing. Windows 2000 domain controllers that are being remotely administered by Windows 2000-based computers that are running Service Pack 4 (SP4), by Windows XP-based computers, or by Windows Server 2003-based computers that are using NTLM authentication must have Windows 2000 SP3 installed. •The Dial-in tab that configures Routing and Remote Access dial-in or VPN access and callback settings is removed when the original-release version of the Administration Tools Pack is installed on Windows XP-based clients. Fixes or workarounds for this problem include the following: •Install Q837490 on the pre-Service Pack 2 Windows XP-based client. This hotfix adds the remote access dial-in tab on pre-Service Pack 2 Windows XP-based clients that are running the original-release version of the Windows Server 2003 Active Directory Users and Computers snap-in, Dsa.msc, that is installed by the original-release version of the Windows Server 2003 Adminpak.msi. •Install the Windows Server 2003 Service Pack 2 version of Adminpak on Windows XP-based computers that have Windows XP Service Pack 2 or later versions installed. •Use Remote Access Policy. •Start Active Directory Users and Computers from a Windows Server 2003-based computer or from a Windows 2000-based computer that is accessed over Terminal Services or Remote Desktop Access. •Start Active Directory Users and Computers from the console of a Windows Server 2003-based computer or of a Windows 2000-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 2000 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 2003-based or Windows 2000-based computer, or log on to the console of a Windows Server 2003-based computer or of a Windows 2000-based computer to manage the Dial-in tab. The remote access policy administration model has the following benefits: •Detailed administration 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. •Groups for access control 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. •Precise connection-specific Access Policy control 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 2000 native mode or a later version. To remotely manage the remote access dial-in tab in Active Directory Users or Computers or in Internet Authentication Server (IAS) from a Windows XP-based computer, use Terminal Services or Remote Desktop to access a Windows Server 2003-based or Windows 2000-based computer. Or, log on to the console of a Windows Server 2003-based computer or of a Windows 2000-based computer to configure these settings directly. •Windows XP-based computers that are joined to Windows 2000-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. For example, executing the Windows Server 2003 ADDPREP /ForestPrep and /DomainPrep in a Windows 2000-based forest and domain would enable multiple-selection support on systems that have the Windows Server 2003 Active Directory Users and Computers snap-in installed. •When the Service Pack 1 version of Active Directory Users and Computers is started on 64-bit systems, it may not always edit Group Policy. Additionally, you receive the following error message: Windows cannot find gpedit.msc. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search. Modify the syntax of your command line or shortcut to use the following syntax: %windir%syswow64mmc.exe %systemroot%system32dsa.msc -32 back Authorization Manager This has been added to the Administration Tools Pack in the Windows Server 2003 RC1 version and later versions. Certification Authority Because of extensive schema changes, you cannot use Windows XP Professional-based clients to administer Windows 2000-based computers, and you cannot use Windows 2000-based clients to administer Windows Server 2003-based computers. To administer Windows Server 2003-based computers, perform remote administration from the console or from a Terminal Services session on the destination computer, or use Windows 2000-based clients to manage Windows 2000 Server-based computers and Windows XP-based and Windows Server 2003-based clients. Cluster Administrator If you are using Windows XP Professional with Service Pack 2 and the Windows Server 2003 Administration Tools Pack, you cannot administer Cluster servers. However, if you use Windows XP Professional with SP1 and Windows Server 2003 Administration Tools Pack, you can manage Cluster servers. Connection Manager Administration Kit We do not recommend cross-version administration from Windows 2000 to Windows Server 2003 because this does not produce Windows XP profiles. Delegation Wizard No known issues. DHCP •Windows 2000 tools cannot generate a dump file of Windows Server 2003 Dynamic Host Configuration Protocol (DHCP) configurations because of code changes. •There are no new issues in Windows Server 2003 Service Pack 2. Distributed File System (DFS) •Adds ring, hub and spoke, and custom topology support for File Replication Service (FRS) replication of DFS roots and links. •Configures connection priority in the Q321557 and SP3 release of Windows 2000 Ntfrs.exe. •If you are using a Windows XP-based client, you must use the Windows XP SP1 update to administer Windows Server 2003 DFS. •Adminpak now includes the Windows Server 2003 DFS Server Help file. DNS When you access a Domain Name System (DNS) server through an IP address, some information that is returned, such as Forwarder information, will be incorrect. 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 2003 Administration Tools Pack. Directory Service command-line utilities The original-release version of the Windows Server 2003 Administration Tools Pack includes LDAP signing. Windows 2000 domain controllers that are being remotely administered by Windows 2000-based computers that are running Service Pack 4 (SP4), by Windows XP-based computers, or by Windows Server 2003-based computers that are using NTLM authentication must either have Windows 2000 SP3 installed. Drag-and-drop functionality of Active Directory snap-ins The original release version of Windows Server 2003 Adminpak.msi added drag-and-drop capabilities to the following snap-ins: •Active Directory Users and Computers •Active Directory Sites and ServicesBe careful that you do not accidentally or unknowingly move organizational units (OUs) under different parent OUs. This action may have the following results: •User and computer accounts do not apply Group Policy as expected. Specifically, Group Policy objects (GPOs) that are applied to user and computer accounts may no longer apply because of a different OU hierarchy or because new GPOs may now apply that are based on the objects' new location. The application or nonapplication of Group Policy may affect the operating system behavior. For example, access to operating system features and to shared resources on the network may be affected. •Programs that are configured to use hard-coded distinguished name paths may not always locate required objects. Drag-and-drop behavior changes in the Windows Server 2003 SP2 version of Adminpak.msi In the Windows Server 2003 SP2 version of Adminpak.msi, two new options are available to control drag-and-drop behavior in the Active Directory Users and Computers snap-in and in the Active Directory Sites and Services snap-in: •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. To disable the drag-and-drop feature, follow these steps: 1.If you have the Active Directory Users and Computers snap-in or the Active Directory Sites and Services snap-in open, close the snap-ins. 2.Click Start, click Run, type adsiedit.msc in the Open box, and then click OK. 3.Expand Configuration. 4.Expand CN=Configuration,DC=ForestRootName. 5.Right-click CN=DisplaySpecifiers, and then click Properties. 6.In the list of attributes, double-click flags. 7.In the Integer Attribute Editor dialog box, type 1 in the Value box. 8.Click OK two times. 9.Close ADSI Edit. Microsoft Exchange •The Microsoft Exchange Simple Mail Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP) DLL files were added to Adminpak.msi. The additional Staxmem.dll, Smtpapi.dll, Smtpadm.dll, Smtpsnap.hlp, and Nntpsnap.hlp files were added to Adminpak.msi to allow 32-bit Windows XP Professional-based clients to administer the release of Exchange after Microsoft Exchange 2000. •Administration of Exchange-based servers after the Exchange 2000 version from 64-bit clients is not supported. Help •The Ntcmds.chm Help file was added to support command-line administration. •The Windows XP Professional Help files are reinstalled when the Administration Tools Pack is removed. Windows XP Professional versions of the Ntart.chm and Ntcmds.chm files are backed up during the installation of the Administration Tools Pack and are restored during removal. Internet Information Services command-line utilities This section applies to the following utilities: •IisApp.vbs •Iisback.vbs •IisCnfg.vbs •IisFtp.vbs •IisFtpdr.vbs •Iisvdir.vbs •Iisweb.vbs The following issues have been reported: •All scripts are compatible with Microsoft Internet Information Services (IIS) 6.0 only. •IISCnfg: When you use the iiscnfg /export command, the destination file (the file that you specify after the /f switch) is created on the remote computer (the Windows Server-based computer). For example, to export the metabase, type the following command: When you run this command, the D:Config.xml file is created on the remote server. To import the metabase, type the following command: IISCnfg checks that the D:Config.xml file (the file that you specify after the /f switch) exists on both the local and the remote computer (RemoteServer). However, the actual import uses only the file on the remote server. When you import or copy the Config.xml file from the remote server, use the same path on the local computer. Internet Authentication Service The Internet Authentication Service (IAS) snap-in has been removed from the Administration Tools Pack. Netsh •The netsh dhcp server ip dump command output is truncated. The output from this command that is issued from a Windows Server 2003-based computer against a Windows Server 2003-based DHCP server returns the following output: The same command that is issued from a Windows XP-based client is truncated as follows: •By default, the netsh dhcp server command does not run from Windows XP-based clients. For example, the following command runs successfully from a Windows Server 2003-based computer but does not run from a Windows XP-based client: Dhcp Server 157.59.136.135 Add Optiondef 101 "String Array" STRING 1 comment="" "hello" "cathy" "jim" "bob" If you run this command from a Windows XP-based client, you receive the following error message: To remotely administer a DHCP server from a Windows XP-based client, install the Administration Tools Pack, and then type the following command at the command prompt: Network Load Balancing Manager •No known issues in the release version of the Windows Server 2003 Adminpak. •The Service Pack 2 Adminpak installs a 32-bit Network Load Balancing Manager that does not bind on 64-bit versions of Windows. Ntdsutil.exe The authoritative restore command in Ntdsutil depends on Ntdsbsrv.dll. Ntdsbsrv.dll is not included in Windows XP Professional or in the Windows Server 2003 Administration Tools Pack. Perform authoritative restores from the console of Active Directory-based domain controllers. If you must run this command on Windows XP-based clients, copy the Ntdsbsrv.dll file from a release version of a Windows Server 2003 installation. Object Picker The original-release version of the Windows Server 2003 Administration Tools Pack introduces LDAP signing. Windows 2000 domain controllers that are being remotely administered by Windows 2000-based computers that are running Service Pack 4 (SP4), by Windows XP-based computers, or by Windows Server 2003-based computers that are using NTLM authentication must have Windows 2000 SP3 installed. Remote Access User Extensions Remote Access User Extensions have been removed from the original-release version of the Windows Server 2003 Administration Tools Pack. The Remote Access User Extensions are available if the version of the Adminpak.msi file that is included in Windows Server 2003 Service Pack 2 (SP2) is installed on your Windows XP Professional-based computer. If you have the RTM or SP1 version of the Adminpak.msi file installed, you must uninstall it and then install the Windows Server 2003 SP2 version. Remote Desktop Connect to Console mode is supported against Windows Server 2003-based and Windows XP-based computers only. Remote Storage •Cross-version administration is not supported. Remote Storage administration from Windows 2000-based computers is not supported against Windows Server 2003-based and Windows XP-based computers. Perform remote administration from a Windows 2000-based computer, from the console of the destination computer, or over a Terminal Services session. •Cross-version administration is not supported. Versions of Windows Server 2003 and Windows XP that are running the Windows Server 2003 Administration Tools Pack cannot administer Windows 2000-based computers. Perform remote administration from a Windows Server 2003-based computer, from a Windows XP-based computer, from the console of the destination computer, or from a Terminal Services session. Remote Installation Services (RIS) UI Administration Extension No known issues. Routing and Remote Access This has been removed from the Administration Tools Pack. Telephony Telephony administrators cannot administer remote lines on a Windows 2000 Server-based computer from a Windows XP Professional-based computer. Specifically, the Edit users option is unavailable. Terminal Services Licensing Manager No known issues. UDDI No known issues. Windows Server 2003 Administration Tools issues on x64-based versions of Windows Server 2003 When you try to modify a Group Policy on an x64-based version of Windows Server 2003 from the Active Directory Users and Computers snap-in, the Active Directory Sites and Services snap-in, or the Group Policy Management Console snap-in, you receive the following error message: When you try to modify a GPO from any one of the snap-ins that is listed earlier, a call is made to start the Gpedit.msc file. Currently, the snap-ins that call the Gpedit.msc file are 32-bit tools. However, on x64-based versions of Windows Server 2003, Gpedit.msc is a 64-bit snap-in. This problem will be corrected in a future release of a 64-bit Adminpak.msi package. To work around this problem, use either of the following methods. Method one Modify the GPOs from a computer that is running a 32-bit version of Windows Server 2003, a 32-bit version of Windows XP, or a version of Windows 2000. Method two Use the following commands to start the snap-ins, and then modify the GPOs: •To start the Active Directory Users and Computers snap-in: %windir%syswow64mmc.exe %windir%system32dsa.msc -32 •To start the Active Directory Sites and Service snap-in: %windir%syswow64mmc.exe %windir%system32dssite.msc -32 Installation and upgrade issues Windows Server 2003 Winnt32.exe and the Winnt32 /checkupgradeonly process on Windows 2000 domain controllers report that Adminpak.msi is installed when it was never installed or when it has already been removed. This issue occurs because the Active Directory Installation Wizard (Dcpromo.exe) in Windows 2000 uses an internal feature of the Windows 2000 version of Adminpak.msi to install menu shortcuts on domain controllers. You can safely ignore this warning in Winnt32.exe and continue the upgrade. After the upgrade is complete, install the Windows Server 2003 version of Adminpak.msi from the I386 folder of the installation media to make sure that you have the latest version of the domain administration tools. See full list on learn.microsoft.com
PROJET : RÉSUMÉ DU PLAN DE GESTION ENVIRONNEMENTALE ET
RÉSUMÉ DU PLAN DE GESTION ENVIRONNEMENTALE ET SOCIALE (PGES)
RESUME DU PLAN DE GRSTION ENVIRONNEMENTALE & SOCIALE (PGES)
Plan de gestion environnementale et sociale de l’entreprise
RÉSUMÉ DU PLAN DE GESTION ENVIRONNEMENTALE ET SOCIALE
Résumé du plan de gestion environnemental et social
PROJET DE DEVELOPPEMENT COMMUNAUTAIRE PARTICIPATIF EN MILLIEU
DOCUMENT DE PROJET DU PBF
Des négociations fournisseurs-distributeurs 2020 sous
How to setup up file shares in Windows Server 2003
how to reset the admin password on windows server 2003
