• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Locked

‎02-22-2018 08:53 AM

HP Recommended
Product: T630
Operating System: Microsoft Windows 10 (64-bit)

Hi All,

 

In the middle of implementing HPDM at a customer location. Using a server in a DC and a NAS onpremise for a local repository. Repositories setup succesfully and tests are succesfull.

Image Capture was succesfully, but pushing an image does not work. We keep getting this error on HPDM:

 

Failed to execute DeployImage task.
ErrorCode: 1083392, Error Info:  ..\..\Task\common\ImageTask.cpp@255: Failed to connect the shared folder.

 

After logging in to the T630 and inspecting the wpeinit.log the following error shows up:

 

==== Initializing Network Access and Applying Configuration ====
2018-02-19 17:27:48.011, Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
2018-02-19 17:27:48.027, Info      Waiting on the profiling mutex handle
2018-02-19 17:27:48.027, Info      Acquired profiling mutex
2018-02-19 17:27:48.043, Info      Install MS_MSCLIENT: 0x00000000
2018-02-19 17:27:48.043, Info      Install MS_NETBIOS: 0x00000000
2018-02-19 17:27:48.043, Info      Install MS_SMB: 0x00000000
2018-02-19 17:27:48.043, Info      Install MS_TCPIP6: 0x00000000
2018-02-19 17:27:48.043, Info      Install MS_TCPIP: 0x00000000
2018-02-19 17:27:48.043, Info      Service dhcp start: 0x00000000
2018-02-19 17:27:48.043, Info      Service lmhosts start: 0x00000000
2018-02-19 17:27:48.043, Info      Service ikeext start: 0x00000000
2018-02-19 17:27:48.043, Info      Service mpssvc start: 0x00000000
2018-02-19 17:27:48.043, Info      Released profiling mutex
2018-02-19 17:27:48.043, Info      Spent 15ms installing network components
2018-02-19 17:27:50.070, Info      Installing device pci\ven_10ec&dev_8168&subsys_8158103c&rev_15 X:\windows\INF\oem4.inf succeeded
2018-02-19 17:27:50.788, Info      Spent 2746ms installing network drivers
2018-02-19 17:27:50.835, Error     QueryAdapterStatus: no adapters found.
2018-02-19 17:27:50.835, Info      Spent 16ms confirming network initialization; status 0x80004005
2018-02-19 17:27:50.835, Info      WaitForNetworkToInitialize failed; ignoring error
2018-02-19 17:27:50.835, Info      STATUS: SUCCESS (0x003d0001)

 

I am looking for a way to solve this issue. I asume i need to update some drivers? I found the winPE.tar.gz in the repository WESTools. But i cant imagine i have to update this one.

We are using HPDM 4.7 SP8.

 

Hope someone can help me out here.

 

Mark

1 ACCEPTED SOLUTION

Accepted Solutions

‎03-05-2018 05:17 PM

HP Recommended

Hi, 

 

This seems to be a known issue of t630 and should have been fixed it in SP8.

 

By default, the WINPE will load the driver dynamically when doing the imaging task. But for t630 and t730, as you can see it in the imagingprogress.ling process.og,

 

2018-03-05 11:00:53 INFO  ##PRINT##Loading network adapter drivers
2018-03-05 11:01:04 INFO  DrvLoad: The driver requires the machine to reboot C:\winpe\net\hp640x64.inf.

 

The reboot will interrupt the image process. To fix the issue we have integrated the driver into the WinPE.

 

Could you please go to \Repository\Tools\Imaging\WinPE\sources to check the size of boot.wim file? It should be 236,929 kb in both MasterRepository and Child Repository. 

 

I guess the issue is becuase the wim file in the Chile Repository has not been synced before imaging. If this is the case, simply copy the wim file from MasterRepository to Child Repository will fix the 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**

View solution in original post

Was this reply helpful? Yes No
4 REPLIES 4

‎03-01-2018 05:29 PM

HP Recommended

A dumb question - do you have multiple Repositories or just one? Please be aware that when capturing, the image file go directly to MasterRepository while for deploying, it is from the Child Repository if there is any.

 

Can you please attach agent.log and imageprogress.log in c:\windows\xpeagent when the error happen?

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**
Was this reply helpful? Yes No

