Your email address will not be published. Systweak Support. Skip to content. October 15, October 17, Systweak Support. Download and install Advanced Driver Updater. Related Posts Driver Guide.
November 22, Systweak Support. Driver Guide. November 21, November 20, Systweak Support. Leave a Reply Cancel reply Your email address will not be published. Note: While this post deals with driver packages in ConfigMgr, you can apply the same strategy for application packages that have many small files, or simply really large applications that could benefit from a bit of compression.
For example, I've worked with organizations that create wim images for their larger applications, and instead of extracting the wim prior to running the application setup, they simply mount the wim image, and run the installer from that one. It's a fantastic tool, I highly recommend using it. By switching your ConfigMgr driver packages to archived versions, you don't only make them much smaller, but also increases overall download speed and peer-to-peer efficiency.
Usually between times faster depending on content source. But 7-zip format will reduce package size a bit more. The driver step alone took 7 minutes, and this was on a mbit network with a remote DP. Deploying five of them at the same time, ended up with a total of 10 minutes for the drivers step peering saved me some WAN bandwidth.
Bottom line, downloading, or peering large packages with many small files is just not very efficient. But it can be much better…. Note: When zipping driver packages you do lose the single instance store benefits of the ConfigMgr Content Library for these packages, but in my testing the benefits of reducing package size by zipping driver packages totally outweighs the single instance store.
For the zipped versions, even on the lowest compression rate, the resulting size was 22 GB. When adding data deduplication to the distribution point, another 8 GB was saved, and disk usage was down to 14 GB.
Many organizations have already switched to use legacy packages for the drivers, and have DISM just inject them during the task sequence. But why not take it one step further, and simply zip the content in your driver packages.
If you are optimizing for BranchCache data deduplication efficiency among many packages, use the Compress-Archive cmdlet with compression level set to Fastest , and for 7-Zip, use the zip format with the deflate algorithm.
BranchCache really likes these algorithms, and is quite good in figuring out deltas for these formats too. If you are optimizing for fastest possible deployments, and don't pre-cache lot of data, 7-zip on ultra compression will create quite small packages. Note: While it may be tempting to use super-high compression algorithms, doing so will lower data deduplication efficiency, and delta updates of packages BranchCache uses data deduplication. That being said, higher compression algorithms will usually reduce the size with another 30 percent or so, so for direct download from DP having data deduplication enabled, or from Peer Cache, which can't do data deduplication, you might want to use it.
After archiving my 1 GB driver package for the Dell Latitude model, the resulting drivers. After creating the drivers. The final step is to configure your task sequence to use the Zip-version of your driver package. Basically it will just download the package first, and then extract it using PowerShell. The command line I used to extract the content of the Zip-version of the driver package is the following:.
The final step is to instruct the task sequence to inject the drivers that were extracted into the driver store using DISM. For this you add another Run Command Line action, with the following command:. Don't forget to add a condition to the command so it only runs if the folder exist. You don't want the task sequence to error just because you deployed a machine where you didn't need to use any drivers or forgot to add them.
If you want to learn more on how Data Deduplication and BranchCache works together I recommend reading the below post from Mike Terrill. COM — Enterprise Mobility. My question is what do I set as my root folder to zip up? Do I start where the list of folders like, audio, chipset, graphics and so forth are at, or do I start at the top of the zip, and zip everything using 7zip? I tried to use Driver automation tool, but even with it set to download only, I watched it download all of the files, extract them, and then delete them right back out … Read more ».
Within win10, we have: x64 folder and x86 folder , do I need to modify this? That script was designed for packages created by the Driver Automation Tool, but will work with custom driver packages too as long as you configure the settings right. It will tell you which drivers that are not ok. As far as how ConfigMgr deals with the suppression of errors I don't know. Help Tips. Standard DCH.
Production Branch New Feature Branch. Only supported when using Internet Explorer.
0コメント