cancel
Showing results for 
Search instead for 
Did you mean: 
ArchivedThis topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
jornvdcb
Level 1
7 5 0 0
Message 1 of 20
2,939
Flag Post

SCCM t730 - Windows setup could not configure windows to run on this computer's hardware

HP Recommended
t730
Microsoft Windows 10 (64-bit)

Dear all,

 

I'm having these problems regarding the deployment of Windows 10 iot 64 bit on these new Thin Clients t730.

I followed all the steps from the technical white papers from HP. I even tried alternative ways like MDT and more general settings but this error keeps prompting at the end of the deployment.

Anyone else here who has experienced this?

 

0 Kudos
19 REPLIES 19
Chen_HPDM
Level 7
Level 7
504 504 51 84
Message 2 of 20
Flag Post
HP Recommended

What's the error in the smts.log?  The error meesage on the screen usually is too general to get the root cause.

 

I'm able to capture & deploy win10 IoT image on t730 in my lab environment.

 

Please make sure to use the captured HP image as golden image for deployment.

I am an HPI Employee.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
0 Kudos
jornvdcb
Author
Level 1
7 5 0 0
Message 3 of 20
Flag Post
HP Recommended

Thanks for your involvement, these are the last and only lines that give back an answer. The image deploys succesful but keeps hanging at this error. Shift + f10 does not work for me so I cannot bypass this error with the msoobe fix the internet gives me 😕

 

 

SNAG-0354.png

0 Kudos
jornvdcb
Author
Level 1
7 5 0 0
Message 4 of 20
Flag Post
HP Recommended

This is the full log: there are a couple of failed errors but nothing that I believe could cause an issue

