Unsolved
2 Posts
0
1121
May 26th, 2023 09:00
Dell Dynamic Image Assist - Initial PE drivers and automating Command Update
Good afternoon,
I am reaching the final stretch with my DIA golden image. I have two questions specifically:
1. When reading on how to include the WinPE CAB drivers from Dell, there are many mentions to "include these drivers when prompted by Image Assist." However, I am not prompted for this when creating the initial .wim via DIA. We just want the basic network drivers initially to be able to bootload Command Update. We use various Dell families and machines, and some do not have basic network drivers installed. Is there a specific folder on the image that will automatically deploy the correct .cab file when the new machine first boots up? We do not use MDT or SCCM, so this process would need to be handled via DIA, or we will need to find another way.
2. On the topic of Command Update. It seems that the 'bulk' Dell driver packs have been retired, and I am assuming it is due to people using Command Update instead. Are there any current best practices or guidelines to be followed when updating the computer in this manner? I was going to have DCU run silently in the background to provide initial driver installation. I am curious what some different approaches to this will be.
We are building and maintaining the image in Hyper-V, and outside of the Dell Driver issue, everything has been smooth so far. Win10Entx64, minimal GPO abilities (very minimal), and no real network share access. This seems to be a good solution for our particular circumstances.
Cheers.
DELL-Tyler M
Moderator
•
342 Posts
0
May 30th, 2023 09:00
@ComputerNamesAreDead
Image Assist uses the Family Driver packs during the image restore process. Download the driver pack from www.dell.com/familypacks and add the .zip (do not extract) to the "Dell_Driver_Packs_Local" folder on the Image Assist USB drive. When you restore the image the drivers will be added. Here is an example of the DIA USB drive layout.
Thanks,
Tyler www.dell.com/diakb
ComputerNamesAreDead
2 Posts
0
May 30th, 2023 09:00
Thanks for the response, Tyler.
Since we use more than a dozen (and growing/changing) Dell types and models, downloading individual family packs monthly is not really an option any more. I'm honestly not sure how people that used the bulk download family packs are dealing with their removal.
I think we'll stick with the PE cab drivers for the image, and then use Command | Update for the rest.
Cheers.
parterblockerson
1 Message
0
July 3rd, 2023 02:00
When it comes to including the WinPE CAB drivers from Dell in your DIA golden image, if you're not being prompted for them during the initial .wim creation, you can manually add the necessary drivers to the image. You can create a folder on the image where you place the appropriate .cab file, and the system should automatically deploy the drivers when the new machine boots up. Make sure to place the .cab file in the correct location within the image's folder structure.
Regarding Command Update, it's true that the bulk Dell driver packs have been retired, and Command Update is now commonly used for driver updates. Running DCU silently in the background to provide initial driver installation is a valid approach. It's always a good idea to ensure you have the latest version of Command Update installed to take advantage of any improvements or bug fixes. Additionally, periodically checking for driver updates on best Dell's website and using Command Update to install them can help keep your systems up to date.
wa7154733
2 Posts
0
July 3rd, 2023 09:00
Hello there!
Regarding including WinPE CAB drivers from Dell, if you're not prompted for it during the initial creation of the .wim file via Dell ImageAssist (DIA), there is an alternative way to handle this. You can create a specific folder within your image, usually under the "Out-of-Box Drivers" directory. Place the necessary .cab file in that folder, and upon the first boot of the new machine, Windows Setup will automatically detect and install the appropriate network drivers from the result .cab file. This approach allows you to ensure the basic network drivers are available for Command Update to function correctly without relying on MDT or SCCM.
As you mentioned, the bulk Dell driver packs have been retired, and Command Update has become the preferred method for driver updates. Running Command Update silently in the background to provide initial driver installation is indeed a viable approach. It's recommended to regularly check for updates from Dell's official website or Command Update itself to ensure you have the latest versions of drivers and firmware for your Dell machines. This helps maintain compatibility, performance, and security.