Troubleshooting Tips – Refreshing clients with SCCM 2012 and MDT 2012 RC1

Yesterday I run into a computer refresh failing with SCCM 2012 and MDT 2012 RC1. While the issue is still being investigated, here are the steps I did to troubleshoot, and the temporary workaround I configured for the issue.

Update! This is fixed in the RTM version of MDT 2012. I left the article here as a resource for MDT 2012 troubleshooting techniques.

The Symptoms

The error I got was "The parameter is incorrect. (Error: 80070057; Source: Windows)" (see the following screenshot).

When I opened the smsts.log file I found the following (I cleaned up the log a little bit):

Set command line: "OSDApplyOS.exe" /image:PS100007,1 "/config:PS10000B,unattend.xml" /target:%OSDisk%

The /target parameter specifies an invalid target location.   

Failed to run the action: Apply Operating System Image.

The parameter is incorrect. (Error: 80070057; Source: Windows) 
  

The log file info led me to believe that the OSDisk value was never set (it's supposed to be set by ZTIGather.wsf).  This is the default Apply OS action, where you can see that the target partition/volume, is the OSDisk property.

To workaround my issue I simply set the OSDisk value to in my case, C:, but for Refresh only, since bare metal deployment worked just fine with the default settings.

Note: you might be tempted to just configure the apply OS action to deploy the image to disk 0 partition 1, and that will also make the computer refresh to work… but will cause your bare metal deployments to fail, since the default sequence creates two partitions when deploying Windows 7.

/ Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
6 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Admin
Admin
10 years ago

This is fixed in the RTM version of MDT 2012. I have updated the article with a not about that… thanks

/ Johan

wireshark
wireshark
10 years ago

Hi Johan
Do you now if this issue is solved in the RTM releases ?

Thanks

Admin
Admin
10 years ago

Thanks Mark,

I have uploaded your script to this link:
https://deploymentresearch.com/DRFiles/ZTISetOSDisk.zip

/ Johan

Admin
Admin
10 years ago

Thanks for the tip!

The comment module is removing XML like formatting… if you send me the script ( my email is my lastname, and I'm using gmail), I can add that to the site directly.

/ Johan

markt
markt
10 years ago

Looks like the MDT header might be missing from the script in my previous comment… not sure why.

markt
markt
10 years ago

Hi Johan, We had a similar issue with ConfigMgr 2007 and MDT 2010. The format action would set the OSDisk variable but as this is bypassed for OS refresh the apply OS image step would fail. We also found that setting the OSDisk variable to a specific drive letter would not work in all scenarios as the drive letter assigned to the system disk in PE could change (eg. if Bitlocker partition existed or not). In the end I wrote a little MDT based script to find the OS disk and then set the variable. It's based on some code… Read more »


>