SCCM 2007 R3 OEM Prestage Image Issue (Network Steve Forum)

SCCM 2007 R3 OEM Prestage Image Issue

Greetings All, Has anyone successfully used the prestage OEM image feature of R3 yet and got it working. The environment, is - Windows 7 Professional x86 (Is this supported OS does it have to be Enterprise?) - C and D drive data, User profile Here is the process I used to generate the media Process overview: 1. Create Prestaged media (TS) (Create Task Sequence Media) 2. Outputs WIM file 3. Imported WIM into SCCM as Operating System Images 4. Create TS to Prestage Image for OEM Distribution · Move the CDROm · Creates Paritions/C and D then Formats · Applies Data Image to C:\ · Restores the BCD bootsector (used X:\sms\bin\i386\bootsect.exe /nt60 C:) · Shutdown WinPE 5. Validate against Existing TS updated to support OEMmedia variables for steps Format/and Apply OS used task sequence variables _SMSTSMediaType not equals OEMmedia After the computer is powered on, the Format and Apply OS steps are skipped, then at the Apply Windows Settings it fails. Command line: "osdwinsettings.exe" /config OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) !sInstallType.empty(), HRESULT=80004005 (c:\nts_sms_fre\sms\framework\osdcore\infanswerfile.cpp,325) OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) Failed to read installation type from environment.. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows) OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) OSD::Utility::BaseAnswerFile::CreateAnswerFile( pAnswerFile ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,364) OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) Failed to initialize answer file. OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) ConfigureWinSettings(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,637) OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) Failed to open the Task Sequencing Environment. Code 0x80004005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows) OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) Exiting with return code 0x80004005 OSDWinSettings 25/10/2010 2:59:37 PM 1216 (0x04C0) Process completed with exit code 2147500037 TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) !--------------------------------------------------------------------------------------------! TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Failed to run the action: Apply Windows Settings. Unspecified error (Error: 80004005; Source: Windows) TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Sending status message . . . TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Send a task execution status message SMS_TSExecution_ActionFailError TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) MP server test.com and port 80. SSL=false. CRL=false. TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Site code: MIL TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Client machine name: Unknown TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Client Identity: GUID:A77505B3-BA7C-4FCF-9BAE-337E011E6D98 TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Advertisement ID: MIL2004C TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Package ID: MIL00036 TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Sending StatusMessage TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) Formatted header: TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>40891350-2514-4E0A-9B43-8ED51EC96AC4</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-10-25T04:59:37Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4234"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) CLibSMSMessageWinHttpTransport::Send: URL: test01.test.COM.AU:80 CCM_POST /ccm_system/request TSManager 25/10/2010 2:59:37 PM 1668 (0x0684) The request has succeeded. 200 OK TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) Clear local default environment TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) Let the parent group (Install Operating System) decides whether to continue execution TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) Failed to run the last action: Apply Windows Settings. Execution of task sequence failed. Unspecified error (Error: 80004005; Source: Windows) TSManager 25/10/2010 2:59:38 PM 1668 (0x0684) Lawrence Byrne

October 25th, 2010 10:20am

I have not tested R3 pre-staged media yet but my understanding is that the Apply OS Image step still needs to run. This step will work differently when OEM media is used to initiate the TS and just "configure" the image that has already been restored to the disk rather than wipe the disk or restore an image. Have a read of the following blog article: http://blogs.technet.com/b/inside_osd/archive/2010/04/29/prestaged-media-in-configuration-manager-r3.aspx The important part is: Prestaged media is designed to work with your current task sequences. When Prestaged media is created it will have a built-in read-only variable _SMSTSMediaType = OEMmedia. This can be used as a condition throughout the task sequence. This value is also used when the Apply Operating System task sequence action is run. If _SMSTSMediaType is set to OEMmedia, the task sequence action will bypass the disk wipe and deploying the .wim because the disk is ready. It will perform some configuration to the operating system based on you Configuration Manager environment. As I said I have not tested it yet so I could be wrong! Regards, Mark.