‎03-05-2018 02:41 AM - edited ‎03-05-2018 03:31 AM

HP Recommended

Hello Chen,

 

Yes we are using 2 repositories:

 

- HPDM server at site B (Datacenter)

- Synology NAS at Site A (onpremise)

 

I was able to capture an image from a thin client. Depolying is the issue here.

From repository management I am able to succesfully pass the tests for SFTP and Shared folder.

 

Here by the log's. Tried on a HP T630.

- Agent.log  (Time doesnt seem to match. Wriong time within pxe?)

2017-03-13 23:03:35 INFO  Unified Write Fitler present.
2017-03-13 23:03:45 INFO  Agent starts.
2017-03-13 23:03:45 INFO  Read persistent data successfully.
2017-03-13 23:03:45 INFO  HM Code is valid.
2017-03-13 23:03:45 INFO  strVal=, Gateway=
2017-03-13 23:03:45 INFO  SaveConfigReg(), Gateway=
2017-03-13 23:03:45 ERROR Try to get basic network information.
2017-03-13 23:06:41 INFO  Unified Write Fitler present.
2017-03-13 23:06:51 INFO  Agent starts.
2017-03-13 23:06:51 INFO  Read persistent data successfully.
2017-03-13 23:06:51 INFO  HM Code is valid.
2017-03-13 23:06:51 INFO  strVal=, Gateway=
2017-03-13 23:06:51 INFO  SaveConfigReg(), Gateway=
2017-03-13 23:06:51 ERROR Try to get basic network information.
2017-03-13 23:11:15 INFO  Unified Write Fitler present.
2017-03-13 23:11:25 INFO  Agent starts.
2017-03-13 23:11:25 INFO  Read persistent data successfully.
2017-03-13 23:11:25 INFO  HM Code is valid.
2017-03-13 23:11:25 INFO  strVal=, Gateway=
2017-03-13 23:11:25 INFO  SaveConfigReg(), Gateway=
2017-03-13 23:11:25 ERROR Try to get basic network information.

- ImagingProgress.log

