1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

SolidWorks deployment step by step

Avatar
Marcel Stürtz

Bonjour

I'd like to share my PDQ deployment of SolidWorks 2018. Ours is SolidWorks Premium with network license.

I have created an administrative image. What you end up with is a huge install directory with several dependencies.

I have created steps for each dependency as described in: SolidWorks Support

But the real problems begin with installation of the separate SolidWorks Client. I achieved that by issuing a command-line like this:

msiexec.exe /i "<full UNC path to administrative image>\64bit\SOLIDWORKS\SolidWorks.Msi" INSTALLDIR="C:\Program Files\SolidWorks 2018" SOLIDWORKSSERIALNUMBER="<serial number with spaces every four characters>" ENABLEPERFORMANCE=1 OFFICEOPTION=3 ADDLOCAL=SolidWorks,FeatureWorks,PhotoView,SolidWorksAnimator,SolidWorksToolbox,SolidWorksRoutedsystems,SolidWorksUtilities,ScanTo3D,CoreSolidWorksTaskScheduler,TolAnalyst,CircuitWorks,Simulation,Motion,SolidWorksCosting,SolidWorksDesignChecker,ExampleFiles,Manuals,HelpFiles SERVERLIST="25734@<license server>" TOOLBOXFOLDER="C:\SolidWorks Data 2018" /qb

msiexec.exe /i "<full UNC path to administrative image>\64bit\eDrawings\eDrawings.msi" INSTALLDIR="C:\Program Files\eDrawings 2018" LOGPERFORMANCE=1 SNLSERVER="25734@<license server>" TRANSFORMS=1040.mst ADDLOCAL=All /qb

msiexec.exe /i "<full UNC path to administrative image>\64bit\SOLIDWORKS CAM\SolidWorks CAM.msi" ALLUSERS=1 /qb

msiexec.exe /i "<full UNC path to administrative image>\64bit\SOLIDWORKS Visualize\solidworks visualize.msi" ACTIVESERIALNUMBER="<serial number with spaces every four characters>" SERVERLIST="25734@<license server>" /qb

The ADDLOCAL parameters are case-sensitive, the rest is documented here

0

Comments

4 comments
Date Votes
  • Avatar
    williamb

    Thanks for parting your knowledge on this - I'm also currently looking at performing in-place upgrades too. Is this something you've got working as well?

    0
  • Avatar
    Marcel Stürtz

    Not yet; I have downloaded SW 2019 SP1 and SP2 and could try to deploy SP1 and then upgrade to SP2. Will try it next week probably. . The 2019 has to be installed next to the 2018 install, not upgrading it. The SP2 package will have to determine if it is an upgrade from SP1 or new install, I can achieve this by querying PDQ inventory collection memberships.

    0
  • Avatar
    williamb

    I've conducted a few tests in the last few hours, and it seems easy enough to perform an upgrade - however for individual parts like SolidWorks Inspection, there is no upgrade path, and you simply have to install the new version along side. Perhaps running post uninstall scripts to the older version.

    0
  • Avatar
    Marcel Stürtz

    I got back from my holiday and some users complained about not having the Routing Add-in installed. Changed the first commandline, replaced

    ADDLOCAL=SolidWorks,SolidWorksToolbox

    with

    ADDLOCAL=SolidWorks,FeatureWorks,PhotoView,SolidWorksAnimator,SolidWorksToolbox,SolidWorksRoutedsystems,SolidWorksUtilities,ScanTo3D,CoreSolidWorksTaskScheduler,TolAnalyst,CircuitWorks,Simulation,Motion,SolidWorksCosting,SolidWorksDesignChecker,ExampleFiles,Manuals,HelpFiles

    You can find the necessary ADDLOCAL parameters in the original deployment;

    \64bit\AdminDirector.xml
    0