ÇÔ¸Õ¡ÒûÃѺãªéÊÀÒ¾áÇ´ÅéÍÁ Preinstallation ¢Í§ Microsoft Windows ¨Ò¡à«ÔÃì¿àÇÍÃì RIS ÍÔ¹ â´Âãªéä¤Åà͹µì·ÕèÁÕ¡ÒÃà»Ô´ãªé§Ò¹ PXE

º·¤ÇÒÁ¹Õé͸ԺÒÂÇÔ¸Õ¡ÒûÃѺãªéÊÀÒ¾áÇ´·Õè Microsoft Windows Preinstallation ÅéÍÁ (Windows PE) ¨Ò¡à«ÔÃì¿àÇÍÃìÃÐÂÐä¡Å¡ÒõԴµÑ駺ÃÔ¡Òà (RIS) ÊÓËÃѺ¡ÒÃàÃÔèÁµé¹ã¹ÊÀÒ¾áÇ´ÅéÍÁ»ÃÐÁÇÅ Pre-Boot (PXE)

ÁÕÊͧÇÔ¸Õ·Õè¤Ø³ÊÒÁÒöãªéà¾×èÍ»ÃѺãªé Windows PE ¨Ò¡à«ÔÃì¿àÇÍÃì RIS ÇÔ¸Õ¡ÒÃááãªé RAM ´ÔÊ¡ìÍØ»¡Ã³ìãªé§Ò¹ Windows PE ¨Ò¡à«ÔÃì¿àÇÍÃì RIS ÇÔ¸Õ¡Ò÷ÕèÊͧãªéÃٻẺ Windows PE ¨Ò¡ Microsoft Windows XP ËÃ×ÍÃÙ»ÀÒ¾·Õèãªé Microsoft Windows Server 2003 á¼è¹«Õ´Õ ¤Ø³µéͧãªéÇÔ¸Õ¡Ò÷ÕèÊͧ¹Õé¶éҤسÁÕÃØè¹·Õèà¡èÒ¡ÇèҢͧ Windows PE ËÃ×ͶéҤسäÁèÁÕà«ÔÃì¿àÇÍÃì RIS ·Õèãªé Windows Server 2003 ÇÔ¸Õ¡Ò÷ÕèÊͧ¹Õéà»Ô´¡ÒèѴ¡ÒáѺä¿ÅìµèÒ§ æ ¨Ò¡à«ÔÃì¿àÇÍÃì RIS ´Ñ§¹Ñé¹ ÇÔ¸Õ¡ÒùÕéÅ´»ÃÐÊÔ·¸ÔÀÒ¾¡Ò÷ӧҹ¢Í§à«ÔÃì¿àÇÍÃì RIS àÁ×èͤسàÃÔèÁ¡Ò÷ӧҹ¢Í§ÍÔ¹Êáµ¹«ìËÅÒÂÍÔ¹Êáµ¹«ì¢Í§ Windows PE ¹Í¡¨Ò¡¹Õé¤Ø³ÍÒ¨¾º¢éͼԴ¾ÅÒ´¡ÒÃËÁ´àÇÅÒ

ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺÇÔ¸Õ¡ÒûÃѺãªé Windows PE ¨Ò¡à«ÔÃì¿àÇÍÃì RIS ãËé´Ù·Õèá¿éÁ Winpe.chm ÅèÒÊØ´ á¿éÁ¹Õé¶Ù¡ÃÇÁäÇé ¡Ñºá¼è¹«Õ ´Õ Windows PE áÅÐ ¡Ñºá¼è¹«Õ´Õ OEM Preinstallation Kit (OPK)

¡è͹·Õè¤Ø³ãªéÇÔ¸Õ¡Ò÷Õè͸ԺÒÂäÇé㹺·¤ÇÒÁ¹Õé ¤Ø³µéͧÁÑè¹ã¨ÇèÒ ¤Ø³ÁÕÃÒ¡ÒõèÍ仹Õé:

