Operating System Deployment (OSD) Fail on task sequence step:" set RebootStep Variable"

Are you talking about on the new machine or on the SCCM server?

I'm assuming the new machine. I'll try it again and check the logs when I get a chance.

On de new machine... Then in WinPe...

I'm seeing the same thing as you:

### DESCRIPTION: GetResourceID: ERROR : Could not locate the computer ID in WMI InstallSoftware 3/18/2009 2:01:12 PM 1368 (0x0558)

It also shows a completely different GUID than above. I'll post more later when I get a chance.

**EDIT**
I can see where it sees the SMBOIS GUID:

Setting SMBIOS GUID = 4C4C4544-0056-3010-804C-B1C04F334731. TSPxe 3/18/2009 1:56:55 PM 1544 (0x0608)

And sets a separate client GUID:

Client Identity: GUID:3A323128-F884-44CB-A395-4FA3771013CA TSPxe 3/18/2009 1:56:55 PM 1544 (0x0608)

This would explain why it's not found in SMS_R_System when I pre-stage it.

Anything beyond that, I don't know what else to look for or try.

Nice! I'll try this when I get a chance, probably next week, as I'm in training all this week.

I edited the .vbs on the distribution point, but that didn't do anything, so I edited both vbs files I could find on the system (one coming from the software package and the other on the DP), then had SCCM update the DPs, but it didn't change anything either.

In the vbs, it displayed:

WriteDebugLog " _SMSTSClientGUID " & vbTab & gsClientGuid & vbTab

So I changed that to _SMSTSClientIdentity to see if it changed in the log file, but it did not. I've edited all the "OemDeployment.vbs" files I can find on the system (one in the UNC for the package, the other on the DP), updated the DP, looked at the file on the DP and it matches the changes I made.

I also added a line to the error display:


WriteLog " #########=[ " & sTitle & " ]=######################################"
WriteLog " ### "
WriteLog " ### ERROR CODE: " & iErrorCode & gsPad
WriteLog " ### DESCRIPTION: " & sErrDescription & gsPad
WriteLog " ### SEVERITY: " & iSeverity & " (" & LCase(sTitle) & ")" & gsPad
WriteLog " ### "
>>WriteLog " ### Edited by PGLH @ 20090401 "
WriteLog " #####################################################################"

None of it shows up.

Am I missing something?

Usually all you have to do is go to the following directory:
C:\Program Files\Microsoft Configuration Manager\OSD\lib\Packages\Deployment\Dell\PowerEdge\DTK2.6
Edit the OemDeployment.vbs file, save, then update distribution points. There is usually nothing else to do. The script is not saved in the task sequence, and if you're booting to PXE/WinPE, it won't be cached anywhere. Of course, if you're booting from CD and elected to get all packages from the CD instead of DP, you'll have to burn another CD.

That is file I edited second. First, I edited the one on the DP directly. When that didn't work, I edited the source in the DTK2.6 directory and updated the distribution point.

I'm PXE booting, so I'm not sure why it's not updating.

I'll try to play with it more this evening.

I found out why my changes never showed up.

It's failing while running CustomReboot.vbs.

On line 291, I changed "gsClientGuid = GetTaskSequenceVariable("_SMSTSClientGuid")" to "gsClientGuid = GetTaskSequenceVariable("_SMSTSClientIdentity")"

But still have the same problem (this time my 'edited by' line showed up):

#########=[ CRITICAL ERROR ]=######################################
###
### ERROR CODE: 1
### DESCRIPTION: GetResourceID: ERROR : Could not locate the computer ID in WMI
### SEVERITY: 3 (critical error)
###
### edited by PGLH - CustomReboot.vbs
#####################################################################

in the log file above that, does it show the GUID of the machine or did it return a null value? If it showed a GUID, was the GUID the valid machine GUID as shown in SMS_R_System or was it one of the unkown machines in SMS_R_UnknownSystem?

From the log file:

GetResourceID: Query: Select * from SMS_R_System where SMSUniqueIdentifier = 'GUID:7bf6d1de-942e-44fd-9729-75cf3631f3fc'

What I'm seeing for the two unknown computers:

x86 = 3ad43e74-d156-43b3-afee-6bb1cd61475c
x64 = c6843bcc-52d7-4ba1-82fa-f2c68888e407


