Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
brommo
Visitor.
2126 views

WinPE imaging

Hello,

I'm working on moving over to WinPE imaging to overcome driver/compatibility issues with Linux imaging. However, I'm running into some trouble imaging certain devices.

Both fleets of HP Probook 430 G4 and Dell Latitude 3380 and experiencing the same problem. I'm assigning the appropriate imaging bundle and applying it to the devices, they boot into WinPE but fails. The WorkToDoDebug.txt on the device shows:

07/12/18 - 13:29:17 - connected to server 
07/12/18 - 13:29:17 - wstree sent
07/12/18 - 13:29:18 - found hardware also
07/12/18 - 13:29:18 - sent PSI
07/12/18 - 13:29:18 - reading data from server
07/12/18 - 13:29:18 - <ZENworks-Imaging><Type>Restore-ZENworks-winPE-Image</Type><File>C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg</File><ServerIP>172.16.0.142</ServerIP><FileSet>1</FileSet></ZENworks-Imaging>
07/12/18 - 13:29:18 - extracting params
07/12/18 - 13:29:18 - got WinPE ZMG restore image work
07/12/18 - 13:29:18 - C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg
07/12/18 - 13:29:18 - 172.16.0.142
07/12/18 - 13:29:18 - got winpe File Set value
07/12/18 - 13:29:18 - updating ISD as attempting
07/12/18 - 13:29:18 - Got ZENworks WinPE Imaging task
07/12/18 - 13:29:18 - NOVELL_FIRMWARE_UEFI set by user,Consider firmware Type Flag : UEFI
07/12/18 - 13:29:18 - Firmware Type Flag : UEFI
07/12/18 - 13:29:18 - Img invoked from WinPE manual mode
07/12/18 - 13:29:18 - Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1
07/12/18 - 13:29:34 - NOVELL_FIRMWARE_UEFI set by user,Consider firmware Type Flag : UEFI
07/12/18 - 13:29:34 - Firmware Type Flag : UEFI
07/12/18 - 13:29:34 - ZISD task state and return code:4 802
07/12/18 - 13:29:34 - Failed to complete ZENWorks WinPE Imaging work


I boot into WinPE maintenance mode and run following command:

img -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=xxx.xxx.xxx.xxx


It creates the partitions then comes up with:

Error: Error reading from archive


Both devices obtain an IP addresses in WinPE and I can ping the image repo. I've added the latest NIC drivers to the .wim and updated BIOS on both.

The same bundle works on other devices without a problem.
Labels (1)
0 Likes
13 Replies
Micro Focus Expert
Micro Focus Expert

Re: WinPE imaging

Is the HDD a Spindle Drive or some type of Solid State Drive?
SSD compatibility can be an issue in many different WinPE Versions.
The fact the partitions are create may not be sufficient to know they are fully operational.....

Just a total guess.....

For Example....Some Intel Based SSDs needed firmware upgrades to fix W10v1803 issues....even though the worked in v1709....not sure if they eventually avoided firmware updates by differnet drivers....


brommo;2492122 wrote:
Hello,

I'm working on moving over to WinPE imaging to overcome driver/compatibility issues with Linux imaging. However, I'm running into some trouble imaging certain devices.

Both fleets of HP Probook 430 G4 and Dell Latitude 3380 and experiencing the same problem. I'm assigning the appropriate imaging bundle and applying it to the devices, they boot into WinPE but fails. The WorkToDoDebug.txt on the device shows:

07/12/18 - 13:29:17 - connected to server 
07/12/18 - 13:29:17 - wstree sent
07/12/18 - 13:29:18 - found hardware also
07/12/18 - 13:29:18 - sent PSI
07/12/18 - 13:29:18 - reading data from server
07/12/18 - 13:29:18 - <ZENworks-Imaging><Type>Restore-ZENworks-winPE-Image</Type><File>C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg</File><ServerIP>172.16.0.142</ServerIP><FileSet>1</FileSet></ZENworks-Imaging>
07/12/18 - 13:29:18 - extracting params
07/12/18 - 13:29:18 - got WinPE ZMG restore image work
07/12/18 - 13:29:18 - C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg
07/12/18 - 13:29:18 - 172.16.0.142
07/12/18 - 13:29:18 - got winpe File Set value
07/12/18 - 13:29:18 - updating ISD as attempting
07/12/18 - 13:29:18 - Got ZENworks WinPE Imaging task
07/12/18 - 13:29:18 - NOVELL_FIRMWARE_UEFI set by user,Consider firmware Type Flag : UEFI
07/12/18 - 13:29:18 - Firmware Type Flag : UEFI
07/12/18 - 13:29:18 - Img invoked from WinPE manual mode
07/12/18 - 13:29:18 - Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1
07/12/18 - 13:29:34 - NOVELL_FIRMWARE_UEFI set by user,Consider firmware Type Flag : UEFI
07/12/18 - 13:29:34 - Firmware Type Flag : UEFI
07/12/18 - 13:29:34 - ZISD task state and return code:4 802
07/12/18 - 13:29:34 - Failed to complete ZENWorks WinPE Imaging work