• ¡ÒáÓ˹´àͧ Windows PE ÊÒ¡Åͧ¤ì¡ÃÊÓËÃѺÃÙ» Standardization (ISO) ·ÕèÊÃéÒ§¢Öé¹ ¨Ò¡á¼è¹«Õ ´Õ Windows PE ËÃ×Í ¨Ò¡á¼è¹«Õ´Õ OEM Preinstallation Kit (OPK)
• à«ÔÃì¿àÇÍÃì RIS ·Õèãªé Windows Server 2003 Service Pack 1 (SP1)
• A Windows PE CD or an OEM Preinstallation Kit (OPK) CD.

Method 1: Deploy Windows PE from a RIS server by using a RAM disk

1. On the RIS server, locate the \RemoteInstall\Setup\ÀÒÉÒ\Images folder.
2. Create a subfolder for Windows PE. For example, type the following at a command prompt:
   ä´Ã¿ì:\Cd \RemoteInstall\Setup\English\Images md winpe
   ËÁÒÂà˵Ø:In this step,ä´Ã¿ìis the placeholder of the hard disk drive on which RIS is installed.ÀÒÉÒis the language of the Windows PE image.
3. Create a subfolder in the \Windows PEfolder that is named Platform, whereplatformis i386 or amd64. For example, type the following command at the command prompt:md winpe\i386
4. Copy the customized Windows PE .iso image file that you created earlier to theWindows PE\á¾Å·¿ÍÃìÁfolder, whereplatformis i386 or amd64. For example, type the following command at the command prompt:
   Copyä´Ã¿ì:\Work\Winpex86.isodrive 1:\RemoteInstall\Setup\English\Images\Winpe\i386
   ËÁÒÂà˵Ø:ä´Ã¿ìis the placeholder of the hard disk that contains the Windows PE image. Also,drive 1is a placeholder for the hard disk partition on which RIS is installed.
5. Create a subfolder in the \Windows PE\á¾Å·¿ÍÃìÁfolder that is named Templates. For example, type the following command at the command prompt:
   md winpe\i386\templates
6. Locate the Platform folder of the Windows PE image, and then copy Ntdetect.com and Startrom.com to the Windows PE\á¾Å·¿ÍÃìÁ\Templates folder. For example, type the following commands at the command prompt:
   ä´Ã¿ì:\ cd \winpe\i386 copy ntdetect.com
   drive 1:\RemoteInstall\Setup\English\Images\winpe\i386\templates copy startrom.com
   drive 1:\RemoteInstall\Setup\English\Images\winpe\i386\templates
   
   
   ËÁÒÂà˵Ø:In this step,ä´Ã¿ìis the placeholder of the hard disk that contains the Windows PE image anddrive 1is a placeholder for the hard disk partition on which RIS is installed.
   
7. Copy the \á¾Å·¿ÍÃìÁ\Setupldr.exe (not Setupldr.bin) file from the Windows PE image to the \Windows PE\platform\templatesfolder, and then rename Setupldr.exe to Ntldr. For example, run the following command at the command prompt:
   copy setupldr.exedrive 1:\RemoteInstall\Setup\English\Images\winpe\i386\templates\ntldr
   .
   
   ËÁÒÂà˵Ø:In this step,drive 1is a placeholder for the hard disk partition on which RIS is installed.
8. Create a text file that is named Winnt.sif in the \Windows PE\á¾Å·¿ÍÃìÁ\áÁèẺfolder by using the following text.

   [SetupData]
   BootDevice = "ramdisk(0)"
   BootPath = "\platform\System32\"
   OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=%INSTALLPATH%\%MACHINETYPE%\<bootimage>"
   
   Architecture = "platform" 
    
   [RemoteInstall]
   Repartition = No
    
   [OSChooser]
   Description = "brief description"
   Help = "longer description"
   LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
   ImageType = Flat
   Version = "5.2 (0)"
   

9. Start a RIS client, and then select the operating system image that you created.

ËÁÒÂà˵Ø

• RAM disk method supports only x86 and x64-based Windows PE ISO images. For Itanium (IA-64)-based Windows PE ISO images use Method 2.
• You can put the i386 and amd64 folders within the same folder on a RIS server. For example, you can create the following folder structure:
  \RemoteInstall\Setup\English\Images\Winpe\i386 \RemoteInstall\Setup\English\Images\Winpe\Amd64