**EDIT**
This is the SQL statement for me to see that SMSUniqueIdentifier above when running a report in SCCM:

Select * from v_R_System where SMS_Unique_Identifier0 = 'GUID:3ad43e74-d156-43b3-afee-6bb1cd61475c'

Running that shows the system as unknown and shows the SMBIOS GUID I see during PXE.

You shouldn't go by the SMBIOS GUID as displayed by the PXE boot as it has nothing to do with the GUID assigned by ConfigMgr to the machine.

What you should do is try:

Select * from v_R_System where SMS_Unique_Identifier0 = 'GUID:7bf6d1de-942e-44fd-9729-75cf3631f3fc'

I like using WMI CIM Studio (free DL from MS) because i can browse WMI and see all the instances of particular classes pretty easily. So if I look in SMS_R_System, the GUID above should be there (not the unknown comptuer GUID).

As far as the log... is the info immediately after the query showing failure to get the computer from WMI?

"You shouldn't go by the SMBIOS GUID as displayed by the PXE boot as it has nothing to do with the GUID assigned by ConfigMgr to the machine."

I wasn't going by the SMBIOS GUID. When I ran a report for the SMSUniqueIdentifier, it showed several columns, one being the SMBIOS GUID, which was what I saw at PXE, which indicated to me that the SMS_Unique_Identifier0 of 'GUID:7bf6d1de-942e-44fd-9729-75cf3631f3fc' is actually the machine I am using.

As far as where the error is, it falls immediately after the select statement. I assume it fails right then because SMS_R_System doesn't exist?

I changed all SMS_R_System and SMSUniqueIdentifier in CustomReboot.vbs & OemDeployment.vbs to v_R_System and SMS_Unique_Identifier0 and it doesn't fail anymore.

However, you can see it run the Set RebootStep Variable, then it reboots. It just does this endlessly. I'm not sure what the RebootStep variable is, but I can see where it checks Step 1, 2 & 3, and all three evaluate to false.

The only error I see in the log is this:

D:\_SMSTaskSequence\Packages\CC10006D\CustomReboot.vbs(445, 5) SWbemObjectSet: Invalid class

Right after: GetResourceID: Query: Select * from v_R_SYSTEM where SMS_Unique_Identifier0 = 'GUID:7bf6d1de-942e-44fd-9729-75cf3631f3fc'

A few lines above that, I can see where it pulls that SWbemObjectSet:

ConnectToProvider: Connecting to WMI at : 'root\sms'
ConnectToProvider: goSWbemServices returned type: SWbemServicesEx
ConnectToProvider: Connected to management point.
ConnectToProvider: Looking for instances of SMS_ProviderLocation
ConnectToProvider: ProviderLoc returned type: SWbemObjectSet
ConnectToProvider: Location returned type: SWbemObjectEx
ConnectToProvider: Machine 'snip' is the provider for the local site 'snip'
ConnectToProvider: Connecting to the server. Attempt #1
ConnectToProvider: Connected to the server.
ConnectToProvider: ending...

Hi, I'm trying to deploy Win2k3 to a PE840. The error I get in SCCM when I run Status Message Queries is this:

The task sequence execution engine failed executing the action (Set RebootStep Variable) in the group () with the error code 2147942561
Action output: 800700a1 (e:\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,102)
RecursiveCreatePath(sPath.substr(0, nPos), psa), HRESULT=800700a1 (e:\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,102)
RecursiveCreatePath( sNormalizedPath, psa ), HRESULT=800700a1 (e:\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,157)
DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=800700a1 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3128)
TS::Utility::ResolveSource(pszPkgID, sPath, 0, hUserToken, sUserName.empty() ? NULL : sUserName.c_str(), sUserName.empty() ? NULL : sUserPassword.c_str()), HRESULT=800700a1 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\runcommandline.cpp,395)
cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=800700a1 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,385)
Failed to resolve the source for SMS PKGID=2010009B, hr=0x800700a1
Install Software failed to run command line, hr=0x800700a1. The operating system reported error 2147942561: The specified path is invalid.

I've checked at updated my DP's, the username and password is a domain admin with permissions set to full. I'm Running SCCM SP1 not R2 so I don't have the "unknown machine" option.

I've made the changes put forward in this post, but still nothing. Hope you'll be able to help.