From the General tab, you can enter the IP address or fully qualified domain name FQDN of the computer you wish to connect to within the Computer field.
If you use the default menu shown in Figure A the remote computer will prompt you for a username and password. However, from the General tab, you can specify the username, password and domain in the appropriate fields and skip the logon process. Saving this information makes quick work of logging on to remote connections, such as those used often by employees wishing to connect to their office desktops from home.
The Display tab, shown in Figure D provides options for configuring the desktop size. Use the Local Resources tab, shown in Figure E to set sound, keyboard and local device options. For example, you can configure remote system events to generate sounds on the local PC by selecting Bring To This Computer within the drop down box within the Remote Computer Sound section or automatically connect to remote printers, disk drives and even serial ports by selecting the respective checkbox from within the Local Devices section.
The Programs tab, shown in Figure F , permits users to trigger a specific program upon establishing the remote connection. Windows Remote Desktop Connecting to a remote desktop is fairly straightforward, but a few elements must be in place first: The host desktop must have Internet access preferably high-speed.
The local system the PC connecting to the remote desktop that will serve as the host must be running Windows XP Professional or a Windows flavor server or have the appropriate Terminal Services tools installed.
Firewalls between the local system and the remote host must be configured to pass the appropriate traffic. Remote Desktop must be installed and enabled on the target system. To install it on a host system to enable a computer to accept a remote connection request , Microsoft recommends you: Click Start.
Click Control Panel. Select Add Or Remove Programs. Select Internet Information Services. Click the Details button. Select World Wide Web Service. Check the Remote Desktop Web Connection checkbox. Click OK. This creates a file named Remboot. This filename is confirmed to you at step 25 of Step by Step 2.
Remember the names of the various answer files You can modify the Ristndrd. Also remember that Winnt. After you have prepared the appropriate images on the RIS server, remote users can access this server and use the Client Installation Wizard, which is a text-based wizard that walks them through the process of installing Windows XP Professional.
This wizard uses Plug and Play to detect hardware differences between the reference computer and the computer on which it is installing Windows XP. If the remote computer is not equipped with a PXE-compliant NIC, insert the remote boot floppy and turn the computer on. When you receive the logon prompt, use an existing domain account and password to log on to the network see Figure 2.
You need to log on with a domain user account with privileges to add the computer account to the domain. The wizard presents the menu shown in Figure 2. Select an operating system from the available options, if more than one option is displayed. When more than one operating system image is present, the wizard presents you with a choice of images. Press Enter to accept the warning message that informs you that the hard disk will be formatted and all data will be erased. Having completed the Client Installation Wizard, Windows XP Professional Setup proceeds to install the operating system together with configured service packs, hotfixes, and applications without further intervention.
Challenge You are a consultant who is on the short bidding list for a contract that involves rolling out new Windows XP Professional computers to a company opening a new office in Phoenix. The company has provided you with a computer running a basic installation of Windows Server and another computer with a basic installation of Windows XP Professional.
You are responsible for completing all the steps necessary to perform this task and prove to the CIO that you are the right person to handle the rollout. You need three computers for this exercise, one running Windows Server or Windows Server , one running Windows XP Professional, and one with no operating system installed.
These computers should not have any data of value stored on them. You should try to work through the required steps on your own. Those of you who are unfamiliar with the procedures required that involve configuring the server may want to consult one of the training guides available for the Microsoft and exams. If you need further guidance, follow the steps presented here:.
Follow the steps presented by the Active Directory Installation Wizard. You should create the first domain in a new forest, and accept the option to install DNS on this computer. On the Windows Component Wizard, select Remote Installation Services, ensuring that the check box for this item is selected.
Follow the instructions presented by the New Scope Wizard. Do not add any exclusion, and accept the default lease duration. Do not configure any additional DHCP options. See Step by Step 2. After you click Finish to complete this wizard, go to the Windows XP Professional computer while you are waiting for the copying stage to complete.
On the Windows XP Professional computer, install SP2 and one or more applications that might be typical of what users will require in their everyday tasks. Follow the instructions presented by the Remote Installation Preparation Wizard. If you need assistance, see Step by Step 2. When the Windows XP Professional computer shuts down, move to the third computer. Review the information on the summary page and press Enter to install Windows XP Professional on this computer.
You should be aware of the following major points:. You can use Setup Manager to create answer files that supply answers to questions asked by the Windows XP Professional setup program. As well as the answer file, Setup Manager creates a uniqueness database file that contains information specific to each computer being installed and a batch file that simplifies installation on target computers. The answer file is a text file that you can prepare or edit, using a text editor such as Notepad.
Microsoft recommends that you use the Setup Manager to create this file so that you avoid syntax errors. RIS enables users to connect to a remote installation server and download an image of Windows XP Professional, complete with service packs and applications.
Previous page. Table of content. Next page. Install Windows XP Professional by using Remote Installation Services RIS First introduced with Windows , RIS provides a means of performing on-demand, image-based installation of operating systems across a network connection from a server running RIS to the computer on which the operating system is to be installed.
RIS simplifies the duties associated with management of an installation server. The capabilities of RIS include the following: Enable users to install an operating system on demand. Exam Alert Be sure you know these requirements for using RIS You might encounter a question where you are asked to troubleshoot why RIS isn't working, when the reason is that one of these services is missing. Log on to a computer running Windows Server as an administrator.
When the completion screen appears, click Finish. If requested, click Yes to restart the server. Click Next to bypass the welcome screen of the Check Server Wizard. 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.
Most of the tools in the Windows Adminpak can remotely administer Windows in addition to 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.
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
0コメント