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

OK It looks like I have cracked it.
If you are new to the Dell Deployment pack for SCCM07 like me, then do the following. Don't get too excited about the .ini files that come with DDT by creating your own just use the ones that come with the initial installation until you become more familiar. I deployed win 2003 server to a PE2950 x86. Simple deployment with two disks configured for RAID1.

1. After installation copy and then update the DP's with all the new packages that come with DDT however with the driver packages only do the ones you are interested in. It’s important that you update these packages once they have been copied. In my case 'PE2950 win2003 x86'. Also with Dell poweredge packages make sure you copy them to both the DP's and PXE DP's.

2. Create a TS by right clicking Task Sequences and selecting 'Bare metal Server Deployment' - 'Create a poweredge server deployment template'. fill out as much as you can but remember to only use the .ini files that come with it i.e. RAID Config - 5i-raid5.ini. You can always elaborate on this part once you have mastered the rest of the steps and completed a whole TS.

3.Change the following VBScript as detailed by sccm_ddp_eng in post 19. I quote “This problem is easy to fix…..The gsClientGuid variable is set in the OemDeployment.vbs script at line 520:
gsClientGuid = GetTaskSequenceVariable("_SMSTSClientGuid")
Simply change this code to the following:
gsClientGuid = GetTaskSequenceVariable("_SMSTSClientIdentity")”
Once done make sure you update the packages again.

The Oemdeployment.vbs script is located in the following path C:\Program Files\Microsoft Configuration Manager\OSD\lib\Packages\Deployment\Dell\PowerEdge\DTK2.6.

4. In the TS open all the ‘Set RebootStep Variable’ and ‘Reboot to PXE / USB’ and manually enter the password again. I assumed that it did this automatically but found that when I re-entered it manually it worked. I may have entered it incorrectly in the first place but you never know.

5. Once you have finished your TS create a new collection. I called mine ‘Dell Server Deployment’. Then Import a new computer by right clicking Computer association – Import Computer Information. Add a name and the MAC address of the server you want to deploy to. Don’t bother with the GUID, waste of time. You can’t get this to work with the R2 feature of unknown computers just yet. Dell are working on that.

6. Advertise the task sequence created earlier as a mandatory assignment. Make sure you set it to access content directly from the distribution point as PXE will not be able to download any files as the RAID and partitioning hasn’t happened yet so there is nothing to download to.

7. Turn off the computer and then boot it up. Make sure PXE is enabled in the BIOS of course. It should then be a case of sit back and enjoy the show. If you have password protected your PXE service point you will have to type it in again every time it reboots to PXE.

Hope this helps, Good Luck : -)

Hi TommyER
It sounds like it could be an issue with your OS image file. Is it a .wim file or does your TS point to source files with sysprep.inf?
It may also be an issue with the driver package you are using. Also, have you ticked the checkbox on the 'Apply Driver Package step' which starts with 'Select the mass storage driver' i don't think it is ticked by default so you may want to check yours.
How far into the boot up process do you get? Is it win 2003 or 2008. Does it start to load the OS and then produce the error message "Error loading OS".
Any more detail will be helpful.
Masby661

Hi Masby!
I'm installing from an original installation source where the task does the sysprep for me (ie I've not made a sysprep file). The OS is Windows Server 2003 Standard x86. I've ticked the checkbox for mass storage driver. I'm using the driver package PE0840-Microsoft Windows 2003 x86 since it's a PE 840 server I'm trying to install. The installation of the OS finishes and then reboots, it's then when the server is trying to load the OS the error message appears.

Tommy

I know the next step I suggest might be a bit time consuming and I don't know how much time you have, but it may be worth using a .wim file instead of the source files. What I do is build a machine, put sysprep into c:\sysprep folder then use the SCCM capture CD to create a .wim file i.e PE2950win2003.wim. When you use the SCCM capture CD you have the option of putting in a path to where you want to save the .wim file which is usually a network path however you may find it easier to save it to local USB storage (quicker and you don't run into network issues). From there you can then copy it to your SCCM server and then import it, distribute it, put into TS etc.
Give it a go and let me know how you get on.

I would want to make it work with original source installation and not a .wim file as that would save me much time in deploying new servers. Having googled it may not even be SCCM causing the problem rather the DRAC. I'm going to disable DRAC during installation which is recommended and try again. I'll keep you posted on how it goes.

Tommy

Hi Tommy,

Are you using the Apply device drivers step as well as the apply driver package step?.. Do u have a mass storage controller or only onboard SATA(As PE840 comes in both these configs). Try the deployment disabling the Apply Device drivers step.