I boot into WinPE maintenance mode and run following command:

img -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=xxx.xxx.xxx.xxx


It creates the partitions then comes up with:

Error: Error reading from archive


Both devices obtain an IP addresses in WinPE and I can ping the image repo. I've added the latest NIC drivers to the .wim and updated BIOS on both.

The same bundle works on other devices without a problem.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Knowledge Partner
Knowledge Partner

Re: WinPE imaging

Hi.

I have zero experience with ZCM imaging running *on* Windows, but I'm
pretty sure that this:

> 07/12/18 - 13:29:18 - Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1

Is just wrong.

Try just

"img.exe -rp win10-base-winpe-v1.zmg [-ip=172.16.0.142 -set=1]"

Aka the path you specify is supposed to be relative to the base image
folder of the server, in your case as it's right in there, you don't
need a path at all. And the ip and set parameter in your case shouldn't
be needed, but won't hurt eiter.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: WinPE imaging

Good Catch.....
When it was reported as hardware specific...I did not look at the command-line.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
brommo
Visitor.

Re: WinPE imaging

mrosen;2492152 wrote:
Hi.

I have zero experience with ZCM imaging running *on* Windows, but I'm
pretty sure that this:

> 07/12/18 - 13:29:18 - Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1

Is just wrong.

Try just

"img.exe -rp win10-base-winpe-v1.zmg [-ip=172.16.0.142 -set=1]"

Aka the path you specify is supposed to be relative to the base image
folder of the server, in your case as it's right in there, you don't
need a path at all. And the ip and set parameter in your case shouldn't
be needed, but won't hurt eiter.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de


The command Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1 is invoked by Zenworks on the device by applying assigned image bundles. This command works, it confirms the path of the image file, otherwise it would error with "Image file path is invalid". But yes, the entire path isn't necessary, only the image name and proxy ip is needed.

Craig, I've determined that I can image these models if they have a particular SSD. So far, Sandisk will image, but Samsung and Hynix give me this error and imaging fails.

I will investigate further and see if I can perform firmware updates.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: WinPE imaging

Maybe a newer version of WinPE (1809 should be out now....)
Those drives may need a particular driver......
Could be a Firmware Update...





brommo;2492222 wrote:
The command Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1 is invoked by Zenworks on the device by applying assigned image bundles. This command works, it confirms the path of the image file, otherwise it would error with "Image file path is invalid". But yes, the entire path isn't necessary, only the image name and proxy ip is needed.

Craig, I've determined that I can image these models if they have a particular SSD. So far, Sandisk will image, but Samsung and Hynix give me this error and imaging fails.

I will investigate further and see if I can perform firmware updates.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
brommo
Visitor.

Re: WinPE imaging

CRAIGDWILSON;2492249 wrote:
Maybe a newer version of WinPE (1809 should be out now....)
Those drives may need a particular driver......
Could be a Firmware Update...


Yeah I'm using 1809, even tried going back to 1803 and 1709 with no difference. This was before I realised something...

With the 220 units of each model (440 total), I was testing with the two demo units that I originally received from Dell and HP, assuming they were identical to fleet we received. Turns out that all of the Dell 3380's have Toshiba SSDs and all of the HP 430's have Sandisk SSDs which image fine. But, the demo Dell 3380 has a Hynix SSD and the demo HP 430 has a Samsung SSD which will not image. Go figure...

I'll revisit looking for drivers for these two problem children later down the track should I find the time, but for now I'll leave it as I'm no longer in hot water.

Cheers!


For reference, I'm imaging with ZCM 17.3 using WinPE (1809) imaging. The two SSDs that were giving me problems were:

Samsung MZ-NTY2560 256GB M.2
SK Hynix SC311 256GB SATA
0 Likes
Knowledge Partner
Knowledge Partner

Re: WinPE imaging

