Solidworks msi on CC3

[riskyburden]

It appears this week is technology package building week

So I've read the SolidWorks 2008 install guide that includes all the notes on building it for CC3, only it still doesn't quite work. I have got to the point where it installs fine but isn't combining the mst with the msi properly so the licence server info isn't included in the package. This means I'd have to go round each PC and add that information into the software manually (not happy). So i tried combining the mst and the msi with orca (has worked before) this left me with a duff msi that wouldn't install. so here's my plee, has anyone got around this. Cheers and Right on!

[kmount]

Can you show us the package ini file for the package you've created?

 

Example of a working package with transforms.

 

[Package]

Description=Pro/Desktop 8.0

Version=1.0.0.1

OS=5.WS

WIPackage=ProDesktop 8.0.msi

reboots=1

WITransform=PTC ProDESKTOP 8.0.mst

WITransform=PTC ProDESKTOP 8.0 Graphics Fix.mst

InstallGroup=Late

[riskyburden]

[Package]

WIPackage=English_i386_SolidWorks.Msi

Description=Package for Solidworks 2008 SP2.1

OS=5.WS

Transform=English_i386_SolidWorks.Mst

Dependencies=Microsoft dotNet 3.5,Microsoft Visual C Plus Plus 2005 Runtime

[kmount]

Transform=English_i386_SolidWorks.Mst

 

Try changing that to how mine is, it might just work.

[riskyburden]

[Package]

WIPackage=English_i386_SolidWorks.Msi

Description=Package for Solidworks 2008 SP2.1

OS=5.WS

WITransform=English_i386_SolidWorks.Mst

Dependencies=Microsoft dotNet 3.5,Microsoft Visual C Plus Plus 2005 Runtime

 

I'll restore my package station and post back. Cheers

[riskyburden]

I tried what you said and installed it onto a build station unfortuantly its still the same. I have to go into the solidnetwork license administrator and add our server in

[kmount]

Look in the event viewer and see if the mst is applying.

 

Did you create the mst or was it supplied?

[riskyburden]

Theres nothing in the event viewer that remarks on applying the mst. and no the mst was one I've created using solidworks CC3 install guide. this is the command suggested at the command prompt in the solidworks msi folder: SwCreateMST.exe English_i386_SolidWorks.msi INSTALLDIR="C:\Program Files\SolidWorks" SOLIDWORKSSERIALNUMBER="9710 *************" ADDLOCAL=English,SampleFiles,Manuals,RealViewGraphicsdisplay,SolidWorks,InstantWebsite,PhotoWorksRender,ScanTo3D,SolidWorksAnimator,SolidWorksDesignChecker,SolidWorksRoutedsystems,SolidWorksTaskScheduler,SolidWorksToolbox,SolidWorksUtilities,TolAnalyst,ExampleFiles,HelpFiles,Intel_Modules_AgeiaX86 ENABLEPERFORMANCE=0 INSTALLWDS=0 SERVERLIST=25734@pcn-svr-vid OFFICEOPTION=0 Edited December 10, 2008 by riskyburden

[riskyburden]

I'm going to try and capture the changes and add to the existing msi

[kmount]

You may wish to remove your S/N !!

 

I wouldn't recommend hacking the supplied msi ....

 

I'll have a nose later on.

[riskyburden]

whoops

[Cache]

I had exactly the same problem for whatever reason. The only way arround it I found was to allocate all the solidworks stuff out to the clean workstation, start a package capture, input the server details, finish capture, tidy up then make it dependant on SolidWorks so that it was installed after Solidworks. That seemed to solve the issue, just means another package that needs to be allocated out.

 

Never did work out why it didn't work with the MST.

[riskyburden]

I'm capturing the changes made after I've added the server details. I'll have a look with orca after to see if it needs a tidy.

[mrjonesybop]

Anyone packaged this for CC4? We've just been quoted £600 for RM to build us one, but funds are short - as usual!

[plexer]

I don't know the instructions for earlier versions but with 2010 they have the ability to create a file that is launched from an hta and can be run as another user that you could possibly use in a login/startup script or something?

 

Ben

[bossman]

Solidworks 2010-2011, built server, ran through the wizard on the server which built a package then transfered that package onto CC3 and made a batch file to run the install. worked perfectly and should hopefully transfer over to CC4.

 

start /wait sldim\sldIM.exe /adminclient /new /source ".\AdminDirector.xml"

 

This is the contents of the package:

 

 

hope this works for you.