Popular Tags

  • WinPE Imaging Scripts Looping - zenworktodo

    I'm back after my last post, which is found below. We're working on an older version of ZCM Server version 20.2.0.0 and zenworktodo.exe was not kicking off automatically. I finally got some time to come back to it and found modifying the unattend.xml…

  • Where does ZCM 2020 server stores the winpe.wim on disk ?

    Hi, we used already a customized winpe boot image for our PXE imaging with zenworks. Now, as we have a new kind of HP docking stations we need a new intel lan driver integrated into that existing winpe boot image. My idea: As i unfortunately have…

  • WinPE Imaging zenworkstodo not automatically starting

    I am very new to ZenWorks and inherited it when I started at this job. Currently they had no way to automate imaging and I'm finally getting around to the task. I have WinPE setup in Preboot Services I'm able to create a Zenworks Image Preboot bundle…

  • WinPe Image capture has no EFI partition

    Hi everyone, i capture an image from UEFI notebook which i imaged with ZCM. There 3 volumes / partitions in harddisk. After i capture an Image to server i image another notebook with that image. When imaging finished notebooks can not booted…

  • IMG.EXE not found in ZENworks 11.4.3 WinPE preboot.

    Hi! Why does the img.exe command not exist in WinPE imported into ZENworks 11.4.3? The image capture and restore tool runs, but the IMG.EXE file does not appear to have been injected into WINPE.WIM. I couldn't identify what I could have done differently…

  • Get BIOS information in WinPE script

    Hi, I'm trying to configure a general script that I can use with all my devices by filtering my zmg files based on BIOS Product name. I'm using a script model that I found on Microfocus Community but nothing is associated with $HARWARE_IMAGE when…

  • WinPE Imaging and TPM

    Hello everyone, I thought I'd write this up and share an issue I've been having with the switch to WinPE based Zenworks imaging (ZCM 17.3) from Linux based imaging. Since day one (approx. 18 months ago), I was struggling with imaging particular models…

  • How do you guys automate boot sequence on UEFI systems?

    Hey guys, I'm trying to figure out what I want to do with my "boot order" on UEFI systems. Compared to legacy systems, my boot order is getting messed up after imaging. My new systems come in with "UEFI PXE" disabled and we need to set other configs as…

  • WinPE upload failed with ZCM2017Sp3

    Hello, I tried to upload winpe.wim into ZCM 2017Sp3 and I get the error "Unable to mount the selected wim file" I have installed the newest ADK for Win10 1803 on my PC. I tried it on another PC with Win10 also the same error. The error appears on both…

  • ZEN 2017 Update 1 Linux to WinPE Imaging

    We are using Linux to image our computers using a Preboot bundle with an imaging script. Since Linix does not support newer models especially in UEFI mode, it looks like WinPE may be the way to go. We are on 2017 Update 1. There are three parts to our…

  • Modify startnet.cmd? ZCM 2017 Update 2

    We are using ZCM 2017 update 2 to let us use WinPE via USB to restore images on some of our newer devices that aren't loading using the PXE/Linux imaging system (like the latest HP x360 G1, or the HP Stream G4). I have worked with Novell Support (who…

  • WinPE Windows 7

    Hi I have a question regarding imaging with WinPE and Windows 7. We have an image (WIM) of a Windows 7 setup with two partitions (the boot partition system partition). The image was taken from a computer with a 320GB hard drive. Now when we restore the…

  • PXE Menu With WINPE

    I'm depolying windows 7 (600 of 2000) in my company I want to add to the pxe menu a row that will excute a winpe image automaticly I look on the pxemenu.txt file and see that it's pointing the winpe.cfg file Can a make a script that take winpe image and…

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.