I was going to document this for my own purposes then saw this post so decided to write out a proper guide.
I'm using SCCM 2012 sp1 and I’m upgrading from SW2013, the method is the same but some of this may be subsequently slightly paraphrased. Also worth noting is it's a pretty big software application so if it's simply not downloading the content from your distribution point you may need to increase the SCCM software cache size on your clients, especially if you have other installs happening. I think the default cache is 15-20gb and SW2014 install is around 6-7gb.
Firstly you're going to need to create software packages in SCCM for the prereqs. There's a lot of them on the disk but the only ones you really need are the MS C++ redistributables (one each for 2005, 2008 and 2010) and MS Visual Studio (VSTA) provided you're running Win7 or above. They're only small .msi files so pull into sccm with a quick run through of the Application Creation Wizard selecting .msi file. If you doing both x86 and x64 install you'll need to do both so eight applications total. Some people may have these as part of their windows gold image or already preinstalled. If that’s the case you can skip this step and the one’s further on when I explain about dependencies.
Next you need to install the licence monitoring software on the server, registering your licence keys and such. Put the disk into your server or like me browse to your cd share if you're using VMs, run setup.exe and follow the instructions on disk. VM’s massively take the sting out of having to use licence monitoring software.
Now create the Solidworks software images. Put the disk into your workstation and again run setup.exe. Choose the option to create the software images and if you’re doing x64 as well then go ahead and check that box also. I think the wizard will ask you if you want to download the latest version, which at the time of writing is sp4. sp2 is on the disk I have so I would say go ahead and do that if your internet throughput is decent enough to pull down 11gb of data fairly quickly. It’ll also ask for the address for you licence server at some point which needs to be correct. Afterwards you can tweak your install directories to make sure that fits your software restrictions.
Once you’ve finished with that and you have your images created and tweaked, copy them across to your SCCM server or application storage area. You’re then ready to create the applications in SCCM. If you need to do one for each for x86/x64 you’ll need to run through this twice:
Go to Software Library in SCCM and Applications and Create Application.
In the Wizard select Manually Specify and click next.
Put any relevant info in that’d you’d like, most importantly give it a name (eg Solidworks 2014 x86) and version (SP2/SP4) and click next.
On the next page optionally input any documentation, description or keywords for the software, click next. (I don’t bother)
In deployment types select Add.
In the Create Deployment Type Wizard drop down the Type box and select Script installer, click next.
Type a name, give it the same as the software name or whatever. Click next.
In the content location box browse to the network folder where you copied your images to. Select the folder with startswinstall.exe file in it. e.g \\servername\sharename$\sccmapplications\Solidworks2014\Solidworks_2014_sp4
On your Installation Program browse and choose startswinstall.exe (might say publisher could not be verified, just proceed)
On uninstall program do the same choosing startswinstall.exe (this might be incorrect, I’ve never uninstalled it but it should just add /x or equivalent switch to the script though), click next.
On Detection Method click Add Clause. This is really important because it determines whether the software has installed on the client and how it reports that information back to the server. I couldn’t find the unique reg key (which is what lead me to this article in the first place and subsequently write all this) so in Setting Type select File System, in Type select File, for Path select your install dir (e.g C:\Program files\Solidworks Corp\Solidworks) and in File or Folder Name type SLDWORKS.exe. For mine because I upgraded from 2013 I needed it to differentiate between this install and the older version so I put a Date Modified, Equals or Greater Than, 01/06/14 clause on that also. Click OK.
Click next
On User Experience select Install for System in the Installation Behaviour and Whether or Not a User is Logged on, keep the program visibility Normal you can hide it upon deployment and it’s better to have it there for troubleshooting. Click next.
There are no necessary requirements, unless you fancy adding some click next.
In Dependencies click add. Enter a name of C++ redistributables 2005, browse to that software on the left panel click it on the Top right and check the box for it on the bottom right panel. Click OK and repeat this step for the other 3 prereqs (Redist 2008, 2010 and MS VSTA). Click OK.
Click next on summery, Progress and Completion until the Wizard Finishes
Right Click your software in applications and click Distribute Content to publish it to your Distribution Point following the wizard.
Right Click the software again and deploy it to a device collection with a test PC. Preferably a Virtual Machine with a snapshot you can revert to should you need to do any troubleshooting.
That about wraps it up. If you get any fails don't worry it might be installed fine and your detection rule could be wrong. A tip worth noting is that if you make any changes to your Application once the package is created you can update it on your DP by going to your Application>right click>Properties>Content Location Tab>Redistribute Button.
Well I hope that all helps and isn't a case of tl;dr.
