How To Install Windows Remotely

Setting Upwards a Windows Remote Installation Services Server

The N1 Organisation Manager Bone provisioning process uses the Microsoft Remote Installation Services (RIS) engineering science to provision Windows operating systems to manageable servers from a RIS server. To provision Windows operating systems to manageable servers, you lot must gear up up a RIS server that is accessible to the N1 System Manager equally described in the following sections. For more data nearly RIS, come across the Microsoft RIS documentation at http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/c62e5951-5eb9-42f1-95ae-490e5d7a5551.mspx.

Setting up the Windows RIS server consists of the following tasks:

• To Set Upward the Windows RIS Server

• To Set the BIOS Boot Lodge on a Manageable Server

• To Prepare Up a Windows Paradigm on the Windows RIS Server

To Fix the Windows RIS Server

Steps

1. Install Windows 2003 Enterprise Edition operating system for 32–bit systems with Service Pack one on the Windows RIS server.

   Create a split NTFS segmentation that contains 800 Mbytes for each Windows operating system image that you want to provision. The Windows OS image partitioning should be on a drive or logical division other than the C: drive. You will prompted for the sectionalisation data when you configure the N1 System Director.

   ---

   Note –

   If you already have a automobile that is running Windows 2003 Server 32-fleck Enterprise edition without Service Pack one, you can install just the Windows 2003 Service Pack i on the server See Microsoft Noesis Base Commodity #891128.

   ---

2. Install and configure Active Directory Server on the RIS server.

   During installation of Active Directory Server software on your RIS server, identify your RIS server equally a domain controller. For information well-nigh Active Directory Server, see Microsoft Knowledge Base of operations Article 324753

3. Install and configure the RIS server software on the RIS server.

   For more data, run into Microsoft Knowledge Base Article 325862.

   ---

   Notation –

   While installing RIS server, add a Windows 2003 x64 Risetup.exe image or the Windows 2003-Service Pack 1 x86 Risetup.exe paradigm on the RIS server.

   If the Windows Server 2003 SP1 RISETUP image is the first image to exist uploaded to the RIS server, the new OS chooser screen (x8664.osc ) is copied to the RIS server by default.

   If there are existing Windows Bone images on the RIS server at the time the commencement Windows Server 2003 SP1 prototype is added, y'all must choose whether to overwrite (or backup and overwrite) the Bone chooser screens during the installation to get the new screen. See Microsoft Cognition Base of operations Article #891128.

   ---

4. Install Cygwin© on the RIS Server and configure Open Secure Vanquish Service (OpenSsh service) for Windows 2003 on the RIS server as n1smssh user.

   For more than information, see the Cygwin Dwelling house Page and the Open Ssh Windows Install Instructions. For information about removing existing Cygwin packages, come across http://cygwin.com/faq/faq_2.html#SEC20.

   The Cygwin install source is located in the install media Windows directory.

To Ready a Windows Image on the Windows RIS Server

Steps

1. Log onto the Windows RIS server using the ambassador account or an account with administrator privileges.

2. Copy the Windows distribution from a CD or Network Share to the RIS server CIFS.

   On the RIS server, re-create the windows distribution either from a CD or Network Share using the RiSetup.exe utility with the -add choice onto the RIS Server Common Cyberspace File Organization (CIFS) share.

   ---

   Note –

   Make sure you lot select the option "Go along the old existing OSC files" in the risetup sorcerer while creating RIS images.

   When you re-create a Windows distribution to the RIS server, the appropriate Windows drivers are copied automatically. To add together other drivers into the distribution, copy the drivers into the scripts directory on the RIS server.

   Do non use the Microsoft Developers Network (MSDN) Combination CDs to create a RIS Image. RIS image cosmos will neglect, and you lot will get an error message that is described in the Microsoft Knowledge Base Article #300556. To resolve this result, use a retail version of the OS image beingness created.

   ---

   To create a RIS prototype of a Windows distribution integrated with service packs, follow the procedures described in the post-obit articles:

   • How to create a RIS prototype with the service pack bundled is explained in Service Pack 3 Installation and Deployment Guide for Windows 2000 Server edition. Similar guides can be plant in Microsoft documentation for other Os version service packs likewise.

   • How to obtain the latest Windows 2000 service pack is explained in Microsoft Knowledge Base Article #260910

     Cull "Network installation" option for Windows Service Pack Express/Network Installation for downloading a service pack to create a RIS image. Windows 2000 Service pack 3 download process is explained in http://www.microsoft.com/Windows2000/downloads/servicepacks/sp3/download.aspx. Similar download pages can be found in Microsoft documentation for other OS version service packs also.

3. (Optional) To provision non-English language versions of the Windows OS, you demand to do some boosted configuration when you set up the prototype on the RIS server.

   Basically, the RIS server assumes that you have files in an English path. To resolve this issue, copy the other language's files to the English language path.

   1. Go to the directory in which the Bone Chooser files live.

      For example:

      
      

      %                                          cd RemoteInstall\OSChooser                                      

   2. Re-create the files from the linguistic communication directory to an English directory.

      For example:

      
      

      %                                          copy -r Japanese English                                      

      This creates a directory RemoteInstall\OSChooser\English that contains the install screens in the native language. When the RIS software looks into the default English path, it will display the not-English OS Chooser screens during install.

To Set the BIOS Kicking Order on a Manageable Server

Before You Begin

Ensure that the Windows operating arrangement is supported on each target manageable server. For a list of manageable servers that back up the Windows operating system, see Tabular array 2–6.

Steps

1. Gear up the BIOS Settings on the target host in the following order:

   1. Kicking from Hard Disk

   2. Boot from Network (PXE-enabled)

   3. Boot from CD

   4. Kicking from Floppy

2. Identify the target host'due south primary NIC MAC address for a PXE network boot and the Globally Unique Identifier (GUID) value.

   You can obtain the GUID from the target host'south BIOS settings or from any of the following other sources:

   • A label on the side of the computer case.

   • A label within the reckoner case.

   • The basic input/output organisation (BIOS) of the customer computer.

   • Network traffic from the client estimator. You tin use a network utility to sniff the network traffic and locate the DHCPDiscover packet. That field will contain the 128-scrap, 16-byte GUID or a 128 bit Universally Unique IDentifier (UUID).

   ---

   Annotation –

   The GUID must be in the form {dddddddd-dddd-dddd-dddd-dddddddddddd}, where d is a hexadecimal text digit. For example, {921FB974-ED42-11BE-BACD-00AA0057B223}. Valid entries for the customer GUID are restricted to the numbers 0 through 9, lowercase alphabetical characters, capital alphabetical characters, and a nuance.

   ---

   ---

   Caution –

   Spaces, underscores, and other special symbols are not permitted in a GUID nor in a UUID.

   ---

Source: https://docs.oracle.com/cd/E19957-01/819-5134/osp-win-setup/index.html

Posted by: dvorakbefave.blogspot.com

Share this post