2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET SHARE="\\172.20.110.15\hpdm\Repository\Images\T630-Win10-V1-Template"
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET IMAGE="T630-Win10-V1-Image.ibr"
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET isClone=0
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET hdNO=hd0
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET BACKUPFILE=:\repack\Wes8ImageTool\Backup.cmd
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET RESTOREFILE=x:\repack\Wes8ImageTool\Restore.cmd
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET isPreload=0
2018-03-05 11:00:52 INFO
2018-03-05 11:00:52 INFO  C:\>SET isWES7ToWin10IoTUpgrade=0
2018-03-05 11:00:53 INFO  ##PRINT##Loading network adapter drivers
2018-03-05 11:01:04 INFO  DrvLoad: The driver requires the machine to reboot C:\winpe\net\hp640x64.inf.
2018-03-05 11:01:04 INFO  ##PRINT##Initializing Windows PE
2018-03-05 11:01:07 INFO  ##PRINT##Backup task files
2018-03-05 11:01:07 INFO          1 file(s) copied.
2018-03-05 11:01:07 INFO          1 file(s) copied.
2018-03-05 11:01:07 INFO  ##PRINT##Backup Other files
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\Backup.cmd
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\Config.ini
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\DisableAgent.reg
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\hpdmagent.cmd
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\NoGateway.key
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\repack.cmd
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\Restore.cmd
2018-03-05 11:01:07 INFO  C:\repack\Wes8ImageTool\TSCalLicense.reg
2018-03-05 11:01:07 INFO          8 file(s) copied.
2018-03-05 11:01:07 INFO          1 file(s) copied.
2018-03-05 11:01:07 INFO          1 file(s) copied.
2018-03-05 11:01:07 INFO          1 file(s) copied.
2018-03-05 11:01:07 INFO          1 file(s) copied.
2018-03-05 11:01:07 INFO  C:\windows\xpeagent\.tasks\*
2018-03-05 11:01:07 INFO          0 file(s) copied.
2018-03-05 11:01:07 INFO  C:\windows\xpeagent\.tasks\schedule\*
2018-03-05 11:01:07 INFO          0 file(s) copied.
2018-03-05 11:01:07 INFO  C:\windows\xpeagent\.tasks\trigger\*
2018-03-05 11:01:07 INFO          0 file(s) copied.
2018-03-05 11:01:07 INFO  C:\windows\xpeagent\.report\*
2018-03-05 11:01:07 INFO          0 file(s) copied.
2018-03-05 11:01:07 INFO  C:\windows\xpeagent\.report\trigger\*
2018-03-05 11:01:07 INFO          0 file(s) copied.
2018-03-05 11:01:07 INFO  ##PRINT##Set up share folder
2018-03-05 11:01:07 INFO
2018-03-05 11:01:07 INFO  Windows IP Configuration
2018-03-05 11:01:07 INFO
2018-03-05 11:01:07 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:01:07 INFO  this operation.
2018-03-05 11:01:17 INFO
2018-03-05 11:01:17 INFO  Windows IP Configuration
2018-03-05 11:01:17 INFO
2018-03-05 11:01:17 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:01:17 INFO  this operation.
2018-03-05 11:01:27 INFO
2018-03-05 11:01:27 INFO  Windows IP Configuration
2018-03-05 11:01:27 INFO
2018-03-05 11:01:27 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:01:27 INFO  this operation.
2018-03-05 11:01:37 INFO
2018-03-05 11:01:37 INFO  Windows IP Configuration
2018-03-05 11:01:37 INFO
2018-03-05 11:01:38 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:01:38 INFO  this operation.
2018-03-05 11:01:47 INFO
2018-03-05 11:01:47 INFO  Windows IP Configuration
2018-03-05 11:01:47 INFO
2018-03-05 11:01:48 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:01:48 INFO  this operation.
2018-03-05 11:01:57 INFO
2018-03-05 11:01:57 INFO  Windows IP Configuration
2018-03-05 11:01:57 INFO
2018-03-05 11:01:58 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:01:58 INFO  this operation.
2018-03-05 11:02:07 INFO
2018-03-05 11:02:07 INFO  Windows IP Configuration
2018-03-05 11:02:07 INFO
2018-03-05 11:02:08 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:02:08 INFO  this operation.
2018-03-05 11:02:17 INFO
2018-03-05 11:02:17 INFO  Windows IP Configuration
2018-03-05 11:02:17 INFO
2018-03-05 11:02:18 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:02:18 INFO  this operation.
2018-03-05 11:02:27 INFO
2018-03-05 11:02:27 INFO  Windows IP Configuration
2018-03-05 11:02:27 INFO
2018-03-05 11:02:28 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:02:28 INFO  this operation.
2018-03-05 11:02:38 INFO
2018-03-05 11:02:38 INFO  Windows IP Configuration
2018-03-05 11:02:38 INFO
2018-03-05 11:02:38 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:02:38 INFO  this operation.
2018-03-05 11:02:48 INFO
2018-03-05 11:02:48 INFO  Windows IP Configuration
2018-03-05 11:02:48 INFO
2018-03-05 11:02:48 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:02:48 INFO  this operation.
2018-03-05 11:02:58 INFO
2018-03-05 11:02:58 INFO  Windows IP Configuration
2018-03-05 11:02:58 INFO
2018-03-05 11:02:58 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:02:58 INFO  this operation.
2018-03-05 11:03:08 INFO
2018-03-05 11:03:08 INFO  Windows IP Configuration
2018-03-05 11:03:08 INFO
2018-03-05 11:03:08 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:03:08 INFO  this operation.
2018-03-05 11:03:18 INFO
2018-03-05 11:03:18 INFO  Windows IP Configuration
2018-03-05 11:03:18 INFO
2018-03-05 11:03:18 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:03:18 INFO  this operation.
2018-03-05 11:03:28 INFO
2018-03-05 11:03:28 INFO  Windows IP Configuration
2018-03-05 11:03:28 INFO
2018-03-05 11:03:28 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:03:28 INFO  this operation.
2018-03-05 11:03:38 INFO
2018-03-05 11:03:38 INFO  Windows IP Configuration
2018-03-05 11:03:38 INFO
2018-03-05 11:03:38 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:03:38 INFO  this operation.
2018-03-05 11:03:48 INFO
2018-03-05 11:03:48 INFO  Windows IP Configuration
2018-03-05 11:03:48 INFO
2018-03-05 11:03:48 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:03:48 INFO  this operation.
2018-03-05 11:03:58 INFO
2018-03-05 11:03:58 INFO  Windows IP Configuration
2018-03-05 11:03:58 INFO
2018-03-05 11:03:58 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:03:58 INFO  this operation.
2018-03-05 11:04:08 INFO
2018-03-05 11:04:08 INFO  Windows IP Configuration
2018-03-05 11:04:08 INFO
2018-03-05 11:04:08 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:04:08 INFO  this operation.
2018-03-05 11:04:18 INFO
2018-03-05 11:04:18 INFO  Windows IP Configuration
2018-03-05 11:04:18 INFO
2018-03-05 11:04:18 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:04:18 INFO  this operation.
2018-03-05 11:04:28 INFO
2018-03-05 11:04:28 INFO  Windows IP Configuration
2018-03-05 11:04:28 INFO
2018-03-05 11:04:28 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:04:28 INFO  this operation.
2018-03-05 11:04:38 INFO
2018-03-05 11:04:38 INFO  Windows IP Configuration
2018-03-05 11:04:38 INFO
2018-03-05 11:04:38 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:04:38 INFO  this operation.
2018-03-05 11:04:48 INFO
2018-03-05 11:04:48 INFO  Windows IP Configuration
2018-03-05 11:04:48 INFO
2018-03-05 11:04:48 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:04:48 INFO  this operation.
2018-03-05 11:04:58 INFO
2018-03-05 11:04:58 INFO  Windows IP Configuration
2018-03-05 11:04:58 INFO
2018-03-05 11:04:58 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:04:58 INFO  this operation.
2018-03-05 11:05:08 INFO
2018-03-05 11:05:08 INFO  Windows IP Configuration
2018-03-05 11:05:08 INFO
2018-03-05 11:05:08 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:05:08 INFO  this operation.
2018-03-05 11:05:18 INFO
2018-03-05 11:05:18 INFO  Windows IP Configuration
2018-03-05 11:05:18 INFO
2018-03-05 11:05:19 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:05:19 INFO  this operation.
2018-03-05 11:05:28 INFO
2018-03-05 11:05:28 INFO  Windows IP Configuration
2018-03-05 11:05:28 INFO
2018-03-05 11:05:29 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:05:29 INFO  this operation.
2018-03-05 11:05:38 INFO
2018-03-05 11:05:38 INFO  Windows IP Configuration
2018-03-05 11:05:38 INFO
2018-03-05 11:05:39 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:05:39 INFO  this operation.
2018-03-05 11:05:48 INFO
2018-03-05 11:05:48 INFO  Windows IP Configuration
2018-03-05 11:05:48 INFO
2018-03-05 11:05:49 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:05:49 INFO  this operation.
2018-03-05 11:05:58 INFO
2018-03-05 11:05:58 INFO  Windows IP Configuration
2018-03-05 11:05:58 INFO
2018-03-05 11:05:59 INFO  The operation failed as no adapter is in the state permissible for
2018-03-05 11:05:59 INFO  this operation.
2018-03-05 11:06:09 INFO  Software Loopback Interface 1
2018-03-05 11:06:09 INFO  Loopback Pseudo-Interface 1
2018-03-05 11:06:09 INFO  Software Loopback Interface 1
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:09 INFO  1231
2018-03-05 11:06:12 INFO  The operation completed successfully.
2018-03-05 11:06:14 INFO  ##PRINT##Reboot
2018-03-05 11:06:17 INFO  The operation completed successfully.
2018-03-05 11:06:20 INFO  The operation completed successfully.