Free Windows Admin Tool Kit Click here and download it now

October 25th, 2010 1:44pm

Thanks Mark for your response. Basically I have followed that article to the T, and for me it hasn't worked. I have tried both the Apply Operating System TS step and Apply Data Image to no avail. The Apply Data Image seems the most logical however when it boots back up and starts executing the deployment TS it fails on the step Apply Windows Settings Unfortunately, I still do not have a resolution to this presently. Still researching. Any thoughts welcome. Cheers

October 25th, 2010 1:55pm

My understanding is that to restore the OEM media to the disk you have to use the "Apply Data Image" TS action, rather than OS Image. Once restored the system will boot into PE from the local disk, connect to your ConfigMgr site and then process policy etc. to see if there are advertised task sequences. It will then run your normal deployment TS. I assumed from your original post that you have changed your normal deployment TS to bypass the "Apply OS Image" step when _SMSTSMediaType is "OEMMedia". From reading the blog article you shouldn't do this. The "Apply OS Image" action still needs to run even when the OEM media has been restored to the disk. The action itself will then work differently if OEMMedia is being used, you don't need to change your TS action options to do this. Sorry if I am misunderstanding what you are saying. However I think the "Apply Windows Settings" step may be failing as you are bypassing the "Apply OS Image" step. Regards, Mark.

Free Windows Admin Tool Kit Click here and download it now

October 25th, 2010 2:10pm

Greetings Mark, Spot on, I just had another read of the SCCM help file, my failure is not reading the text properly. It does say to set _SMSTSMediaType = OEMmedia for the Apply Operating System ts step. I was skipping this. Extract from SCCM Help File Prestaged media is designed to work with existing task sequences. If you are using the default task sequence you created by selecting the Install from existing image package from the New Task Sequence wizard, you must include additional conditions to prevent the files prestaged on the drive from being removed. To do this you can add the following Task Sequence Variable condition for the Partition Disk action and the Apply Operating System Image action: _SMSTSMediaType not equals OEMmedia. Prestaged media on creation will set _SMSTSMediaType = OEMmedia. This can be used as a condition throughout the task sequence. This value is also used when the Apply Operating System action is invoked. If _SMSTSMediaType is set to OEMmedia, the task sequence action will not erase the disk or download the .wim file. I will give this a go tomorrow, and if all goes well i will post the good news here. Thanks for the extra pair of eyes on this. Reading has never been one of my strong points.:) Thanks for your comments, they have directed me well. Lawrence Byrne

October 25th, 2010 2:44pm

No worries... I am interested to know how you get on so please report back when you have had some time to test it. I am hoping to test this out myself later this week. I had to read it a few times myself to understand what was being said so you're not the only one :-). Mark.

Free Windows Admin Tool Kit Click here and download it now

October 25th, 2010 2:54pm

Greetings Mark, just a quick follow up to confirm that the following worked a charm: TS Step Task Sequence Variable Partition Disk _SMSTSMediaType not equals OEMmedia Apply Operating System Image SMSTSMediaType = OEMmedia Overall, the process works well.... Cheers Lawrence Byrne

October 26th, 2010 4:38am

Ok that's good news. I don't think you need any options configured on the Apply Operating System Image step. This step should run in all scenarios, it will allow you to use the same TS for bare metal, OS refresh and OEM pre-staged media. When this step executes it will work out for itself what it needs to do based on the the value of _SMSTSMediaType. If it is a normal bare metal deployment that it would restore the image referenced in the Appy Operating System Image step, if you have pre-staged the system with OEM Pre-staged media then this step would just configure whatever OS image has been pre-staged. Mark.

Free Windows Admin Tool Kit Click here and download it now

October 26th, 2010 4:45am

This topic is archived. No further replies will be accepted.