MDT 2013 Zenworks imaging issue

Hello, we are trying to set up pxe boot options for our MDT in Zenworks and I'm having troubles figuring out how we get the deployment wizard to popup instead of just the standard winpe environment. I expected to see the MDT Deployment Wizard popup but what I get is a command prompt loading wpeinit then zenworktodo.exe where it prompts for imaging type: WIM or GHOST. I've tried selecting all the options including query for work and it says there is no third Party imaging work assigned.

So far I have gone in and created a preboot bundle using my 64bit Litetouch.wim file that MDT supplies you with your deployment, it's been fully updated and the current version. I've uploaded the 64 bit winpe and imagex files into the 3rd party imaging options under preboot services (Configuration, Device Management).

We can pxe boot and I get the Zenworks preboot deployment Services Menu to come up in which I select WinPE Maintenance Mode. It then boots to the winpe.wim file but it's the one that comes with the ADK and MDT doesn't get offered in any way. Maybe I'm misunderstanding how you access a MDT created image but that is where I'm at.. Very new to this but am stubborn enough to eventually figure it out just hoping someone can give me some insight on all this. I'm still at a loss somewhat on how it's going to find all the files it needs on my machine. I have given EVERYONE read/write access on my deployment share though so there should be the info included in my custom wim somewhere that will point my machines in the right direction.

Thanks for any help with this. Really wanting to figure this out cause we are so close! :D

