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

"Hello,

Have anyone running into problems with the deployment for Dell Poweredge M605/M905? I have a problem running the first step of the task sequence ("Set RebootStep Variable"), this step have no logs, except de smsts.log. The error in the log is:

####################################################################
###
### ERROR CODE: 1
### DESCRIPTION: Get ResourceID: ERROR: Could not locate the computer ID in WMI
### SEVERITY: 3 (critical error)
###
####################################################################

***************************************************************************
Dumping *All* Task Sequence Environment Variables:
.....
.....


There is a NAA account
I run SCCM SP1 R2

The deploy server obtain's a ip-adress and it doensn't mather wich server i take (M605 or M905).

Does anyone have the same problem here?





"

ErikF - I'm not familiar with this error - Questions:
1 - are you using ConfigMgr R2?
2 - Have you configured a network access account?

Ramsey,

Thnx for the reply.
But like i said i have configured a Network Acces Account (NAA) and I'm running Configmgr ServicePack 1 R2.

Any further idea's?

so on the Set RebootStep variable, you enter a username/password there also - this account needs to have access to ConfigMgr to both read and modify the Comptuer Object. have you given that account the proper rights into ConfigMgr?

Does this system already exist in Configmgr, or is it an 'unknown computer' ??

Hello,

The network acces account has enough rights (it's a domain admin account, just for testing purposes). So this account has the rights to read and modify the computer object. The system is in the first place an 'unknown computer', but when first pxe booted he appears not in a collection, but in the 'unprovionised computer' container under OSD. When added with a 'computer assocation' it also doesn't work.

Some more information:
I run SCCM SP 1 R2 in mixed mode.
The NAA account has enough rights onto the SQL server.
The PXE service point is on the SCCM-server
DHCP is on the domain controller (another server).

More suggestions?

I'm having the exact same problem. I installed the DDP a couple weeks ago and haven't been able to make it past that step.

**EDIT**
A little more information. I'm also using SCCM sp1 r2 with a configured network access account. I also tried enter my own credents into the TS where it sets the variable, but it failed just the same.

I can build a custom task sequence and it works.

What I see right away is that initially that will work because the system's unknown, but after the first couple steps, is it still unknown to SCCM, or does it then go to to SMS_R_System?

What about importing the system's guid into SCCM? I may try that now, although it'd be a PITA to do for all systems.

After some debugging and research we have found a possible problem.
This step makes use of the 'customReboot' script. In this script there is command that search for de ComputerID in SCCM.

The command makes the following query:

Select * from SMS_R_System where SMSUniqueIdentifier = '" & gsClientGuid & "'"

problem 1:
This query should never work, because in the SMSUniqueIdentifier in the SMS_R_System table begins with 'GUID:' (Where is the client GUID)

problem 2:
If we deploy an 'unknown system' the system would not be placed in the SMS_R_System table, but in the SMS_R_UnknownSystem table. In this table the SMSUniqueIdentifier doesn't begin with GUID:. So the query would work on this table...

What have I done:
I've changed the table name in the script. SMS_R_System must be SMS_R_UnknownSystem (two times). Then its works. Momentally This step is passed, but i encounter some problems later in the task sequence, which i'm debugging now.
And I'm searching a solution that the SMSUniqueIdentifier will be searched in both tables (SMS_R_System and SMS_R_UnknownSystem).

Does it also work for you?

Hmm i don't know. Give it a try.

The first question i also don't know. I just found this problem a few hours ago! So I'm currently testing and debugging.

You said you have builded a custom task sequence. How have you don''t it?
How have you customize it?

Are you deploying Windows Server 2003 or 2008? And on which hardware (Blades)?

I originally used the Microsoft Deployment Toolkit to create a TS. From there, I created a new custom task sequence to copy the order of things.

I have successfully deployed w2k8 (x64 & x86) & w2k3 onto a 1955 (my only available hw currently). Eventually I'll test this on an m600 & 2950.

I'm having a problem with 2k3, though. When I deploy it, I use Dell's boot image with the latest broadcom drivers downloaded from support.dell.com. Everything goes fine until the end and it goes to install software packages (OMSA is the first one I have post-OS install). What I found is it's not loading the NIC drivers correctly and thus can't contact SCCM.

If I let it error and reboot, it boots w2k3 no problem, except the NICs won't start. I tried the DDP drivers (version 4.0.0.0), but that didn't work either. The ones from dell.com are 4.4.0.0.

W2k8 works fine, joins the domain, goes to the correct OU, installs OMSA, SAV, and other packages I have.

I haven't tested the staging of the GUID yet, will try shortly.

Tried pre-staging the blade, but some problem. I found the GUID in the Unprovisioned Computers as "4C4C4544-0056-3010-804C-B1C04F334731", but I just noticed that when it booted up, the GUID showed 45444C4C-0056-3010-804C-B1C04F334731 (first group is transposed).

Not sure why it would show the two different GUIDs.

**EDIT**
The GUID was more off than I originally noted:
First is from the console during pxe boot, second was in unprov. comp. in SCCM:
444454C4C-5600-1030-804C-B1C04F334731
4C4C4544-0056-3010-804C-B1C04F334731

**EDIT 2**
Despite SCCM requesting a GUID, it lists it as the System UUID, and "SMS Unique Identifier" starts with "GUID:" with what appears to be a randomly generated hex number following.

"Tried pre-staging the blade, but some problem. I found the GUID in the Unprovisioned Computers as "4C4C4544-0056-3010-804C-B1C04F334731", but I just noticed that when it booted up, the GUID showed 45444C4C-0056-3010-804C-B1C04F334731 (first group is transposed).

Not sure why it would show the two different GUIDs.

**EDIT**
The GUID was more off than I originally noted:
First is from the console during pxe boot, second was in unprov. comp. in SCCM:
444454C4C-5600-1030-804C-B1C04F334731
4C4C4544-0056-3010-804C-B1C04F334731

**EDIT 2**
Despite SCCM requesting a GUID, it lists it as the System UUID, and "SMS Unique Identifier" starts with "GUID:" with what appears to be a randomly generated hex number following."

Never noticed that before. I take look at it tommorow...

I tried staging it by the MAC only and no difference. I also noticed that when it's staged, you can set variables on the computer object, so I set RebootStep to 0 hoping it would increment, but it didn't change anything.

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?

Where is the log located? Whey mine fails, there are no logs on the host.

Logs are on different places, but the most important:

X:\Windows\temp\SMSTSlog\smsts.log

or

C:\SMSTSlog\smsts.log

Open it in trace32 and you can simply see each error (highlighted with a color)
Install ConfigMgr 2007 Toolkit Package for the trace32 tool.