Hyper V Help

Hey Brian,

First you will need to make the usb key, and since Hyper-V does not support that, simply run DIA on a physical system and go to advanced tools to make the usb "stand alone". If the system is on a domain, you will need to edit the config file to skip the validation by makin it true like this: "SkipApplicationLaunchValidations" value="true".  

Now when in Hyper-V and the image has been captured, there is a message that comes up to allow you to move the image. You will need to have networking turned on in the VM and select "Map network drive" to move the image. If you reboot the VM, the image is in the root of C:. You can map a drive in the OS and move it now as well. If you have any further issues, please reach out to our support desk, located in the ImageAssist website. .Thanks

Hey, thank you so much for your help that worked 100%. 

Im not trying to figure out when you restore the WIM files, where do you place the drivers pack? Because I remember the old one you were able to select it this one im not too sure where you place it? 

Thanks again for all your help.  

Happy to assist. So when you create the usb restore stick, there will be two partitions. First is a F32 boot partition and the second is a NTFS data partition. On the Data partition, there will be a folder "Dell_Driver_Packs_Local", that is where the driver packs go. Download them from the DIA website but do not extract or rename them. Also there is a Image folder to place your image in. You can browse to the image as well if needed. 

Thanks...TK

Thank you so much for your help once again. 

I was wondering why is it that when I go to Driver Path and I click browse and I look for the drivers it doesn't show me anything but I have CAB and ZIP files in there of drivers but it doesn't show me them? Is there anything I'm doing wrong?

Thank you so much.

The new version of ImageAssist works differently that the previous releases with how driver packs are selected / detected. Previously, you would browse to the folder where the driver packs were located, select the folder and the GUI would display a list of driver packs to select from. With the new version, if no packs are detected it will display a red message stating "No valid driver pack detected". If a valid pack is detected in the selected directory (which by default is the one Tony mentioned) then the red message will go away an this means it sees a valid pack to use.

Makes plenty of sense. 

However, im trying to figure out what is it with the 9310 2-in-1. It's not taking the drivers from my Mapped drive or my bootable USB key.. but it accepts my Latitude 5410. Any guidance on that part? 

Thanks again for your help on this. 

@Brian404x - thanks for reaching out directly. So others in the forums are aware, the Command Deploy single platform CAB was being used, which ImageAssist failed to recognize. The Command Deploy packs are not tested / qualified to work with ImageAssist. The Family Driver Packs are built & qualifed with ImageAssist. The Family Packs also work for our other in factory DDI options (SCCM / MDT / Connected Config / KACE). As packs are tested and qualified for new systems in our factory, they are eventually promoted to be downloaded either using the Family Pack Downloader utility, or using the Family Packs webpage. The pack in question for the 9310 2-in1 was promtoted, but the HTML content for the Family Packs page is pending an update. In the iterrum, it's possible to find that pack using the Family Pack Downloader utility.

Thanks, TM