15 Replies Latest reply on Feb 26, 2019 3:39 PM by Matthew Brahm

    Deploying SolidWorks with SCCM 2012 SP1

    Support Admin

      I have been trolling the forums and there appears to be a lot of confusion on how to install SolidWorks with SCCM 2012.  SolidWorks has not provided much documentation on how to do this and I struggled through it for a while so I thought I would share some of my notes.  My notes are based on SolidWorks 2014 x64 SP04, Windows 7 x64 and SCCM 2012 SP1.


      Steps to Deploy

      1. Download install files from SolidWorks
      2. Generate MST for install
        1. If you have more than 30 installs of SolidWorks and are still using the SolidWorks Installation Manager, stop.    We have found that its bulky and doesn't work that well when you are doing mass installs.  We went from a 25% failure rate to less than 1% failure rate when we switched from the SolidWorks Installation Manager to MSI installs.
      3. Create Deployments for SolidWorks Prerequisites
      4. Create Deployment for SolidWorks 2014 x64 SP04


      Download Install Files from SolidWorks

      This one is pretty self-explanatory, make sure you select Download Only and download a full copy of SolidWorks.  When it is done downloading copy the install files to the fileserver you are using for SCCM.


      Generate MST for Install

      Browse out to the SolidWorks Installation Guide and go to page 44.  Pages 44-47 will have all the command line properties you will need to make your MST.  The Command Line Feature Properties are for specific features of SolidWorks, such as Costing or PhotoView.  Command Line Global Properties are for installation properties, such as the install directory or serial number.


      Generating the MST is actually very easy once you have all the command line properties.  In the SolidWorks installation directory there is a program called SwCreateMST.exe that will create your MST. Make a batch file that calls the SwCreateMST.exe, then points at solidworks.msi and then has your settings behind it.  A copy of what we use is below. 


      Please note that spelling and capitalization are important!  Make sure your command line properties are spelled and capitalized exactly how they are listed in the SolidWorks Installation Guide.  According to SwCreateMST.exe, SolidWorksRoutedsystems is different than SolidWorksRoutedSystems.


      "\\fileserver\Sources\Dassault Systems\SolidWorks 2014 x64 SP04\swwi\data\SwCreateMST.exe" "\\fileserver\Sources\Dassault Systems\SolidWorks 2014 x64 SP04\swwi\data\solidworks.msi"  INSTALLDIR="C:\Program Files\Solidworks Corp" SOLIDWORKSSERIALNUMBER="XXXX-XXXX-XXXX-XXXX-XXXX-XXXX" ENABLEPERFORMANCE=0 OFFICEOPTION=3 SERVERLIST="25734@servername" UPGRADESWINSTALL=0 TOOLBOXFOLDER="C:\Solidworks Data 2014 SP4" ADDLOCAL=SolidWorks,FeatureWorks,PhotoView,SolidWorksRoutedsystems,SolidWorksUtilities,TolAnalyst,CircuitWorks,SolidWorksCosting,SolidWorksDesignChecker,ExampleFiles,Manuals,HelpFiles,Vsta,Motion,Simulation


      After you run your batch file you will see a new file in the \swwi\data directory called solidworks.mst.   That will be the file you use to customize the SolidWorks install.


      Create Deployments for SolidWorks Prerequisites

      Within SCCM you will need to create an Application for each of the 13 (assuming you are using Windows 7 x64) SolidWorks Prerequisites.  Most of the prerequisites are Script Installers, some are Windows Installers.  Just depends how they are packaged.  Page 32 of the SolidWorks Installation Guide has all the information you need about the prerequisites and how to install them. 


      For all of my Detection Rules I used the MSI GUID and then made sure the MSI Property Version was greater than or equal to the SolidWorks Perquisite value.  There are a number of prerequisites that may already be installed and updated through Windows Update so their property version may be higher then what SolidWorks requires.


      Below are all the file versions and command lines to silence the installs of the prerequisites.

      • Office Web Components
        • Version: 12.0.6213.100
        • \prereqs\OfficeWeb\owc11.exe" /quiet
      • Visual C++ 2005 Redistributable Package x86
        • Version: 8.0.61001
        • \prereqs\VCRedist\vcredist_x86.exe" /q
      • Visual C++ 2005 Redistributable Package x64
        • Version: 8.0.59192
        • \prereqs\VCRedist\vcredist_x64.exe" /q
      • Visual C++ 2008 Redistributable Package x86
        • Version: 9.0.30729.6161
        • \prereqs\VCRedist9\vcredist_x86.exe" /q
      • Visual C++ 2008 Redistributable Package x64
        • Version: 9.0.30729.6161
        • \prereqs\VCRedist9\vcredist_x64.exe" /q
      • Visual C++ 2010 Redistributable Package x86
        • Version: 10.0.40219
        • \prereqs\VCRedist10\vcredist_x86.exe" /q
      • Visual C++ 2010 Redistributable Package x64
        • Version: 10.0.40219
        • \prereqs\VCRedist10\vcredist_x64.exe" /q
      • Visual Studio Tools for Applications
        • Version: 8.0.50727.146
        • \prereqs\VSTA\vsta_aide.msi" /q
      • Visual Studio Remote Debugger
        • Version: 8.0.50727.1844
        • \prereqs\RemoteDebugger\rdbgexp.msi" /q
      • Visual Basic 7.1
        • Version:
        • \prereqs\VBA\vba71.msi" /q
      • Visual Basic English
        • Version:
        • \prereqs\VBA\vba71_1033.msi" /q
      • .NET Framework 4
        • Version: 4.0.30319
        • \prereqs\dotNetFx\dotNetFx40_Full_x86_x64.exe" /q /norestart
      • Bonjour service for Windows
        • Version:
        • \prereqs\Bonjour\Bonjour64.msi" /q


      Create Deployment for SolidWorks 2014 x64 SP04

      Setting up the Application Deployment for SolidWorks in SCCM is where things get funky.  We use a Script Installer with a batch file in SCCM because SolidWorks will not install by importing the MSI and because we do a couple customizations.


      Before setting up the Application Deployment we make a couple of changes to the swwi folder.  First we copy the solidworks.mst that was created earlier out of the data folder and into the root of the swwi folder.  Then we make a folder called Reference Files where we put a couple of registry files we call during the install.  And finally we make an install batch file in the root of the swwi folder.


      The install batch file is copied below but the general work flow of our install batch file is:

      • Uninstall previous version of Solidworks using Msiexec.exe /x
      • Remove the Solidworks Installation Manager
      • Delete any leftover folders
      • Delete any leftover registry keys
      • Install SolidWorks


      The most important thing to note about the install batch file is that you cannot use Msiexec.exe to call solidworks.msi.  For some lovely reason when we try to use msiexec.exe /i solidworks.msi the install fill fail.  When we take the msiexec.exe /i solidworks.msi out it works just fine.  We don't know if its poor coding on Solidwork's part but it is backwards from every other MSI installer we've come across.


      REM Uninstall Solidworks 2013 SP5.0

      MsiExec.exe /X{B6B5EA7E-B91F-443D-A958-B0062FB53804} /qn

      REM Uninstall Solidworks Installation Manager

      regedit /s ".\Reference Files\SLDIMUninstall.reg"

      REM Delete Leftover Files and Folders

      if exist "C:\Program Files\SolidWorks" rmdir /s /q "C:\Program Files\SolidWorks"

      if exist "C:\SolidWorks Data" rmdir /s /q "C:\Solidworks Data"

      if exist "C:\Program Files\SolidWorks Corp\Solidworks" rmdir /s /q "C:\Program Files\SolidWorks Corp\Solidworks"

      if exist "C:\Windows\Solidworks" rmdir /s /q "C:\Windows\Solidworks"

      REM Delete Leftover Registry Files

      regedit /s ".\Reference Files\Wipe-SW-CU.reg"

      regedit /s ".\Reference Files\Wipe-SW-LM.reg"

      REM Install Solidworks 2014 SP4.0

      ".\data\solidworks.msi" TRANSFORMS="solidworks.mst" /qn


      Once you have the install batch file created you can create the Application Deployment.  At this point it's pretty self-explanatory.  Set the content location as the swwi folder and the install program as the install batch file.  Add the all the prerequisites as dependencies, load up your distribution points and you should be all set.


      This is a pretty quick and dirty how to so hopefully it helps someone.  I don't know if some of the issues we run into are specific to us or everyone that uses SolidWorks but it seems that Solidworks does not follow normal standards.

        • Re: Deploying SolidWorks with SCCM 2012 SP1
          Nick Mallard

          Lovely writeup, I'm wanting to give this a go however from where would one get those registry files? Not really wanting to install Solidworks on over 100 machines manually when even then I can only do 4 at a time before it fails!

            • Re: Deploying SolidWorks with SCCM 2012 SP1
              Support Admin



              The Wipe-SW-LM and Wipe-SW-CU reg files have been floating around here for a while.  One deletes left over HKLM reg keys and the other deletes left over HKCU reg keys.




              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2005]

              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2006]

              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2007]

              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2008]

              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2011]

              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2012]

              [-HKEY_LOCAL_MACHINE\Software\SolidWorks\SolidWorks 2013]





              [-HKEY_CURRENT_USER\Software\Bluebeam Software]


              [-HKEY_CURRENT_USER\ Software\GSSL]

              [-HKEY_CURRENT_USER\ Software\Moldflow]

              [-HKEY_CURRENT_USER\ Software\SolidWorks BackOffice]



              The SLDIMUninstall.reg is a little tricky.  The path will depend what version you have installed so you'll have to do a little hunting to find it.



              Windows Registry Editor Version 5.00

              [-HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\SolidWorks Installation Manager 20130-40500-1100-100]

            • Re: Deploying SolidWorks with SCCM 2012 SP1
              Mark Landin

              This is exceptionally helpful! Thanks! We are on SCCM 2012 so we might be doing our 2014 deployment like this.


              One thing that's a little different for us is that we have about 7 locations worldwide we need to install for, and each has a different licensing setup ... some are node-locked, some are network only, and some sites have a mix of node-locked and network. I use the Installation Manager to build the installation depot, then cusotmize an AdminDirectory.xml file for each site that references the appropriate site-customized users.xml file that has the right licensing info for their location. When a user launches the install, I have a custom script that detects the office location (based on IP subnet) and then determines which AdminDirector.xml file should be used for them.


              Would this approach mesh well with what you've done? Or do you suggest a better way to handle licensing customizations that need to vary by installation site?

              • Re: Deploying SolidWorks with SCCM 2012 SP1
                Josiah Sansone

                I realize this is an old thread but have you done this procedure in 2015 and are there any updates to it? Our company has 150-200 SW seats and up till now upgrading has been on a site by site basis, but we are too often out of sync so there is an initiative to globalize the upgrade and push it out automatically.  SW Admin Image installer seems horribly ineffective and buggy for this type of deployment.

                I've been trying some pf these command lines and I've been having trouble getting SW 2014 to uninstall via command line. It seems to start the uninstaller but all it does is remove the SW 2014 entry from the Installed Programs and Features, but the program is actually still there.

                Also, I'm trying to deploy SW Flow Sim along with SW, and it appears you have to install that as a separate package, unless I'm missing something?

                  • Re: Deploying SolidWorks with SCCM 2012 SP1
                    Jeffrey Buck

                    Hi Josiah,


                    It may be a bit late for you now, but I used this process for installing 2015/16 edition and it worked for me. It was a bit of a pain having to edit the registry for the "RemappedElevatedProxiesPolicy" fix, but I got around this by creating 4 separate applications, then deploying them as a Task Sequence.


                    The applications are:


                    Disable Registry Key

                    Install PreRequisites

                    Install SolidWorks

                    Enable Registry Key


                    I hope this helps.

                  • Re: Deploying SolidWorks with SCCM 2012 SP1
                    Peter Van De Bogert

                    I was using this procedure to create a new image for 2017SP5 to be deployed with SCCM. My predecessor, created images for 2017SP3 prior to his departure that were not deployed. We’re now in the process of reviving the upgrade from 2015 SP5 to 2017 SP5.

                    2017 SP3 was packaged to be deployed in the following manner:

                    2017, along with SW2017eDrawings, Composer Player, and SW Explorer

                    Individual deployment of the following modules…


                    Composer Player (Non SW users)


                    eDrawings No SW


                    Flow Simulation



                    I created the original image downloading all the modules shown above. I basically understand how to create the image for just the basic
                    SW2017 image, but I’m more than a little confused how to create the separate images for the other modules?

                    • Re: Deploying SolidWorks with SCCM 2012 SP1
                      Matthew Brahm

                      Does this method still work for 2019?

                        • Re: Deploying SolidWorks with SCCM 2012 SP1
                          Jeffrey Buck

                          In a word, YES.


                          However the list of PreReqs has changed over the years, and if you want to include eDrawings you will need an additional deployment type. Here's a brief snapshot of the deployment types in my application, note the priority and dependencies.



                          Set server location is a registry hack which points to the server - [HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager]


                          The script for launching the eDrawings msi installer is - msiexec /i "eDrawings.msi" LOGPERFORMANCE=0 SNLSERVER=25734@servername/IP TRANSFORMS=1033.mst ADDLOCAL=All /q

                            • Re: Deploying SolidWorks with SCCM 2012 SP1
                              Matthew Brahm

                              Yeah, it looks like they have all the prereq's in here, unfortunately it seems like one of the prereq's doesn't have a silent switch, but I'm sure I'll find a way around that.  Definitely not using the admin option editor again, good grief. 


                              and yeah, I've always kept edrawings separate, and then I also do a separate install for just PDM users, and then I'm probably going to have like 3 deployment types for users with Visualize, users with Flow Simulation, et cetera. 

                                • Re: Deploying SolidWorks with SCCM 2012 SP1
                                  Jeffrey Buck

                                  I work in a college, so I make all of the required tools available on all computers, as you never know when they are going to be required.


                                  Which PreReq are you having a problem with? All of mine work with the /q switch, apart from the below


                                  REM    Windows Performance Tools

                                  "%~dp0WPT\WPTx64-x86_en-us.msi" /QN /NORESTART

                                    • Re: Deploying SolidWorks with SCCM 2012 SP1
                                      Matthew Brahm

                                      We discussed whether we would do that or not, and I didn't want to give everyone all the tools, because I don't want to be the one that has to manage the licenses when too many people use something.  We give people exactly what they need, and then we also limit them by creating groups on the license server. 


                                      The specific prereq that I am having issues with is the .NET Framework 4.6.2.  It will install silently, but if it's already installed, a dialog box pops up saying something like "this version or a higher versio of .NET Framework is already installed." which could cause issues during a silent deployment.


                                      NDP462-KB3151800-x86-x64-AllOS-ENU.exe is the file, and it doesn't seem to accept any switches.