==============================[ TSMBootStrap.exe ]==============================	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Command line: TSMBootstrap.exe /env:FullOS 	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Current OS version is 10.0.10240.0	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Executing from Media in Full OS	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Verifying Media Layout.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
MediaType = FullMedia	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
PasswordRequired = false	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Executing stand-alone media in full operating system on a machine that is running a Configuration Manager client. 	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
User has sufficient security rights to create a service.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Running Wizard in Unattended mode	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Loading Media Variables from "D:\sms\data\variables.dat"	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
no password for vars file	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
If current logging settings specify more logging details to be preserved, udpate these settings in TS environment	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Current LogMaxSize is saved to TS environment since it has not been saved before	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Current LogMaxHistory is saved to TS environment since it has not been saved before	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Current LogLevel is saved to TS environment since it has not been saved before	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Current LogEnabled is saved to TS environment since it has not been saved before	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Current LogDebug is saved to TS environment since it has not been saved before	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
UEFI: true	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Loading variables from the Task Sequencing Removable Media.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Loading Media Variables from "D:\sms\data\variables.dat"	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Root CA Public Certs=	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Support Unknown Machines: 1	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Custom hook from D:\\TSConfig.INI is 	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
No hook is found to be executed before downloading policy	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Loading policy from D:\sms\data\Policy.XML.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Loading policy from file: D:\sms\data\Policy.XML	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
This Task sequence is set for RunFromDP	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Retrieving collection variable policy.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Found 0 collection variables.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Retrieving machine variable policy.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Found 0 machine variables.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting collection variables in the task sequencing environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting machine variables in the task sequencing environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Creating the Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting Media Variables in Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Resolving content location for selected task sequence.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Task sequence content location: 	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Getting policy for CCM_SoftwareDistribution[AdvertID="{522145E4-2C69-4F93-B1BE-B34CB6197B1A}", PackageID="GNK0019A", ProgramID="*"]	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Source version for package GNK0019A saved in the environment: _SMSTSSourceVersionGNK0019A = 3	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Successfully resolved policy for GNK0019A.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Resolving content location for GNK0019A	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
GNK0019A content location: file:VOL001:\SMS\PKG\GNK0019A	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
No need to register providers	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Registering the Progress UI.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Executing command line: "D:\SMS\BIN\x64\TsProgressUI.exe" /Register	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
==========[ TsProgressUI started in process 4184 ]==========	TsProgressUI	1/07/2016 14:21:41	3684 (0x0E64)
Registering COM classes	TsProgressUI	1/07/2016 14:21:41	3684 (0x0E64)
sbModulePath = D:\SMS\BIN\x64\TsProgressUI.exe	TsProgressUI	1/07/2016 14:21:41	3684 (0x0E64)
Shutdown complete.	TsProgressUI	1/07/2016 14:21:41	3684 (0x0E64)
Process completed with exit code 0	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Successfully registered TS Progress UI.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting Media Variables in Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting WinPE Flag in the Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting Media Type Flag in the Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting Local Computer Name in the Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting Selected Task Sequence Information Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting selected task sequence information in the environment.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting source for GNK0019A to file:VOL001:\SMS\PKG\GNK0019A	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Setting _SMSTSPKGFLAGSGNK0019A to 0	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Initializing the local data path.	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
DeviceIoControl() failed with GetLastError() = 1	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Ignoring inaccessible volume 'Z:' with error 0x80070001	TSMBootstrap	1/07/2016 14:21:41	5640 (0x1608)
Volume C:\ has attributes 0x00000000	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
C:\_SMSTaskSequence does not exist	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Updated security on object C:\_SMSTaskSequence.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting Task Sequence User State Path to "%_SMSTSMDataPath%\UserState".	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting Network Access Account Information in Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Cannot find NAAConfig CCM_NetworkAccessAccount	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Unable to get Network Access Account. Ignoring.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Found property CCM_ClientAgentConfig.BrandingTitle = H.Essers	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting Client ID in Task Sequencing Environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting machine name from SMS database.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Failed to retrieve the machine name from SMS database. Fall back to the current local computer name.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting SysHealthConfig policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting SoftUpdConfig policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting SoftDistClient config policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting software update policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting software update policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting quarantine policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting NAAConfig policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting CIVersionInfo policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting RebootSettingsConfig policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting AppManClientConfig policy in the environment.	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Media root drive is: D:\	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Setting launch mode to: UFD	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
copying files from d:\ to C:\_SMSTaskSequence	TSMBootstrap	1/07/2016 14:21:44	5640 (0x1608)
Executing command line: OsdCaptureCD.exe	TSMBootstrap	1/07/2016 14:21:48	5640 (0x1608)
==============================[ OSDCaptureCD.exe ]==============================	OSDCaptureCD	1/07/2016 14:21:48	3032 (0x0BD8)
Command line: "OsdCaptureCD.exe"	OSDCaptureCD	1/07/2016 14:21:48	3032 (0x0BD8)
Loading vista instructions.	OSDCaptureCD	1/07/2016 14:21:48	3032 (0x0BD8)
Activating Welcome Page.	OSDCaptureCD	1/07/2016 14:21:48	3032 (0x0BD8)
Verifying that this machine meets the capture requirements.	OSDCaptureCD	1/07/2016 14:21:54	3032 (0x0BD8)
Local machine is not a domain controller.	OSDCaptureCD	1/07/2016 14:21:54	3032 (0x0BD8)
System partition is NTFS	OSDCaptureCD	1/07/2016 14:21:54	3032 (0x0BD8)
Verified deploy tools are present.	OSDCaptureCD	1/07/2016 14:21:54	3032 (0x0BD8)
Local machine is not part of a domain	OSDCaptureCD	1/07/2016 14:21:54	3032 (0x0BD8)
Activating Destination Page.	OSDCaptureCD	1/07/2016 14:21:54	3032 (0x0BD8)
Activating Welcome Page.	OSDCaptureCD	1/07/2016 14:22:17	3032 (0x0BD8)
Activating Finish Page.	OSDCaptureCD	1/07/2016 14:22:17	3032 (0x0BD8)
Saving capture information in the environment.	OSDCaptureCD	1/07/2016 14:22:18	3032 (0x0BD8)
Adding OSDCaptureDestination to the path migration list.	OSDCaptureCD	1/07/2016 14:22:18	3032 (0x0BD8)
Exiting with return code 0x00000000	OSDCaptureCD	1/07/2016 14:22:18	3032 (0x0BD8)
Process completed with exit code 0	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Creating the TS Manager Service.	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Starting Task Sequence Manager Service.	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Modifying TS Manager Service to auto start.	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Starting the TS Manager Service.	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Successfully intialized Logging for TS Manager.	TSManager	1/07/2016 14:22:18	1588 (0x0634)
Commandline: "C:\_SMSTaskSequence\sms\bin\x64\TsManager.exe" /service /noclient /loghandle 5360 308	TSManager	1/07/2016 14:22:18	1588 (0x0634)
Successfully registered Task Sequencing COM Interface.	TSManager	1/07/2016 14:22:18	1588 (0x0634)
Executing as a service	TSManager	1/07/2016 14:22:18	1588 (0x0634)
Waiting for the TS Manager Service to start.	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Started ServiceMain	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Task Sequence Manager executing as service main thread	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Reading  logging settings from TS environment to set TS logging	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Deleting volume ID file Z:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Task Sequencing Manager Service successfully started.	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
Parsing task sequence . . .	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Task sequence schema version is 3.00	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Current supported schema version is 3.10 and 3.00	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Exiting with return code 0x00000000	TSMBootstrap	1/07/2016 14:22:18	5640 (0x1608)
No variables found in default variable list	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Starting Task Sequence Engine . . . 	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
****************************************************************************	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSNextInstructionPointer=0	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSInstructionTableSize=6	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable SMSTSRebootRequested=	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable SMSTSRebootDelay=	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable SMSTSRebootMessage=	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable SMSTSRebootReason=	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable SMSTSRetryRequested=	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
The task execution engine started execution	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Do not send status message in full media case	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Do not send status message in full media case	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Start executing an instruction. Instruction name: Capture the Reference Machine. Instruction pointer: 0	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSCurrentActionName=Capture the Reference Machine	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSNextInstructionPointer=0	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
The group (Capture the Reference Machine) has been successfully started	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Do not send status message in full media case	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Updated security on object C:\_SMSTaskSequence.	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSNextInstructionPointer=1	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a TS execution environment variable _SMSTSNextInstructionPointer=1	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSInstructionStackString=0	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a TS execution environment variable _SMSTSInstructionStackString=0	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Save the current environment block	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSLastActionRetryCount=0	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Start executing an instruction. Instruction name: Prepare Configuration Manager Client. Instruction pointer: 1	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSCurrentActionName=Prepare Configuration Manager Client	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSNextInstructionPointer=1	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Set a global environment variable _SMSTSLogPath=C:\windows\CCM\Logs\SMSTSLog	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Expand a string: osdpreparesmsclient.exe	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Expand a string: 	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Start executing the command line: osdpreparesmsclient.exe	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
!--------------------------------------------------------------------------------------------!	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Expand a string: FullOS	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Executing command line: osdpreparesmsclient.exe	TSManager	1/07/2016 14:22:18	3996 (0x0F9C)
Checks succeeded. Client meets capture requirements	PrepareSMSClient	1/07/2016 14:22:18	2500 (0x09C4)
Set TSEnv:SMSClientVersion=5.00.8239.1000 ok	PrepareSMSClient	1/07/2016 14:22:18	2500 (0x09C4)
Successfully enabled provisioning mode.	PrepareSMSClient	1/07/2016 14:22:19	2500 (0x09C4)
Waiting for CcmExec service to be fully operational	PrepareSMSClient	1/07/2016 14:22:19	2500 (0x09C4)
CcmExec service is up and fully operational	PrepareSMSClient	1/07/2016 14:22:38	2500 (0x09C4)
Cache contents deleted successfully	PrepareSMSClient	1/07/2016 14:22:38	2500 (0x09C4)
Stopped the service 'ccmexec' successfully	PrepareSMSClient	1/07/2016 14:22:59
0 Kudos
Chen_HPDM
Level 7
Level 7
504 504 51 84
Message 5 of 20
Flag Post
HP Recommended