• You can give the Winnt.sif file any name that you want as long as the file name extension is .sif.
• The "Repartition = No" entry in the Winnt.sif file avoids a warning from the Client Installation Wizard (OSChooser) about the disk being erased.
• The text for the "Description" and "Help" entries can be any information that you want to include.
• The "LaunchFile" and "ImageType" entries must not change.
• Restart the client, and then go into PXE startup. After you log on, select theMaintenance and Troubleshootingoption in the Main menu. "Windows PE in RAMDisk," or whatever other description exists in the .sif file, appears as an option. Select this option, and then press ENTER.
  
  The computer starts Windows PE by using the RAM disk.

Method 2: Deploy Windows PE from RIS server in legacy flat method

1. On the RIS server, type the following command at a command prompt:
   RISetup.exe –add
   When you are prompted for a source, point RISetup to the Windows operating system CD that you want to use. The choice of the Windows operating system depends on the version of Windows PE that you add to the RIS server. For Windows PE 2004, use Windows XP Professional Service Pack 2. For Windows PE 2005, use Windows Server 2003 Standard Edition Service Pack 1.
2. Browse the location where RISetup installed the image. For example, the location may resemble the following:
   \\Server_name\Share_name\REMINST\Setup\ÀÒÉÒ\Images
   ËÁÒÂà˵Ø:In this step, theServer_nameplaceholder represents the RIS server name. ¡Ãкǹ¡ÒÃShare_nameplaceholder represents the name of the shared folder that contains the image. ¡Ãкǹ¡ÒÃÀÒÉÒplaceholder represents the language version of the image.
3. à»Ô´¡ÒÃplatformsubfolder in the image that you created, whereplatformrepresents i386, amd64, or IA-64.
4. à»Ô´¡ÒÃá¾Å·¿ÍÃìÁfolder on the CD or network share that contains Windows PE files, whereplatformrepresents i386, amd64, or IA-64.
5. Copy the contents of the Windows PEá¾Å·¿ÍÃìÁfolder to theplatformfolder of the image that you just opened.
6. When you are prompted to overwrite the files, clickYes to all.
7. Open the Templates folder in theá¾Å·¿ÍÃìÁfolder to which you copied Windows PEá¾Å·¿ÍÃìÁcontents.
8. Open the RIStndrd.sif file in a text editor. On the line that starts with OSLoadOptions, add the/minintµÑÇàÅ×Í¡
9. Copy the drivers (*.inf and *.sys) for the network adapter to theá¾Å·¿ÍÃìÁfolder that was created by RISetup.
10. Stop and start the BinlSvc service on the RIS server. For example, type the following commands at a command prompt:
    net stop binlsvc
    net start binlsvc
11. Start a RIS client, and then select the operating system image that you created in step 1.

ËÁÒÂà˵Ø

• If you do not copy the network drivers to theá¾Å·¿ÍÃìÁfolder, you may receive the following error message:
  The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. ¶éһѭËÒÂѧ¤§ÁÕÍÂÙè µÔ´µèͼÙé´ÙáÅÃкº¢Í§¤Ø³ Setup cannot continue. ¡´á»é¹ã´ æ à¾×èͨº¡Ò÷ӧҹ
