Now when you image your computer, it will only have the bare driver installed until it runs the Dell Command Update, where it will check for the latest Dell supported drivers and apply them to your system.
For New Windows 10 Machines, we've switched to this model. No more downloading Dell Driver Packs and applying drivers. This is great for testing new Models, instead of taking time to import the drivers, just image it and Dell Command Update will do it's part to get you far enough along. There are still quite a few bugs in Dell Command Update 2. I am trying to do this in WinPe. Thing is, I cannot get the xml working so it will pull only from a share i have onsite, i never want it to go to FTP site.
Awesome stuff! Thank you for putting this blog together. This worked for me on my first attempt with a Dell Optiplex mff using version 2. After a few month do you still use this? I'm concerned about all the "crap" that come with the standard drivers package. Do you have your own repo or take the drivers directly from dell each time? Does it take much longer than using driver package or family cab from Dell? Also do you leave the dell command update installed after OSD, and use it during the life cycle of the computer?
I'm thinking about just launching the dcu-clie. Still using this, it's been working well. We actually download directly from dell, we have a huge internet pipe, and only image computers a day, so it's not an issue. It does take a little while to run, and probably longer than a normal apply driver step. The "bloat" has been a concern, I run a step later to uninstall the intel wireless proset software if it got installed.
I do leave it installed after OSD, our service desk will run it from time to time if they think an issue my be driver related. I do lock it down so it can only install certain drivers though. I think the idea of running the command line from a package source is a good idea, I might give that a try in the future. I want to do the BIOS but I'm concerned if MDT will resume the task sequence, because task sequences tend to break when an application automatically reboots the computer.
For Dell, HP, and Lenovo, there is a no reboot option you use in the command line. In the TS, you trigger the reboot after upgrade by using the built in reboot step. We're still imaging with Windows 7 where I currently work, but going to Windows 10 soon.
However, I've got all steps right, but on the "Run Dell Command Update" step, it will run, but after a while it gives the error 0x I can close that and it goes in to Windows once I put my credentials in, but then I am prompted to do a restart.
I restart and unit comes back up. What am I missing to get this error message? What Model are you testing on? How long is "awhile", perhaps it's timing out connecting to the internet? I'd start troubleshooting by importing a filter with a very few driver options, like just chipset and video, or something, and try again to see if that goes.
So doing some troubleshooting it was giving error on the docking station firmware. The only thing we will need are bios and drivers, and nothing else. I made the changes, but still getting the same error message. Found out it is failing on installing the wifi driver and deleting the Intel Graphics shortcut.
Yet everything installs. I haven't tried on a Latitude E, but will test Windows 10 for that one. Where should I be placing the Dell Command Update tasks? It could be having the issue that it's not installing all this in the resident OS, that I have selected. Also, I noticed from the activity.
The other 2 error codes are 0x2 and 0x3. My only option I can see in the Task Sequence would be to check "continue on error", but that may stop any drivers from giving an error before it completes everything from Dell Command. Also, we are not the Dell Command Update software to stay installed after it runs. What is the command to uninstall it after all drivers are installed? Are you having issues with the E on Windows 10? I have not tested Windows 7 on that.
I've got my step set to continue on error. Sorry, no better advice for you there. Consider opening a support Case with Dell, especially about the docking station firmware issue. They are good about getting back to you on these things. If not, hit up Warren on Twitter. Thank you for the tip on checking "continue on error". That corrected the issue and worked flawlessly. I was even able to uninstall the Dell Command tool too.
I also verified that everything installed correctly. I've been fighting for a way to get the drivers updated for the team and this is by far the best that I've seen. I also moved the placement of the Dell Command in my Task Sequence.
Thank you for the guide you have created on here. I've followed this guide at every step. You can see if you open up Dell Command Update in Windows it show's it has never check or even updated.
What ports does it use when reaching out to the Dell Support site? It could be that our Security Team is blocking it from communicating out to the site. However, I can run it and it shows that it had driver updates. What am I missing in the TS. This is during an install for Windows However, if you set a place for the Logs during OSD, you can check there.
This post is great and thank you so much Learn how to upgrade to Windows 11 Windows 11 Upgrade Guide. Already have an HP account? Select from the products you own. To contact support, select from your products. Examples of where to find your product name. Or select your product from popular printers. Need help finding a serial number?
Try a keyboard command. Locate your product's information label. Watch a video. Find your serial number by locating the product label. The product information label contains your serial number and product number. You can find it either on the back of your laptop, inside the battery compartment or under the cover on the back of the laptop.
Sample product label. Find your serial number using a keyboard command. If your laptop is currently functioning you can find the serial number by using a simple keyboard command. Artboard 2. Depending on your desktop model you can find it on the side, top, front or back of the computer.
For All-in-One PCs you will find it on the back. If your computer is currently functioning you can find the serial number by using a simple keyboard command. Need help? Locate the product label. For almost all HP products, the product information label can be found from one of the following locations : A label attached to the product usually on the underside Laser etching on the surface of the product Inside the battery compartment A purchase invoice or receipt Product packaging or shipping box Documentation that came with the product.
Examples of where to find your product information label. Select a location.
0コメント