You're right, the logs really doesn't help that much.

 

Since SHIFT +F10 doesn't work, suppose you're not about to run OOBE manually when the error happen.

 

 

When you were preparing the golden image, did you remove all the other account with only default administrator left? (Please make sure the system is not domian joined also.)

 

I saw another post from MSFT claims that SCCM 2012 R2 SP1 CU2 would fix the issue, but personally I doubt it as I'm using just SP1 and didn't see any issue with my deployment.

I am an HPI Employee.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
jornvdcb
Author
Level 1
7 5 0 0
Message 6 of 20
Flag Post
HP Recommended

Dear,

 

Sorry for the late reply. I only had two accounts left, "Administrator" & "User". This always worked.

We also use SCCM 2012 R2 SP1. I think I'll just leave it this way and deploy through USB. This year we are going to install the latest new SCCM when the new Windows server is released. Thanks for the help

0 Kudos
Frederik_1
New member
4 4 0 1
Message 7 of 20
Flag Post
HP Recommended

Dear,

 

Could we re open this issue?

I'm a colleague from the original poster.

 

We have received a new 150 pieces HP thin clients batch from the type t620 Flexible, running on Windows 10 IoT x64.

 

The error still appears when finalizing the installation via an SCCM deployment.

 

We tried the following with no success:

 