On 07.12.2018 03:36, brommo wrote:
>
> Hello,
>
> I'm working on moving over to WinPE imaging to overcome
> driver/compatibility issues with Linux imaging. However, I'm running
> into some trouble imaging certain devices.
>
> Both fleets of HP Probook 430 G4 and Dell Latitude 3380 and experiencing
> the same problem. I'm assigning the appropriate imaging bundle and
> applying it to the devices, they boot into WinPE but fails. The
> WorkToDoDebug.txt on the device shows:
>
>
> Code:
> --------------------
> 07/12/18 - 13:29:17 - connected to server
> 07/12/18 - 13:29:17 - wstree sent
> 07/12/18 - 13:29:18 - found hardware also
> 07/12/18 - 13:29:18 - sent PSI
> 07/12/18 - 13:29:18 - reading data from server
> 07/12/18 - 13:29:18 - <ZENworks-Imaging><Type>Restore-ZENworks-winPE-Image</Type><File>C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg</File><ServerIP>172.16.0.142</ServerIP><FileSet>1</FileSet></ZENworks-Imaging>
> 07/12/18 - 13:29:18 - extracting params
> 07/12/18 - 13:29:18 - got WinPE ZMG restore image work
> 07/12/18 - 13:29:18 - C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg
> 07/12/18 - 13:29:18 - 172.16.0.142
> 07/12/18 - 13:29:18 - got winpe File Set value
> 07/12/18 - 13:29:18 - updating ISD as attempting
> 07/12/18 - 13:29:18 - Got ZENworks WinPE Imaging task
> 07/12/18 - 13:29:18 - NOVELL_FIRMWARE_UEFI set by user,Consider firmware Type Flag : UEFI
> 07/12/18 - 13:29:18 - Firmware Type Flag : UEFI
> 07/12/18 - 13:29:18 - Img invoked from WinPE manual mode
> 07/12/18 - 13:29:18 - Img.exe -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=172.16.0.142 -set=1
> 07/12/18 - 13:29:34 - NOVELL_FIRMWARE_UEFI set by user,Consider firmware Type Flag : UEFI
> 07/12/18 - 13:29:34 - Firmware Type Flag : UEFI
> 07/12/18 - 13:29:34 - ZISD task state and return code:4 802
> 07/12/18 - 13:29:34 - Failed to complete ZENWorks WinPE Imaging work
> --------------------
>
>
> I boot into WinPE maintenance mode and run following command:
>
>
> Code:
> --------------------
> img -rp "C:\Program Files (x86)\Novell\ZENworks\work\content-repo\images\win10-base-winpe-v1.zmg" -ip=xxx.xxx.xxx.xxx
> --------------------
>
>
> It creates the partitions then comes up with:
>
>
> Code:
> --------------------
> Error: Error reading from archive
> --------------------


This may be late, but I ran into this myself and diagnosed it, so this
might help whoever runs into this:

There are two possible reason for this (highly misleading I might add)
error message.

1: You are trying to restore an UEFI Image to a Hard Disk previously
initialized in MBR mode. For UEFI mode, drives *must* be initialized as GPT.

Solution: use diskpart to convert the disk to GPT mode and clean it,
then restore again.

2. The drive you're restoring the image to previously contained a main
windows partition (in the same area) which was bitlocker enabled or
encrypted. This will stop img from formatting the (new!) partition,
which triggers that error.

Solution: After receiving the error, use diskpart to select the main
windows partition, and format it using the "override" parameter. Then
try to restore the image again. It'll work.

Craig:

Can you internally suggest that IMG adds those steps (make sure the HD
is initialized in the proper mode for the image to be laid down, and
always use "override" when formatting, avoiding these issue(s)?

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: WinPE imaging

I passed the info along to the folks who do most of the imaging calls for their thoughts about possible code or doc updates.

--

Craig:

Can you internally suggest that IMG adds those steps (make sure the HD
is initialized in the proper mode for the image to be laid down, and
always use "override" when formatting, avoiding these issue(s)?

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: WinPE imaging

On 17.01.2019 13:26, CRAIGDWILSON wrote:
>
> I passed the info along to the folks who do most of the imaging calls
> for their thoughts about possible code or doc updates.


Thanks. Oh, and of course, may I suggest at least some more meaningful
error messages? This one is as far from the real cause as possible (like
failing to format a partition throwing an "unable to read from archive"
error).

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: WinPE imaging

Will Suggest...
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
brommo
Visitor.

Re: WinPE imaging

Massimo,

Thanks for your reply. I haven't yet tried your suggestion, this issue was only present on 2 devices that have since had their SSDs replaced with different brands, fixing the issue.

However, I had a similar issue where I was getting "Error writing to archive" instead of "Error reading from archive" on all of my Dell 7450 AiO units. These devices had a mixture of different brand SSDs too.

I was able to overcome this by imaging this model via a WinPE imaging script instead of applying the images via a Zenworks image bundle.

With diskpart, I had to clean the disk, create and format a partition before img.exe would be able to apply anything without errors.

I posted it here:
https://forums.novell.com/showthread.php/510787-ZCM-17-3-WinPE-Imaging-Script
0 Likes
Knowledge Partner
Knowledge Partner

Re: WinPE imaging

On 21.01.2019 03:36, brommo wrote:
>
> Massimo,
>
> Thanks for your reply. I haven't yet tried your suggestion, this issue
> was only present on 2 devices that have since had their SSDs replaced
> with different brands, fixing the issue.


Well, replacing the drive would also solve both issues, but is a bit
drastic. 😉


> I was able to overcome this by imaging this model via a WinPE imaging
> script instead of applying the images via a Zenworks image bundle.
>
> With diskpart, I had to clean the disk, create and format a partition
> before img.exe would be able to apply anything without errors.


Partition too big?

I also *think* (I have to verify it) that image explorer has issues
editing the partitions (especially the size)in winpe images. I strongly
suggest avoiding changing the partitions with image explorer at this point.

> I posted it here:
> https://forums.novell.com/showthread.php/510787-ZCM-17-3-WinPE-Imaging-Script
>
>


CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
brommo
Visitor.

Re: WinPE imaging

Very drastic, yes, but they were under warranty so they were easily replaced.

It's strange how it's only 1 model that experiences this problem.
The same image applies to other devices with no issue.
The image was taken via WinPE and is a 100GB partition unmodified.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.