Trying to deploy Win 8 ENT to HP Elitepad 900

[goudviske]

Hi,

 

Short version:

Tried deploying win 8 to HP Elitepad tablet computers.

 

When trying to deploy over PXE, I encountered some issues (more here http://www.windows-noob.com/forums/index.php?/topic/8045-trying-to-deploy-over-pxe-uefi-x86-with-wds-2012/), I think they're related to pxe booting a x86 uefi machine, which my wds 2012 doesn't seem to like...

 

After a couple of days I thought why not try to deploy it over USB, created a task sequence, configured media on the WDS and tried deploying it. At first I hit some issues related to disk partitioning, that seemed to be resolved, but maybe it isn't entirely.

 

What happens now is:

- Elitepad boots on USB

- Task sequence performs a few tasks

- prepares

- formats the disk (uefi)

- injects drivers

- uses imagex to expand the previously captured .wim

- reboots

 

Then when rebooting I get a new style of blue screen.

This shows:

 

 

the operating system couldn't be loaded because a critical system

driver is missing or contains errors

file: \windows\system32\drivers\megasas2.sys

Error Code: 0xc000035e

I suppose it has something to do with drivers for the storage controller, but I don't quite get what's wrong, the drivers are installed correctly in the .wim, so after restoring that should be ok, and also they are injected during the earlier phases.

I think it may have something to do with which partition is active, but I can't seem to get it resolved.

Any thoughts/ideas/... ?

Thanks

 

[zemerick]

I left it going in the office overnight. If it's still going when I get to the office in the morning I will take out that switch.

[zemerick]

"Successfully completed the action (install Elitepad KB Package) with the exit win32 code 0"

 

Then it looks like it moved on to the Root update

Expand a string: FullOS	TSManager	8/15/2013 8:26:54 PM	2136 (0x0858)
Executing command line: smsswd.exe /pkg:OCS00027 /install /basevar: /continueOnError:	TSManager	8/15/2013 8:26:54 PM	2136 (0x0858)
[ smsswd.exe ]	InstallSoftware	8/15/2013 8:26:55 PM	3948 (0x0F6C)
PackageID = 'OCS00027'	InstallSoftware	8/15/2013 8:26:55 PM	3948 (0x0F6C)
BaseVar = '', ContinueOnError=''	InstallSoftware	8/15/2013 8:26:55 PM	3948 (0x0F6C)
ProgramName = 'Root Certificate Update'	InstallSoftware	8/15/2013 8:26:55 PM	3948 (0x0F6C)
SwdAction = '0002'	InstallSoftware	8/15/2013 8:26:55 PM	3948 (0x0F6C)

then the log ends (smsts-[date].log)

 

in smsts.log I see:

Failed to set log directory. Some execution history may be lost. 
The system cannot find the file specified. (Error: 80070002; Source: Windows)	OSDSetupHook	8/15/2013 8:27:50 PM	1744 (0x06D0)
Executing task sequence	OSDSetupHook	8/15/2013 8:27:50 PM	1744 (0x06D0)
Task Sequence environment not found.	OSDSetupHook	8/15/2013 8:27:50 PM	1744 (0x06D0)
Attempting to get active request.	OSDSetupHook	8/15/2013 8:27:50 PM	1744 (0x06D0)
Failed to create instance if Software Execution Request Managerr. 0x80070005	OSDSetupHook	8/15/2013 8:27:50 PM	1744 (0x06D0)
Waiting for ccmexec process to start.	OSDSetupHook	8/15/2013 8:27:50 PM	1744 (0x06D0)
Failed to create instance if Software Execution Request Managerr. 0x80070005	OSDSetupHook	8/15/2013 8:27:55 PM	1744 (0x06D0)
Waiting for ccmexec process to start.	OSDSetupHook	8/15/2013 8:27:55 PM	1744 (0x06D0)
Failed to create instance if Software Execution Request Managerr. 0x80070005	OSDSetupHook	8/15/2013 8:28:00 PM	1744 (0x06D0)
Waiting for ccmexec process to start.	OSDSetupHook	8/15/2013 8:28:00 PM	1744 (0x06D0)
GetActiveRequest failed with error code 0x87d01012	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
GetActiveRequest failed. 0x87D01012.	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
ReleaseActiveRequest failed. 0x87d01012.	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Deleting SMS_MaintenanceTaskRequests istance: SMS_MaintenanceTaskRequests.TaskID="{C87232DE-BBBA-4899-9F70-F046D9298422}".	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Removed 1 instance of SMS_MaintenanceTaskRequests for tasksequence.	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Uninstalling Setup Hook	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Removing setup hook from registry.	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Successfully removed C:\WINDOWS\system32\OSDGINA.DLL	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Successfully removed C:\WINDOWS\system32\_SMSOSDSetup	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
GetTsRegValue() failed. 0x80070002.	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
End program: 	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs	OSDSetupHook	8/15/2013 8:28:07 PM	1744 (0x06D0)

[TKilmer50]

 

I used DISM to update the image with .net (You need to extract SXS folder from the win8 .iso)

 

dism.exe /mount-wim /wimfile:C:\DISM\Win8x86_golden.wim /index:2 /mountdir:C:\DISM\mount

dism.exe /Image:c:\DISM\mount /enable-feature /featurename:netFX3 /All /Source:C:\Temp\sxs

dism.exe /Unmount-Image /MountDir:c:\DISM\mount /Commit

 

I have imaged about 30 of these devices, 30 more to go. Some seem to just randomly fail at the BIOS update stage, annoying. I see HP have a new Driver and Firmware Update so may give that a go

Thanks. This is the direction I went. We have a GPO that doesn't allow downloads from windows updates and - even with the stand alone installer - it downloads from windows update anyway; another point of frustration with Win 8. The method you posted works well; thanks.

 

Zemerick: When a log abruptly stops, you'll want to chase down the new log location. It moves (or some become more useful/less useful) as the task sequence hits various steps.

I used dir /s *.log | more to help find all the log files in various directories. The log you posted should give you some direction to dig in; i'm not familiar with that particular error.

 

Good luck!

[Omeganator]

We just completed a deployment of the HP Elitepad 900 using CM2012 Standalone Media. I wanted to share an issue and solution I encountered: out of the box, the data/time was far off from the current time. This caused the task sequence to pause indefinitely, since the system time preceded the time the base WIM was created. Smsts.log displayed "Waiting for job status notification..." Set the current time on these if running from standalone media!!

[zemerick]

I got down to copy the BiosUpdate locally. with this:

 

cmd.exe /C c:\Windows\System32\robocopy.exe \\ocs12\deploy$\Drivers\Extracted\HP-Driver-Firmware-and-Chipset\hp\sp60725 c:\BiosUpdate /MIR /R:3 (Disable 64-bit file redirection is ticked)

 

However even though the files do copy the TS fails with "Incorrect Function" 0x00000001 I then have to run the FDSETUP -s -f manually then It finishes as it should. Anyone got an idea?

[zemerick]

I got down to copy the BiosUpdate locally. with this:

 

cmd.exe /C c:\Windows\System32\robocopy.exe \\ocs12\deploy$\Drivers\Extracted\HP-Driver-Firmware-and-Chipset\hp\sp60725 c:\BiosUpdate /MIR /R:3 (Disable 64-bit file redirection is ticked)

 

However even though the files do copy the TS fails with "Incorrect Function" 0x00000001 I then have to run the FDSETUP -s -f manually then It finishes as it should. Anyone got an idea?

I finally got it imaged but a few drivers were missing. Going to have to narrow that one down. The above is correct the time was very far off in the bios and task sequence would not run. I have to open a cmd prompt and set the date and time before entering in the password for the task sequence.

 

Also to note you don't have to copy the bios locally via a Xcopy command as you can just specify the package when running a command line task in the task sequence and running fdsetup -S -F

 

You don't need to load all of the winpe drivers in the boot image either or it will fail. You only need to load the usb to ethernet drivers for the task sequence to work correctly. I also removed the install kb package from the deploy sequence as it takes entirely too long to install on deployments. It's much better to install it when capturing the image.

 

I plan to make a full tutorial based in part on rocket man's and the HP docs so no one will go through the headaches iI did to get one of these devices imaged. It's a real nightmare based on current documentation if you're doing it over pxe especially. Shame on HP.

[derrynm]

Hi,

 

Short version:

Tried deploying win 8 to HP Elitepad tablet computers.

 

When trying to deploy over PXE, I encountered some issues (more here http://www.windows-noob.com/forums/index.php?/topic/8045-trying-to-deploy-over-pxe-uefi-x86-with-wds-2012/), I think they're related to pxe booting a x86 uefi machine, which my wds 2012 doesn't seem to like...

 

After a couple of days I thought why not try to deploy it over USB, created a task sequence, configured media on the WDS and tried deploying it. At first I hit some issues related to disk partitioning, that seemed to be resolved, but maybe it isn't entirely.

 

What happens now is:

- Elitepad boots on USB

- Task sequence performs a few tasks

- prepares

- formats the disk (uefi)

- injects drivers

- uses imagex to expand the previously captured .wim

- reboots

 

Then when rebooting I get a new style of blue screen.

This shows:

 

 

the operating system couldn't be loaded because a critical system

driver is missing or contains errors

file: \windows\system32\drivers\megasas2.sys

Error Code: 0xc000035e

I suppose it has something to do with drivers for the storage controller, but I don't quite get what's wrong, the drivers are installed correctly in the .wim, so after restoring that should be ok, and also they are injected during the earlier phases.

I think it may have something to do with which partition is active, but I can't seem to get it resolved.

Any thoughts/ideas/... ?

Thanks

 

What was the driver you injected for the storage controller?

[DPE1983]

How long does it approx. take for FDsetup.exe to run during OSD? I've left it running for almost an hour without the TS moving to the reboot step..