![]() ![]() In my example, I have the installer files in the C:\Temp directory, but you can adjust the command to point to any location you would like. New-WindowsImage -ImagePath C:\Temp\.wim -CapturePath c:\Temp\InstallFiles -Name Name = Whatever name you’d like to give the image. ![]() CapturePath = Location of the directory where the install files currently live.ImagePath = Location where you want the.Using the New-WindowsImage cmdlet (run elevated), just specify the following: Use the following code to create the compressed. wim file couldn’t be easier when using PowerShell. We’re talking going from 10–15 minutes to a less than 2-minute download!Ĭreating the. wim file because that’ll allow ConfigMgr to only hash and download one large file, dramatically speeding up this process. The solution is to compress the entire installation package into a. In our case, it took 10-15 minutes just to download this piece of software. No matter how quick your network connection is, ConfigMgr will iterate through and download these thousands of files separately. The package is fairly large (not Autodesk large) at 1.5 GB, but it has thousands of small files included in the installation directories. The past couple days I’ve been trying to create an application deployment for a software called InEight Estimate. Now I’ve finally found a scenario that can benefit from this process! I’ve kept this in the back of my mind for a while now until I needed to take advantage of this method. Also, the MSEndpointMgr guys currently do a similar thing with their Driver Automation Tool for large driver packages. ![]() Several months ago, I ran across some Reddit posts where other sysadmins were talking about wrapping up their HUGE Autodesk app installs into. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |