The first two may well work, the /? string shows the above as the required command line, I have not tried the ones used with previous versions but they may well work. Then the uninstall string is as follows: /uninstall /quiet /norestart It is slightly different for 2013 but not much, here is the install command line: /install /quiet /norestart X86: /q:a /c:"VCREDI~1.EXE /q:a /c:""msiexec /x vcredist.msi /qn"" "įor 2008 you will simply need /q and for 2010 /q /norestart. X86: /q:a /c:"VCREDI~1.EXE /q:a /c:""msiexec /i vcredist.msi /qn"" "įor the uninstall string you will then need this: 圆4: /q:a /c:"VCREDI~2.EXE /q:a /c:""msiexec /x vcredist.msi /qn"" " If you are deploying 2005 edition of the redistributables then you will need the following as the installation string: 圆4: /q:a /c:"VCREDI~2.EXE /q:a /c:""msiexec /i vcredist.msi /qn"" " With this however comes the need to specify an uninstall string and a detection method to help the application model do all the cool things it is now known for.įor convenience as well, if you head over to my downloads page, you will see a link that contains a package with both the x86, 圆4, RTM and SP1 releases of the redistributables for the following versions:
With the adoption of the application model in ConfigMgr, I now setup my redistributables as applications so we can easily create dependencies if they are required.
In this post I will share some information to make the deployment of them much simpler. They are not difficult to setup but can create headaches due to the number of them. Of all the software I have had to deploy at a customers site, the most common is probably the Visual C++ Redistributables.
0 kommentar(er)
