none
SCCM生成的CD 如何实现从网络启动 (SCCM 2007 sp1 with R2) RRS feed

  • 问题

  •  

    大家好!


    近些日子,我尝试使用SCCM的OSD部署操作系统。我已经成功实现的使用DVD一类的媒体部署操作系统。
    但是当我尝试让DVD媒介从网络启动时遇到了问题。以前使用SMS2003和BDD2007配合部署操作系统时,我可以使用RIS导入一个WindowsXP ISO镜像,再将InstallCD覆盖WindowsXP 在RIS的文件实现从网络启动部署,这样客户机可以在需要时选择从网络启动重新部署操作系统。
    然而SCCM的OSD是基于PE2.0的,我尝试但是无法制作一个WDS认可的可启动WIM文件。我尝试使用imagex及其boot参数将SCCM的安装DVD重新打包为WIM格式,但WDS并不认为这个WIM是一个可启动的。我也尝试直接将DVD中的文件和PE2.0一起封装,仍然失败了。而RIS也无法部署PE2.0。

    近日在网上查看了有关R2的说明,在英文SCCM 2007 sp1 with R2 下确实实现了未知客户端的OSD部署,然而仍然需要借助CD这一媒介。

     

    由于SCCM生成的CD其目录层次与原PE2.0不同,且其为WIM文件。我尝试制作一个flat PE2.0,但是按照微软所提供flat PE文档我并未成功制作,主要原因是对于SCCM的ISO,其PE目录存在于比原PE更下一层的目录,在BCDEDIT时卡壳。

     

    恳请大家提供从网络启动ISO或者被定义过的PE2.0的启动方法,实现从网络启动的SCCM2007 OSD部署

     

    附上flat PE 2.0文档:

    -------------------------------------------

    SYMPTOMS

    You start Windows Vista from a Microsoft Windows Preinstallation Environment (Windows PE) 2.0 image by using the flat file boot method. When you do this, an access violation occurs.

    Back to the top

    CAUSE

    This problem occurs because an error occurs when the CD file system (CDFS) driver interacts with a file-based write filter driver.

    Back to the top

    RESOLUTION

    Service pack information

    To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    935791 (http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service pack

    Back to the top

    Hotfix information

    A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

    If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

    Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
    http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
    Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

    Prerequisites

    To apply this hotfix, you must have Windows Automated Installation Kit (Windows AIK) or Microsoft Windows OEM Preinstallation Kit (OPK) installed.

    Restart requirement

    You do not have to restart the computer after you apply this hotfix.

    Hotfix replacement information

    This hotfix does not replace a previously released hotfix.

    Registry information

    To use one of the hotfixes in this package, you do not have to make any changes to the registry.

    File information

    The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
    Windows Vista, 32-bit version
    File name File version File size Date Time Platform
    Fbwf.sys 6.0.6000.20484 69,120 16-Nov-2006 04:39 x86
    Fbwflib.dll 6.0.6000.20484 12,288 16-Nov-2006 07:57 x86
    Windows Vista, 64-bit version
    File name File version File size Date Time Platform
    Fbwf.sys 6.0.6000.20484 97,280 16-Nov-2006 05:11 x64
    Fbwflib.dll 6.0.6000.20484 15,360 16-Nov-2006 08:14 x64

    Back to the top

    Resolution information

    To resolve the problem after you apply the hotfix, follow these steps.
    1. Create a flat boot ISO image of Windows PE. To do this, follow these steps.

    Note The following steps assume that the Windows6.0-KB928570-x86.msu file or the Windows6.0-KB928570-x64.msu file is in the C drive. If the Windows6.0-KB928570-x86.msu file or the Windows6.0-KB928570-x64.msu file is in another location, replace "C:\" with the path of the Windows6.0-KB928570-x86.msu file or of the Windows6.0-KB928570-x64.msu file.
    a. At a command prompt, run the following command to expand the .msu file on a 32-bit computer:
    expand C:\Windows6.0-KB928570-x86.msu -F:Windows6.0-KB928570-x86.cab C:\
    Note On a 64-bit computer, run the following command:
    expand C:\Windows6.0-KB928570-x64.msu -F:Windows6.0-KB928570-x64.cab C:\
    b. Click Start, point to All Programs, point to Microsoft Windows AIK, and then click Windows PE Tools Command Prompt.
    c. Run the following commands at the Windows PE Tools command prompt:
    copype x86 C:\flatPE
    imagex /mountrw C:\flatPE\winpe.wim 1 C:\flatPE\mount
    peimg /import=C:\Windows6.0-KB928570-x86.cab C:\flatPE\mount\Windows
    peimg /install=*928570* C:\flatPE\mount\Windows
    peimg /prep mount
    imagex /unmount /commit C:\flatPE\mount
    imagex /apply C:\flatPE\winpe.wim 1 C:\flatPE\mount
    copy C:\flatpe\ISO\bootmgr C:\flatPE\mount
    mkdir C:\flatpe\mount\boot
    Bcdedit -createstore C:\flatpe\mount\boot\BCD
    Bcdedit -store C:\flatpe\mount\boot\BCD -create {bootmgr} /d "Boot Manager" Bcdedit -store C:\flatpe\mount\boot\BCD -set {bootmgr} device boot Bcdedit -store C:\flatpe\mount\boot\BCD -create /d "WINPE" -application osloader
    Note After you run the last command, you receive a GUID value. Note this value.
    d. Run the following commands at the Windows PE Tools command prompt.

    Note In these commands, replace GUID with the GUID value that you noted in step 1c.
    Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID osdevice boot
    Bcdedit -store C:\flatpe\mount\boot\BCD -set {bootmgr} default GUID
    Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID device boot
    Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID path \windows\system32\boot\winload.exe
    Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID systemroot \windows
    Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID winpe yes
    Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID detecthal yes
    oscdimg -n -betfsboot.com mount flatPE.iso
    2. Burn the ISO image of Windows PE to a blank CD by using a CD-burning program.
    3. Use this ISO image of Windows PE to start Windows Vista.

    Back to the top

    STATUS

    Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

    Back to the top

    MORE INFORMATION

    When you use the flat file boot method, Windows PE files are not stored in a boot image. Instead, Windows PE files are stored in a flat file directory structure. Windows PE is started directly from the flat file directory structure.

    For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
    824684 (http://support.microsoft.com/kb/824684/LN/) Description of the standard terminology that is used to describe Microsoft software updates
     
     
     
    2008年8月11日 12:00

答案

  • 建议如下:

    1. 不要再尝试使用WinPE 2.0的ISO通过RIS从网络引导客户端了。你只要遵守一些官方的最佳实践即可,没必要花时间来琢磨这个。
    2. 升级RIS到WDS的混合模式,这样一来,你原有的RIS RAMDISK镜像可以用,也可以支持新的wim格式的网络启动。很容易又省事。希望对你有所帮助。

     

    2008年8月18日 6:36

全部回复

  • 建议如下:

    1. 不要再尝试使用WinPE 2.0的ISO通过RIS从网络引导客户端了。你只要遵守一些官方的最佳实践即可,没必要花时间来琢磨这个。
    2. 升级RIS到WDS的混合模式,这样一来,你原有的RIS RAMDISK镜像可以用,也可以支持新的wim格式的网络启动。很容易又省事。希望对你有所帮助。

     

    2008年8月18日 6:36
  • 您好!谢谢您的回复。

     

    我已经尝试另一个方法实现。

     

    首先,SCCM的操作系统PXE播发中,如果检测到客户机已经接受了一次PXE播发后,将使用abortpxe而不再使用startcom,如果需要再次让客户端端接收到startcom,则需要清除上一个pxe播发或重新adversite

     

    经多次测试,发现以下方法可以让客户机永远收到startcom,在需要时可以按下F12从网络启动OSD过程。

     

    安装WDS和SCCM后,不要在SCCM中添加PXE服务点的角色,当对x86启动镜像配置分发点并更新后,能够在分发点下找到boot.a00000001.wim。该文件正式从网络启动安装过程的启动文件。

     

    将该文件导入WDS的启动镜像中,正常配置WDS,SCCM可以将OSD任务一起adversite到unknown compuer。

     

    如果使用imagex打开该wim文件,发现其正是采用了flatpe格式的pe2.0

     

    这种方法仅仅是针对客户要求不需要动服务器,并在需要时自行决定重新部署操作系统的变通方法,也许违背了官方建议部署的方式,但是确实在实际部署过程中,存在上面的需求。

     

    再次感谢您的回复!

    2008年8月19日 7:11