- install via an capured .WIM T620 stock image.


- install via the official HP image downloaded via the HP ThinUpdate tool. Renaming the .ibr file to an .WIM file.
   using this tool to create a USB recovery image works.

   I belive the diffirence is that a recovery will 1 : 1 copy the image via the USB,  Keeping all the settings the same (like hostname)
  In our SCCM setup, we need a new installation where Windows is actually installed and needs to go through every step for the first time.

 

- Changed the harddrive modes ( AHCI etc)

- removed the User account , only left was the administrator account.


What are we missing? Do I need to create an answer file with extra settings?
Many people could solve this issue running  "OOBE". unfortunately I could not test this myself( shift f10 isn't working)

 

I would realy appriciate it if someone could point me to the right direction!
Thanks in advance!

 

Kind regards,

 

Frederik

 

 

Chen_HPDM
Level 7
Level 7
504 504 51 84
Message 8 of 20
Flag Post
HP Recommended

How did you captured the .Wim image?  It should be captured by SCCM.

 

Please take a look at the new white paper here, there are plenty of screenshots and key points being updated.

 

http://h20566.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=5404706&docLocale=en_US&docId=emr_na-c04...

 

 

 

I am an HPI Employee.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
0 Kudos
Frederik_1
New member
4 4 0 1
Message 9 of 20
Flag Post
HP Recommended

Dear Chen,

 

Thanks for the reply.

 

We did capture the .wim via sccm.

And already followed the HP white paper.

Still no luck.

 

Did somone faced the same problems ?

 

We encounted this problem since we are using Windows 10 Thin clients.

Our sccm tasksequence runs just fine.
We can see it applying the operating system, installing the drivers....

At the last step, the thin client reboots en gets into the Windows environment.
Here it's dispaying the message "Getting ready" when it fails.

Any tips are welcome!

 

 

0 Kudos
Chen_HPDM
Level 7
Level 7
504 504 51 84
Message 10 of 20
Flag Post
HP Recommended

Well this helped me to recall something...

 

There was an issue being addressed by Microsoft regarding to SCCM deployment with Win10 image. The issue seems to be SCCM mistakely blocked the image with OEM product key. This is an industry problem not only impact HP product.

 

"On non-IoT versions of Windows, Setupcomplete.cmd is blocked when an OEM product key is used in order to provide customers a good out of box experience on new PCs. This block is not intended for IoT versions of Windows but is currently there due to a confirmed bug. Microsoft initially was planning to fix this bug only in Redstone-2"

 

Microsoft has provided a workaround and passed the first verification within HP - sorry I can't share that much details here.

 

The latest update I got is:

Microsoft is currently working on a blog which will document the workaround publically.

 

Maybe the blog with the workaround will fix your issue.

I am an HPI Employee.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
ArchivedThis topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation