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

"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?"

If it fails immediately after the query to SMS_R_System, then yes, it was because the GUID was not found in SMS_R_System. From the code you copied above, it's successfully connecting to the site, just not finding the GUID using the query.

The _SMSTSClientIdentity variable should hold the proper GUID that should be in SMS_R_System.

TommyEr,

The problem does not appear to be with the client script. See the error "Failed to resolve the source for SMS PKGID=2010009B, hr=0x800700a1". All the other messages are directly from SCCM code, not from the script.

This usually means that the package could not be found at a reachable DP. You should check the SMSTS.LOG file in WinPE to get more details about the issue.

"Hi,

Testing again...
Now it is passing the "Set RebootStep Variable" but it ends en don't install anything. In the smsts.log i find the following errors a couple of times:

- Failed to save environment to (80070057)
- Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact.....
- Failed to persist execution state. (Error 0x(80070057)
- Failed to save execution state and envrionment to local hard disk.

Also when the step "Reboot to PXE/USB" is passed, the server is not rebooted. The next time when i start the task sequence it begins form the beginning. This is because the server dont reboot and the last action of the task is to reset the "rebootStep".... Strange... *-)

Very strange...
You've got the same?


"

ErikF,

The "Failed to save environment" and following messages are normal when you are booting to PXE and there is not a valid drive for SCCM to store logs and other info. You can safely ignore those messages.

However, what should be happening is that when the "Reboot to PXE/USB" step runs, it contacts the site server and increments the RebootStep machine variable and resets the PXE advertisement. The task groups in the task sequence are conditioned on the variable being at a certain level, and will run or not run depending on the value. During each cycle of the task sequence, it should be running a different set of steps, then exiting and rebooting and starting where it left off. When the task sequence goes past the last step in WinPE it will reboot, either back to WinPE (if we've reset the advertisement), or to a disk partition based WinPE or regular OS.

If you're saying the task sequence is in WinPE, runs through and then just sits there, then that is strange.

"If it fails immediately after the query to SMS_R_System, then yes, it was because the GUID was not found in SMS_R_System. From the code you copied above, it's successfully connecting to the site, just not finding the GUID using the query.

The _SMSTSClientIdentity variable should hold the proper GUID that should be in SMS_R_System."

After changing SMS_R_System to v_R_System, it finds the GUID, but keeps rebooting, as stated above:

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...

Any ideas?

"After changing SMS_R_System to v_R_System, it finds the GUID, but keeps rebooting, as stated above:

The only error I see in the log is this:

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

"

I'm surprised the task isn't still failing there, because what you're doing is substituting a WMI class name (SMS_R_System) for a SQL View name (v_R_SYSTEM). You can't query SQL views from WMI, hence the invalid class name error. You say it finds the GUID, but I don't think that's happening, because you are getting the error right after the query.

The thing I would find out is why the GUID is appearing in the view but not in the "real" WMI class name. Without locating the computer in WMI, it cannot modify the machine variable, and cannot reset the PXE advertisement. I think you should go back to the change I suggested a while back and start there.

In CustomReboot.vbs (about line 489) and OemDeployment.vbs (about line 5142) - the query line should read:

Set colResources = goSWbemServices.ExecQuery("Select * from SMS_R_System where SMSUniqueIdentifier = '" & gsClientGuid & "'")


In CustomReboot.vbs (about line 295) and OemDeployment.vbs (about line 522), the line getting the gsClientGuid variable should read:

gsClientGuid = GetTaskSequenceVariable("_SMSTSClientIdentity")

Hi,

I've added a few lines from the smsts.log:
PackageID = '2010009B' InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
BaseVar = '', ContinueOnError='' InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
SwdAction = '0001' InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
DownloadOnDemand flag is true. Attempting to download content locally for Package 2010009B.. InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Package Flags: 0x4000000 InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
GetDirectoryListing() entered InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Initializing HTTP transport. InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)

Downloaded file from http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/CustomReboot.vbs to C:\_SMSTaskSequence\Packages\2010009B\CustomReboot.vbs InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Downloaded file from http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/diskpartclean.bat to C:\_SMSTaskSequence\Packages\2010009B\diskpartclean.bat InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Download done setting progress bar to 100 InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Content successfully downloaded at C:\_SMSTaskSequence\Packages\2010009B InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Resolved source to 'C:\_SMSTaskSequence\Packages\2010009B' InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Set command line: Run command line InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Working dir 'C:\_SMSTaskSequence\Packages\2010009B' InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Executing command line: Run command line InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Microsoft (R) Windows Script Host Version 5.7 InstallSoftware 06.04.2009 13:42:33 1576 (0x0628)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 06.04.2009 13:42:33 1576 (0x0628)
InstallSoftware 06.04.2009 13:42:33 1576 (0x0628)
InstallSoftware 06.04.2009 13:42:33 1576 (0x0628)
Main: starting... InstallSoftware 06.04.2009 13:42:33 1576 (0x0628)