• If you use Windows Management Instrumentation (WMI)-enabled Windows PE images, make sure that the share that contains the Windows PE image is marked as read-only. Otherwise, Windows Management Instrumentation (WMI) Tester (WBEMTest) may report error 0x80041014. This will make sure that other clients that connect will not error out when they try to enable WMI.
• ¨Ó¹Ç¹ÊÙ§ÊØ´¢Í§¡ÒõԴµÑ駾ÃéÍÁ·ÕèÊÒÁÒö·Óä´é¨Ò¡à«ÔÃì¿àÇÍÃì RIS à»ç¹ 75
• àÃÒ¢Íá¹Ð¹ÓãËé ¤Ø³»Ô´ãªé§Ò¹ Setupapi ºÑ¹·Ö¡àÁ×èͤسãªéÇÔ¸Õ¡ÒùÕéÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺÇÔ¸Õ¡ÒáàÅÔ¡¡ÒÃÅçÍ¡ Setupapi ¤ÅÔ¡ËÁÒÂàÅ¢º·¤ÇÒÁµèÍ仹Õéà¾×èÍ´Ùº·¤ÇÒÁã¹°Ò¹¤ÇÒÁÃÙé¢Í§ Microsoft:
  822570

  (http://support.microsoft.com/kb/822570/ )

  ¤Ø³¾ºÂÒÇàÃÔèÁµé¹Ãкº¤ÃÑé§àÁ×èͤسàÃÔèÁ WinPE â´Â¤ÇÒÁ¢Í§à«ÔÃì¿àÇÍÃìºÃÔ¡ÒáÒõԴµÑé§ÃÐÂÐä¡Å

à¾ÔèÁ Windows PE ¶Ö§à¤Ã×èͧÁ×Í RIS ¡ÒúÓÃاÃÑ¡ÉÒáÅСÒÃá¡é䢻ѭËÒàº×éͧµé¹

¤Ø³ÊÒÁÒöà¾ÔèÁ Windows PE ã¹ÃÒª×èͧ͢à¤Ã×èͧÁ×͵èÒ§ æ ·Õè¾ÃéÍÁãªé§Ò¹ã¹¡ÒúÓÃاÃÑ¡ÉÒáÅСÒÃá¡é䢻ѭËÒàº×éͧµé¹¢Í§Êèǹ¢Í§µÑǪèÇÂÊÃéÒ§¡ÒõԴµÑé§ä¤Åà͹µì àÁ×èͤسà¾ÔèÁ Windows PE ã¹ÃÒª×èͧ͢à¤Ã×èͧÁ×Í RIS ¤Ø³ÃкØÇèÒ Windows PE ·ÕèãªéÊÓËÃѺ¡ÒõԴµÑé§ ¡ÒúÓÃاÃÑ¡ÉÒ áÅЧҹ·ÕèÁÕ¡ÒÃá¡é䢻ѭËÒàº×éͧµé¹á·¹¡ÒÃãªéà»ç¹Ãкº»¯ÔºÑµÔ¡Ò÷Õèà´Ê¡ì·çÍ»

àÁ×è͵éͧ¡ÒÃà¾ÔèÁ Windows PE ã¹ÃÒª×èͧ͢à¤Ã×èͧÁ×Í RIS ´Óà¹Ô¹¡ÒôѧµèÍ仹Õé:

1. ã¹â¿Åà´ÍÃìáÁèẺ¢Í§ÃÙ»ÀҾ㹠Windows PE ¤é¹ËÒá¿éÁ RIStndrd.sif
2. à»Ô´á¿éÁ RIStndrd.sif ã¹µÑÇá¡é䢢éͤÇÒÁ
3. 㹡ÒÃ[OSChooser]Êèǹ ¡ÒÃà»ÅÕè¹á»Å§ ImageType = ImageType ÃÒ¡Òà "ẹ" = "winpe"
4. ÂéÒÂá¿éÁ Winbom.ini ¨Ò¡¹Ñé¹á¾Å·¿ÍÃìÁâ¿Åà´ÍÃìÃÙ»ÀҾ㹠Windows PE ä»Âѧâ¿Åà´ÍÃìÃÒ¡¢Í§ÃÙ»
   
   ËÁÒÂà˵Ø:¶éҤسäÁè·ÓµÒÁ¢Ñ鹵͹¹Õé áÅÐàÃÕ¡ãªé¤ÓÊÑè§ factory.exe ÃèÇÁ¡Ñº-minintÊÅѺËÃ×Í-winpeÊÇÔµªì Windows PE áÊ´§¡ÅèͧâµéµÍº·Õè¢ÍãËé¤Ø³ÃÕʵÒÃì· Windows PE ËÅѧ¨Ò¡·Õè¤Ø³àÃÔèÁ¡Ò÷ӧҹ
5. à»Ô´ã¹¡ÅØèÁ¹âºÒ Management Console (GPMC) ¤ÅÔ¡¢ÇÒâ´àÁ¹ËÃ×Í˹èÇÂͧ¤ì¡Ã·Õè¤Ø³µéͧ ¡ÒÃãªé áÅéÇ ¤ÅÔ¡ÊÃéÒ§ áÅСÒÃàª×èÍÁâ§ÁÒ·Õè¹Õè¢Í§Çѵ¶Ø¹âºÒ¡ÅØèÁ.
6. 㹡ÒÃÇѵ¶Ø¹âºÒ¡ÅØèÁãËÁè¾ÔÁ¾ìª×èÍÊÓËÃѺ Group Policy object (GPO), ¡ÅèͧâµéµÍº áÅШҡ¹Ñé¹ ¤ÅÔ¡µ¡Å§.
7. ¤ÅÔ¡¢ÇÒ GPO áÅШҡ¹Ñé¹ ¤ÅÔ¡á¡éä¢.
8. µÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ ¤é¹ËÒ áÅТÂÒ¤͹෹à¹ÍÃì·ÕèµèÍ仹Õé:
   ¼Ùéãªé Configuration\Windows Settings\Remote µÔ´µÑ駺ÃÔ¡ÒÃ
   .
9. 㹺ҹ˹éÒµèÒ§´éÒ¹¢ÇÒ ¤ÅÔ¡Êͧ¤ÃÑ駵ÑÇàÅ×Í¡ choice.
10. 㹡ÒäسÊÁºÑµÔµÑÇàÅ×Í¡ choice¡ÅèͧâµéµÍº ÀÒÂãµéà¤Ã×èͧÁ×ͤÅÔ¡·Õèà»Ô´ãªé§Ò¹áÅéÇ ¤ÅÔ¡µ¡Å§.
11. »Ô´µÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ
12. ã¹ GPMC ¤ÅÔ¡â´àÁ¹ËÃ×Í˹èÇÂͧ¤ì¡Ã·Õèàª×èÍÁâ§Çѵ¶Ø¹âºÒ¡ÅØèÁ·Õè¤Ø³ÊÃéÒ§äÇé¡è͹˹éÒ¹Õé
13. 㹺ҹ˹éÒµèÒ§´éÒ¹¢ÇÒ ¤ÅÔ¡Çѵ¶Ø¹âºÒ¡ÅØèÁ ·Õè¤Ø³ÊÃéÒ§ áÅéÇ ¤ÅÔ¡ÂéÒ¡ÒÃàª×èÍÁ⧢Ö鹨¹¡ÇèÒãºÊÑè§àª×èÍÁâ§Çѵ¶Ø¹âºÒ¡ÅØèÁÍÂÙèµèÓ¡ÇèÒ gpo ·ÕèÁÕ¡ÒõÑ駤èÒ·Õè¢Ñ´áÂ駡ѹ
    
    Çѵ¶Ø¹âºÒ¡ÅØèÁ¡ÑºãºÊÑ觵èÓÊØ´¢Í§¡ÒÃàª×èÍÁ⧨Сè͹˹éÒ¼èÒ¹ gpo ¡ÑºãºÊÑ觡ÒÃàª×èÍÁ⧷ÕèÊÙ§¡ÇèÒ

ËÁÒÂà˵Ø

• ੾ÒÐ RIS à«ÔÃì¿àÇÍÃì·Õèãªé Windows Server 2003 ʹѺʹع¡ÒõÒÁ¢Ñ鹵͹¹Õé
• áÁéÇèÒ Windows PE ÃÙ»»ÃÒ¡¯¢Öé¹ã¹¡ÒúÓÃاÃÑ¡ÉÒáÅСÒÃá¡é䢻ѭËÒàº×éͧµé¹¢Í§Êèǹ¢Í§µÑǪèÇÂÊÃéÒ§¡ÒõԴµÑé§ä¤Åà͹µì ¨ÐäÁè»ÃÒ¡¯º¹à¤Ã×èͧÁ×Íá·çº¹Õé¤Ø³ÊÁºÑµÔ¢Í§¡ÒõԴµÑé§áººÃÐÂÐä¡ÅºÃÔ¡ÒáÅèͧâµéµÍºº¹à«ÔÃì¿àÇÍÃì RIS
• The default settings of the Default Domain Policy GPO on a Windows Server 2003-based domain disable all options exceptAutomatic Setup㹡ÒÃChoice Options Properties¡ÅèͧâµéµÍº To override the default settings, make sure that the GPO that you create has a lower link order than the Default Domain Policy GPO.