6 Replies Latest reply on Mar 18, 2008 6:23 AM by Fnurgg

    Deploying a large number of files



      I'm trying to deploy a number of MSI packages with a huge number of files (often 10.000+)



      It takes ages to download and install. I read on the forum here that the common workaround is run from source but i'm reluctant to use it since 3/4 of our installations are over slow link. So far i've been using winrar and creating exe files that auto-extract and run a batch file but when the package fails for some reason (another installation in progress for example) i get no feedback at all.



      So i'm wondering how the other landeskers around here handle the problem.






      Thans for your replies






        • 1. Re: Deploying a large number of files


          You are using the correct method to do this. You can add some code in your batch file to better report the errors... see this link click here



          • 2. Re: Deploying a large number of files
            zman Master


            When you say 10,000+ files is this per package 1 msi with 10,000+ files? You could try this:


            1. Compress the files and msi in either a zip or self extracting exe I would use self extracting exe.

            2. Use target multicasting to prestage the large compressed files.

            3. Run the self extracting exe to expand the files out to a temp folder.

            4. Run MSI

            5. Cleanup temp


            You could also packup the files in a cab file with the MSI - repackage.  I personally use ZipGenius



            Compressing the files up will be better and easier to manage, plus with TMC you can avoid killing the slow links. 



            • 3. Re: Deploying a large number of files

              Zman's suggestion is the way to go. The only thing I would add is to not use targeted multicast. You can achieve the same bandwidth friendly delivery, but do it more reliably than targeted multicast.


              To accomplish this, the most important setting in the delivery in the delivery method is this:

              Limit remote downloads to one per subnet.


              If this option is checked, only one machine will cross a WAN link to get the package. Then, once it is downloaded, the rest of the machines on the network will download it locally through peer download. You can combine this with the bandwidth friendly settings to throttle that one download.


              If you also use a policy, it will stagger the deployment even more, so you don't have all of the remote subnets all downloading the file at the same time.

              1 of 1 people found this helpful
              • 4. Re: Deploying a large number of files

                I use the following method to deploy a large number of files.


                - Use 7zip to compress your folder

                In this example compress the folder C:\dotnet11_temp to MSDotNETFramework11.zip


                - Create a batch file looking like this


                @ECHO ON

                sdclient.exe /msg="Extracting archive"

                7za x MSDotNETFramework11.zip -y

                IF NOT "%ERRORLEVEL%"=="0" EXIT /B %ERRORLEVEL%


                sdclient.exe /msg="Installing"

                cd dotnet11_temp

                msiexec /i netfx.msi /qn REBOOT=ReallySuppress

                IF NOT "%ERRORLEVEL%"=="0" EXIT /B %ERRORLEVEL%



                sdclient.exe /msg="Deleting extracted archive"

                del dotnet11_temp /q

                sdclient.exe /msg="Installation finished"


                - Define a batch distribution package and point to your batch file


                - Add the zip archive and the 7zip command line executable to the addional files section


                - Deploy your package


                • 5. Re: Deploying a large number of files
                  zman Master





                  Very good point! I guess I'm showing my age  I'm going to try this the next large deployment we do.






                  • 6. Re: Deploying a large number of files

                    Thanks for your replies! They've been really helpfull

                    Back to my testlab now. Time to repackage my stuff