- wpeinit.log

2018-03-05 11:01:04.686, Info      No unattend file was found; WPEINIT is using default settings to initialize WinPE
2018-03-05 11:01:04.686, Info      ==== Initializing Display Settings ====
2018-03-05 11:01:04.686, Info      No display settings specified
2018-03-05 11:01:04.686, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:04.686, Info      ==== Initializing Computer Name ====
2018-03-05 11:01:04.686, Info      Generating a random computer name
2018-03-05 11:01:04.686, Info      Computer is already named and no new name is specified, returning success.
2018-03-05 11:01:04.686, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:04.686, Info      ==== Initializing Virtual Memory Paging File ====
2018-03-05 11:01:04.686, Info      No WinPE page file setting specified
2018-03-05 11:01:04.686, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:04.686, Info      ==== Initializing Optional Components ====
2018-03-05 11:01:04.686, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:04.686, Info      ==== Initializing Network Access and Applying Configuration ====
2018-03-05 11:01:04.686, Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
2018-03-05 11:01:04.686, Info      Waiting on the profiling mutex handle
2018-03-05 11:01:04.686, Info      Acquired profiling mutex
2018-03-05 11:01:04.717, Info      Install MS_MSCLIENT: 0x00000000
2018-03-05 11:01:04.717, Info      Install MS_NETBIOS: 0x00000000
2018-03-05 11:01:04.717, Info      Install MS_SMB: 0x00000000
2018-03-05 11:01:04.717, Info      Install MS_TCPIP6: 0x00000000
2018-03-05 11:01:04.717, Info      Install MS_TCPIP: 0x00000000
2018-03-05 11:01:04.717, Info      Service dhcp start: 0x00000000
2018-03-05 11:01:04.717, Info      Service lmhosts start: 0x00000000
2018-03-05 11:01:04.717, Info      Service ikeext start: 0x00000000
2018-03-05 11:01:04.717, Info      Service mpssvc start: 0x00000000
2018-03-05 11:01:04.717, Info      Released profiling mutex
2018-03-05 11:01:04.717, Info      Spent 31ms installing network components
2018-03-05 11:01:06.714, Info      Installing device pci\ven_10ec&dev_8168&subsys_8158103c&rev_15 X:\windows\INF\oem4.inf succeeded
2018-03-05 11:01:07.447, Info      Spent 2730ms installing network drivers
2018-03-05 11:01:07.478, Error     QueryAdapterStatus: no adapters found.
2018-03-05 11:01:07.478, Info      Spent 0ms confirming network initialization; status 0x80004005
2018-03-05 11:01:07.478, Info      WaitForNetworkToInitialize failed; ignoring error
2018-03-05 11:01:07.478, Info      STATUS: SUCCESS (0x003d0001)
2018-03-05 11:01:07.478, Info      ==== Applying Firewall Settings ====
2018-03-05 11:01:07.478, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:07.478, Info      ==== Executing Synchronous User-Provided Commands ====
2018-03-05 11:01:07.478, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:07.478, Info      ==== Executing Asynchronous User-Provided Commands ====
2018-03-05 11:01:07.478, Info      STATUS: SUCCESS (0x00000001)
2018-03-05 11:01:07.478, Info      ==== Applying Shutdown Settings ====
2018-03-05 11:01:07.478, Info      No shutdown setting was specified
2018-03-05 11:01:07.478, Info      STATUS: SUCCESS (0x00000001)

Was this reply helpful? Yes No

‎03-05-2018 05:17 PM

HP Recommended

Hi, 

 

This seems to be a known issue of t630 and should have been fixed it in SP8.

 

By default, the WINPE will load the driver dynamically when doing the imaging task. But for t630 and t730, as you can see it in the imagingprogress.ling process.og,

 

2018-03-05 11:00:53 INFO  ##PRINT##Loading network adapter drivers
2018-03-05 11:01:04 INFO  DrvLoad: The driver requires the machine to reboot C:\winpe\net\hp640x64.inf.

 

The reboot will interrupt the image process. To fix the issue we have integrated the driver into the WinPE.

 

Could you please go to \Repository\Tools\Imaging\WinPE\sources to check the size of boot.wim file? It should be 236,929 kb in both MasterRepository and Child Repository. 

 

I guess the issue is becuase the wim file in the Chile Repository has not been synced before imaging. If this is the case, simply copy the wim file from MasterRepository to Child Repository will fix the 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**
Was this reply helpful? Yes No

‎03-06-2018 04:56 AM

HP Recommended

Hi Chen,

 

Thank you for your assistance. I concluded that the file you mentioned did not have the right size. it was 178.785 KB. With SP8 installed! I can see the version in Programs saying SP8. So i ran the SP8 install again and during the install i noticed the size of the file changing: It now is 236.929 KB. After syncing the repositories i saw that the file size in the repository was not changend, despite the sync was showing succesfull, so i copied the boot.wim manually.

 

I tried to send a image to a T730 and it was succesfull!

 

Thank you for your assistance.

 

Mark

Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† 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.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.