[Today's post is provided by Chaohao Xu.]
The Windows Automated Installation Kit (AIK) for Windows 7 SP1 is released and can be downloaded from the following location: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0aee2b4b-494b-4adc-b174-33bc62f02c5d
You don't have to upgrade to Windows PE 3.1 to deploy Windows 7 SP1 and Windows Server 2008 R2 SP1. But if you want to upgrade to Windows PE 3.1, this post provides information about how you can do this with your existing Configuration Manager 2007 SP2 site. We also list some known issues that you might encounter when you use Configuration Manager operating system deployment with Windows PE 3.1.
To resolve this problem, update all the boot images to use Windows PE 3.1.
This problem is caused by the Configuration Manager 2007 client generating an embedded NULL character into the friendly name for the certificate that is related to the driver apply. To resolve this issue, see KB977203 and run CCMCertFix.exe either before you run the task sequence or add it as a step in the task sequence.
This posting is provided "AS IS" with no warranties, and confers no rights.
I think that in step 3 of the "Upgrade steps" section, you have to mention that the correct value for ExportImagePath property is in fact
\\<site _server>\sms_<site_code>\OSD\boot\i386\boot.wim or
\\<site _server>\sms_<site_code>\OSD\boot\i386 or
If you want that the ExportDefaultBootImage method works fine.
MVP ConfigrMgr - France
You are absolutely correct Aurélien. I have updated the post.
Thanks for pointing it out.
In case you want to use a script to automate Default Boot Image update operation or adding new default image you can use the script I've uploaded on my blog :
Blog Post (but in French) : myitforum.com/.../system-center-configuration-manager-2007-how-to-upgrade-default-boot-images-or-generate-new-default-boot-images-based-on-winpe-3-1-version-part-02.aspx
Script (in English) : myitforum.com/.../UpdateCreateBootImages_SCCM.zip
Have a nice day
If you want/need a more detailed step-by-step process to what the SCCM team blog has done, check out Brandon Linton's post at