Tags:

  • I think part of the issue is the fact you are always booting to the Imaging Menu..........
    Normally that is invoked Manually during the imaging process.
    That is preventing the rules from taking place....

    You can create MDT items on the PXE menu similar to this....
    option = execute ; "MDT x64 Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/c3c8d9a2605178d4b42b2ae088c373de/x64/winpe.cfg
    option = execute ; "MDT x86 Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/fa70fdf71d24961b734ac48e37f0c88b/x86/winpe.cfg

    The exact paths would be unique and created after you created the MDT Bundles.
    (Note: I presume MDT bundles exist on 11.4.x, but I did not look since it is End of Life this month.....)



    Note2: If the Menu is Automatically coming up every time....I would ask your admin why...that would seem to make imaging very difficult and sending a tech around to every device to manually re-image.
    Normally School Admins would set Classroom 1 to re-image automatically at 5pm, Room#2 at 6pm, etc....so that all classrooms are re-imaged for the next day while they are home enjoying dinner or sleeping ;)
  • I think part of the issue is the fact you are always booting to the Imaging Menu..........
    Normally that is invoked Manually during the imaging process.
    That is preventing the rules from taking place....

    You can create MDT items on the PXE menu similar to this....
    option = execute ; "MDT x64 Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/c3c8d9a2605178d4b42b2ae088c373de/x64/winpe.cfg
    option = execute ; "MDT x86 Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/fa70fdf71d24961b734ac48e37f0c88b/x86/winpe.cfg

    The exact paths would be unique and created after you created the MDT Bundles.
    (Note: I presume MDT bundles exist on 11.4.x, but I did not look since it is End of Life this month.....)



    Note2: If the Menu is Automatically coming up every time....I would ask your admin why...that would seem to make imaging very difficult and sending a tech around to every device to manually re-image.
    Normally School Admins would set Classroom 1 to re-image automatically at 5pm, Room#2 at 6pm, etc....so that all classrooms are re-imaged for the next day while they are home enjoying dinner or sleeping ;)
  • I think part of the issue is the fact you are always booting to the Imaging Menu..........
    Normally that is invoked Manually during the imaging process.
    That is preventing the rules from taking place....

    You can create MDT items on the PXE menu similar to this....
    option = execute ; "MDT x64 Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/c3c8d9a2605178d4b42b2ae088c373de/x64/winpe.cfg
    option = execute ; "MDT x86 Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/fa70fdf71d24961b734ac48e37f0c88b/x86/winpe.cfg

    The exact paths would be unique and created after you created the MDT Bundles.
    (Note: I presume MDT bundles exist on 11.4.x, but I did not look since it is End of Life this month.....)



    Note2: If the Menu is Automatically coming up every time....I would ask your admin why...that would seem to make imaging very difficult and sending a tech around to every device to manually re-image.
    Normally School Admins would set Classroom 1 to re-image automatically at 5pm, Room#2 at 6pm, etc....so that all classrooms are re-imaged for the next day while they are home enjoying dinner or sleeping ;)
  • Well so far all I've been playing with is vm's and a couple laptops. I did send it to a desktop in a lab to test but I want to get it working in my testing environment first before I go imaging existing devices. I am treating them like new machines as they do not have a OS installed so that is why I'm booting to the imaging menu. Now that students are out for summer I will be testing more physical machines to see if the rules are applying. I get what you mean by not having to go to every machine but I have some software installs that will definitely need some interaction as well as renaming each computer so we'll have to touch them anyway. But I have MDT setup to only prompt for the computer name and the bundle choice.. I have staff laptop/student, staff/student desktop, teacher laptop etc for my different configurations as well as windows 10/7 options.

    I'm also getting my network admin to give me rights to the zen server so I'll be able to go to these folders and make those changes as you suggest. I'll look into those pxe menu options. That would be awesome. What file do you alter to add that information? Thanks again for all your help. We are moving forward at least...
  • So it looks like one of my main issues is that Zen is just not assigning imaging bundles. Whenever I assign the MDT Deployment bundle nothing happens. I honestly don't know how to initiate it though so I may be doing something wrong but I've refreshed the device, it see's other bundles that are assigned but not the imaging bundle. I reboot, let it log back in.. nothing. I boot to pixe and choose Zenworks imaging, it erros out with error 100: Assigned task is not of Zenworks imaging. I can choose WINPE Maintenance mode but that is just going to launch WINPE and boot my MDT bypassing the actual assigned bundle task and cheating if you will. My rules don't seem to apply either even with the simplest options. Ip starts with 10, which covers all devices, and Hard drive is > 1gb. Automatic imaging or "Zenworks Imaging" just simply is not working but I have no clue where to start to fix that issue. I've done every task you've suggested through many threads and nothing seems to work unless I choose WINPE Maintenance mode.... and that only works now cause we copied the tftp\mdt contents to tftp\boot overwriting the base winpe stuff. Otherwise I'd still be at square one.
  • Today I realized that the reason the imaging menu comes up all the time is cause it was set to always show in zcc. Now I can pxe boot and just let it go and it tries to contact the server. Sadly on my vm's it reaches out to the server and even with no OS and with rules in place that match the IP and the mac address it still won't apply the bundle. I used your info above as a parameter in my rules as well. Not sure if that is where I can apply that but I tried and no go. I did change to my exact location too: option = execute ; "MDT Deployment" ; "MDT Deployment" ; pxelinux.0 ; mdt/b9e6d0144dca60ae62459022657a8809/x64/boot/winpe.cfg
    We have a boot folder before the winpe is the only difference. Still no go though.. I was able to take an image though for the first time so I may just look at using zenworks imaging. I created a base bundle with just the os but now to figure out how to add all my apps along side it or create bundles like I've done in MDT.
  • OK, let me try to help you out here by explaining the steps needed for MDT imaging:

    First, you need to enable the 3rd Party Imaging feature. This is done in ZCC under Configuration > Device Management > Preboot Services. Here you upload the x86 and x64 versions of imagex.exe and the base WinPE (winpe.wim) that comes with the Windows ADK (NOT your LiteTouch WinPE from MDT!). Imagex.exe can be found under 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\<architecture>\DISM' whereas winpe.wim is in 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\<architecture>\en-us'. You need to do the uploading process from a PC that runs Windows and has the ADK installed AND you might need to launch your browser with elevated rights. This is because, upon uploading, the ZCC helper temporarily mounts the winpe.wim file (hence you need elevated admin rights) and injects some ZENworks tools (img.exe, isdtool.exe etc.) which automatically launch when you boot this WinPE. And it's this modified WinPE that's booted when you select the WinPE Maintenance Mode in the PXE menu. Don't forget to apply the changes on the Preboot page!

    Second, you need to create an MDT deployment Preboot bundle in ZCC. When you do this you'll get asked for the WIM image to include. HERE you select your MDT WinPE file e.g. LiteTouchPE_x64.wim. When this bundle is created and published you can go ahead and make it available through a hardware rule (like every other Preboot bundle) or through a custom PXE menu entry like this:
    option = "execute;Start MDT Deployment;Launch WADK WinPE environment;mdt/c4430483d52ed4fc59c0e6a54338cec2/x64/boot/bootmgfw.efi;efi/x86_64/winpe.conf"

    Make sure the GUID (bold red text) represents the folder name on the Primary Server under '%ZENWORKS_HOME%\srv\tftp\mdt' (Windows) or '/srv/tftp/mdt' (Linux) and NOT the GUID you see on the Preboot bundle in ZCC! Additionally, the above example is for native UEFI boot mode (recommended for Win 10), not Legacy/CSM boot, so use the pxemenu.txt under the efi subfolder! With this modification, you can launch your MDT deployment easily through the PXE menu.

    One last thing: on some of our machines, when using PXE boot, the WinPE would just boot into a blank command prompt with the MDT Deployment Wizard not starting. On the other side, when we used the same source WinPE wim file coming from MDT and made a bootable USB thumb drive from it, the MDT Wizard correctly shows up and the deployment succeeds. We found out that upon creating the MDT deployment bundle in ZCC, ZENworks injects ISDTool.exe into the MDT LiteTouchPE wim file and modifies the startnet.cmd (which is automatically started by WinPE upon booting) to start the command line 'ISDTool.exe MDTInitBundleSettings' BEFORE launching wpeinit (which starts the MDT Deployment Wizard). Our guess is that the ISDTool command line runs into an error or infinite timeout on some hardware configurations and hence the MDT Wizard won't show up. We worked around this issue by simply replacing the winpe.wim file in the filesystem of the Primary Server (under 'mdt/<GUID>/x64/boot') with the one from the MDT ('DeploymentShare/Boot'). We have a SR open for this to find out if it's a bug and what functionality we might lose when those ZENworks binaries and modifications are missing from the MDT WinPE.