AnsweredAssumed Answered

Installing Solidworks 2013 via SCCM 2012

Question asked by Nick Walton on Jul 12, 2013
Latest reply on Jul 25, 2014 by Support Admin

   Hi all,

 

Having major troubles with deploying SW2013 via SCCM 2012.

 

All pre requisite packages go on fine with command stipulated in the instructions but the Solidworks 2013 main MSI (32bit) fails even when give the following command line:

 

msiexec.exe /i "SolidWorks.Msi" INSTALLDIR="C:\Program Files\Solidworks" SOLIDWORKSSERIALNUMBER="xxxx xxxx xxxx xxxx" ENABLEPERFORMANCE=0 OFFICEOPTION=3 TOOLBOXFOLDER="C:\Program Files\SolidWorks\Toolbox2013" SERVERLIST="25734@oursever" ADDLOCAL=ALL /l*c c:\solidworks.log /qn

 

 

I've tried creating transforms but with no luck as to improving the situation. The end of the MSI install log for the failed code 1603 deployment is as follows:

 

.......

Property(S): CostingComplete = 1

Property(S): SYSTEMPRIMARYLANGID = 9

Property(S): SourcedirProduct = {B85DDD77-4A6A-4811-B241-EDADBF996BD0}

Property(S): OutOfDiskSpace = 0

Property(S): OutOfNoRbDiskSpace = 0

Property(S): PrimaryVolumeSpaceAvailable = 0

Property(S): PrimaryVolumeSpaceRequired = 0

Property(S): PrimaryVolumeSpaceRemaining = 0

Property(S): FEATURESTATE = 3

Property(S): I386SUPPORTTURKISH = C:\Windows\ccmcache\q\Support\i386\Lang\Turkish\

Property(S): OldOfficeOption = 3

Property(S): SOLIDWORKSSERIALNUMBER16 = 9710 0096 3983 0494

Property(S): ProductToBeRegistered = 1

MSI (s) (00:AC) [19:14:07:496]: Product: SolidWorks 2013 SP02 -- Installation operation failed.

 

 

MSI (s) (00:AC) [19:14:07:532]: Windows Installer installed the product. Product Name: SolidWorks 2013 SP02. Product Version: 21.120.50. Product Language: 1033. Manufacturer: SolidWorks. Installation success or error status: 1603.

 

 

=== Logging stopped: 12/07/2013  19:14:07 ===

 

 

 

Also when this command line is run locally (with correct inserted paths for the msi) it installs the software successfully. But not when the same is applied in SCCM as an unattended installation with administrator rights set to deploy whether or not a user is logged in. Actually watching a client the deployment starts to fill up the isntalltion directory up until about 3 - 4GB then the msi seems to fail and all data is quickly deleted. This is the same for creating an admin image with SP2 and SP3.

 

Can anyone help?

Outcomes