What I've done here is that I've changed the value in the Task Sequence Variable _SMSTSInWinPE eguals (from false to) True
The script now runs until the step involving format and partition. I've created my own array settings file and I suspect there's something wrong with my setting.

Suspecting my Array Configuration to be faulty I tried using the 5i-raid1.ini file included with DDP, but now I'm back to where I started with the task not being able to resolve the source to Custom Reboot.

Is it possible to upload my smsts.log files so that you can see the whole file and what happens during a Task Sequence. There might be a lot of useful info in the log files to help me solve my "little" problem :-)

Any suggestions would be most welcome...

Tommy

Setting URL = http://st-f-sccm-ps.ryfylke.local/SMS_DP_SMSPKGF$/2010009B/. InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Address = st-f-sccm-ps.ryfylke.local, Object = /SMS_DP_SMSPKGF$/2010009B/, Port = 80. InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
WinHttp credentials set InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
CLibSMSMessageWinHttpTransport::Send: URL: st-f-sccm-ps.ryfylke.local:80 PROPFIND /SMS_DP_SMSPKGF$/2010009B/ InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Error. Status code 207 returned InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
List of files to be downloaded InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Directory: http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/ InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
File: http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/CoreUtils.vbs InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
File: http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/CustomReboot.vbs InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
File: http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/diskpartclean.bat InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
GetDirectoryListing() successfully completed InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)
Downloaded file from http://st-f-sccm-ps.ryfylke.local:80/SMS_DP_SMSPKGF$/2010009B/CoreUtils.vbs to C:\_SMSTaskSequence\Packages\2010009B\CoreUtils.vbs InstallSoftware 06.04.2009 13:42:32 1576 (0x0628)

Anyone??

After further review of this issue (unknown computers failing task sequence), it has been discovered that there is an issue related to the use of machine variables on unknown systems. Basically, ConfigMgr is not allowing the use of machine variables on machines currently marked as unknown. This means that even though we can discover the proper GUID of the machine and get the machine's ResourceID from ConfigMgr, we still cannot do the tasks needed to reboot the machine to PXE unless the machine is already a "known" machine in ConfigMgr, and the workaround is more than changing a variable name.

So, until this issue is resolved and a fix posted, the DDP will not work when used with unknown systems. In order to deploy a server using the DPP, you must first import the computer information into ConfigMgr.

"After further review of this issue (unknown computers failing task sequence), it has been discovered that there is an issue related to the use of machine variables on unknown systems. Basically, ConfigMgr is not allowing the use of machine variables on machines currently marked as unknown. This means that even though we can discover the proper GUID of the machine and get the machine's ResourceID from ConfigMgr, we still cannot do the tasks needed to reboot the machine to PXE unless the machine is already a "known" machine in ConfigMgr, and the workaround is more than changing a variable name.

So, until this issue is resolved and a fix posted, the DDP will not work when used with unknown systems. In order to deploy a server using the DPP, you must first import the computer information into ConfigMgr."

My server is a known maschine in ConfigMgr so that can't be the issue with my problem.

That was in reference to the RebootStep variable for Unknown Computers in R2.

Hi
I'm having exactly the same problem. I have distributed all the packages, made sure my NAA has the correct priviledges. Deleted and recreated my task sequence but everytime it fails at the "set rebootstep variable". It fails with error code 0x00000001. I have also set my server PE2950 back to factory default but still no joy. I have also followed all the steps prescribed by "ramseyg" thanks.

Masby661

OK, starting to get some success. The TS configures the BIOS, BMC, RAID and DRAC5 it then reboots but does not automatically PXE boot back into the TS. I have a collection called staging and I imported the PE2950 mac address into that collection and gave it a name of win2003. When I go into the properties of it and look at the variables tab there is a "reboot step of 2". Am I supposed to F12 after everytime it reboots or should it do it automatically. If it is supposed to do it automatically does anyone know why it isn't? Or had the same issue.

Masby661