Home

Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: WinPE imaging

  1. #1

    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:

    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
    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.

  2. #2
    Join Date
    Feb 2008
    Location
    Raleigh, NC
    Posts
    6,658

    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....


    Quote Originally Posted by brommo View Post
    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
    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.
    --
    Any Opinions, Thoughts, Solutions, or Blog Entries are my own and may or may not be shared by Micro Focus or any Sane Person
    Please Use at your Own Risk.

    Blog - https://forums.novell.com/blog.php/5830-CRAIGDWILSON

    https://ideas.microfocus.com/mfi/novell-zcm

    Want to Turbo charge your apps and put an end to compatability issues?
    https://www.microfocus.com/products/...top-containers

  3. #3
    Join Date
    Sep 2007
    Location
    Cologne, Germany
    Posts
    5,682

    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

  4. #4
    Join Date
    Feb 2008
    Location
    Raleigh, NC
    Posts
    6,658

    Re: WinPE imaging

    Good Catch.....
    When it was reported as hardware specific...I did not look at the command-line.
    --
    Any Opinions, Thoughts, Solutions, or Blog Entries are my own and may or may not be shared by Micro Focus or any Sane Person
    Please Use at your Own Risk.

    Blog - https://forums.novell.com/blog.php/5830-CRAIGDWILSON

    https://ideas.microfocus.com/mfi/novell-zcm

    Want to Turbo charge your apps and put an end to compatability issues?
    https://www.microfocus.com/products/...top-containers

  5. #5

    Re: WinPE imaging

    Quote Originally Posted by mrosen View Post
    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.

  6. #6
    Join Date
    Feb 2008
    Location
    Raleigh, NC
    Posts
    6,658

    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...





    Quote Originally Posted by brommo View Post
    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.
    --
    Any Opinions, Thoughts, Solutions, or Blog Entries are my own and may or may not be shared by Micro Focus or any Sane Person
    Please Use at your Own Risk.

    Blog - https://forums.novell.com/blog.php/5830-CRAIGDWILSON

    https://ideas.microfocus.com/mfi/novell-zcm

    Want to Turbo charge your apps and put an end to compatability issues?
    https://www.microfocus.com/products/...top-containers

  7. #7

    Re: WinPE imaging

    Quote Originally Posted by CRAIGDWILSON View Post
    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

  8. #8
    Join Date
    Sep 2007
    Location
    Cologne, Germany
    Posts
    5,682

    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

  9. #9
    Join Date
    Feb 2008
    Location
    Raleigh, NC
    Posts
    6,658

    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[/QUOTE]
    --
    Any Opinions, Thoughts, Solutions, or Blog Entries are my own and may or may not be shared by Micro Focus or any Sane Person
    Please Use at your Own Risk.

    Blog - https://forums.novell.com/blog.php/5830-CRAIGDWILSON

    https://ideas.microfocus.com/mfi/novell-zcm

    Want to Turbo charge your apps and put an end to compatability issues?
    https://www.microfocus.com/products/...top-containers

  10. #10
    Join Date
    Sep 2007
    Location
    Cologne, Germany
    Posts
    5,682

    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

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •