Is that the sound of a 65% speed increase and 250 eye-peeling enhancements coming at you with the ferocity of a one-eyed lemur?
It is, give or take a few percentage points. Suddenly, your ability to blink repeatedly is compromised by the idea that SolidWorks 2009 is speedier. And perhaps you are perplexed by the question that faces many… “Should I upgrade to SolidWorks 2009?”
Over the next month or so, the installation DVD will show up. However, you can rise against the mail delivery system and download it right now from the SolidWorks customer portal.
Then what? Do you upgrade the old version or run multiple versions? Roll it out to everyone or test it out with a few? Let’s knock it around a little bit and get you going.
Taking on a new SolidWorks Installation
If you’ve seen some of What’s New in SolidWorks 2009, you may be ready to move on from 2008. Deciding when and if to upgrade can be difficult, especially when you stack it against all the other work you’re up against. This guide aims to make the task of upgrading SolidWorks a bit clearer.
There’s two ways you can upgrade when you decide to download the files. You can use the SolidWorks Installation Manager, which is the easiest (if you don’t run into problems), or you can download the individual files and do a more manual-type installation. This focuses on using the SolidWorks Installation Manager because it’s quicker for you and I don’t have to type so much.
You’ll think this is cool if…
… if you’re struggling with some of the idiosyncrasies of using the Installation Manager to install a License Server and/or Administrative Image. That simple. It’s not the supreme guide to installing a new version of SolidWorks. We figure you want to install it and want a good resource and a few tips to help you along the way. Plus, it helps to have a place where you can discuss all that.
Are you ready for this?
There’s generally two main areas that you’ll want to consider before upgrading.
Installing multiple versions or upgrading?
It stinks, but you may need to run multiple installations of SolidWorks. If you need to upgrade but have projects and clients using other versions, the best option is to upgrade the people that will be using SolidWorks 2009 and then upgrade the rest when it’s safe to do so. The only problem here is that you run the risk of accidentally upgrading a file to the new version. So if this is a problem wait till all other projects are done and set a date to begin the installation.
What to test before upgrading?
If you’re a CAD administrator, you have probably already done this. If not, do a single installation either on your computer or someone who will be using it and run through some test against other software used with SolidWorks, any custom programs that interface with the SolidWorks API, and even some modeling methods your company uses. If you work directly with a production shop, you may also want to work with them on when to upgrade together. A whole post could be written on this, but generally, coordinate all the upgrades with anyone other division or company that will need to upgrade as well.
Pre-Installation checklist
So, the first thing you want is a pre-installation checklist. It makes you look all professional and you can show all the checked off items to people so they will think you’re really organized and knowledgeable about more things than they are. Here’s one to get started with.
__ Determine best time to install upgrade
__ Gather SolidWorks license info, seat and computer names
__ Send memo/email to managment/users to notify of upgrade
__ Download installation package (if you don’t have the DVD)
__ Check if Anti-Virus software needs disabled
__ Determine installation type from the SolidWorks and Installation Guide
__ Document server name/setting/login for server and admin image installs
Note on when to install: You’ll want to be aware of two things 1) what other programs you use in conjunction with SolidWorks and 2) if your customers are able to upgrade as well. The last thing you want is a program not working or the fiery rage of a customer not able to open files.
It’s about to get messy up in here
Doing a typical stand-alone installation is pretty simple with the Installation Manager. It’s when you start messing with Administrative Images and SolidWorks Network License that it all becomes a hairy mess. (that sounds gross). They can make installation and administration easier, but some of the set-up and usage is a bit obscure. So first, here we go with that safe and orderly fashion of installing multiple licenses with an Administrative Image.
Suggestions for using an Administrative Image
First of all, these are nothing to be scared of. It’s easy to set-up if you have a small knowledge of computers. There’s just some things you want to be aware of.
Basically, an Administrative Image is a copy (image) of the installation. You want that sucker on a network location where everyone can access it. The SolidWorks installation on someone’s computer (the client) is initiated from here. An Image automates upgrades/rollbacks and settings. It’s extremely helpful when doing large installations.
If you’re installing more than one seat of SolidWorks, I recommend doing this. It will make the installation and management of the seats much easier. Here’s some tips to take away to the server room.
- Set aside a good chunk of time to create the image
- Make sure you have a drive with at least 10GB (It will take up about 8GB)
- Use a location that is write protected (but you will need access to it)
- Put it on a server other than you main file server (less traffic)
- Have a SolidWorks Options Setting File Ready (if possible)
- Add a how-to document to the directory that instructs others how to initiate an install
- If you don’t use the Installation Manager, you’ll have to install some files manually
Note: It can take several hours for the initial SolidWorks install and Image creation on the Server. Make sure there will not be any server maintenance or interruption in creating the Administrative Image cause it just sucks to have to go through it all again. I set my image up overnight. Likewise, you may want to have people run the installs overnight so it doesn’t interrupt any work.
Once you’ve successfully created the Image, you can simply email a link to everyone that will upgrade their version of SolidWorks. I’ll test this with one person first and if no issues come up, I’ll send it out to everyone else. The file they’ll need to run is /StartSWInstall.hta. An email link to this can cause issues, so I include a direct link to where the file is located, like so.
“If this doesn’t work click this: O:Mr. SolidWorks Image then double-click this file: StartSWInstall.hta“
Basically it’s a 6 step process using the Installation Manager to create an Image and get others going.
The 6 step Admin Image installation process
- Run SolidWorks Installation Manager
- Enter your serial number
- Select the Administrative Image and Server Product Option
- Choose the network drive to create the Image on
- Set your Administrative Image Options
- Email clients link to StartSWInstall.hta
Switching from stand-alone installations to a SolidWorks Network License (SNL) Installation
A SNL allows you to install SolidWorks on as many computers as you want. When you start SolidWorks it checks the License Server to see if there’s a license available. If there is, SolidWorks starts up, if not, it lets you know that all the licenses of SolidWorks are being used.
I’ve just done a site-wide installation of SolidWorks 2009 using a SolidWorks Network License and an Administrative image. I’ve done this in the past and remember it being a lot more complicated and while I’ve had problems with the Installation Manager before, this time it worked like a charm. I’ve had some question about doing this so here’s the steps I took to make sure it went well.
- Use a server that has 99.9% uptime
- Explain to IT that you will need access to manage/upgrade SNL and reboot server
- Keep a record of SNL management
- Write down your SNL and server setting
- Print out this sheet for IT
- Put your license file in the SolidNetWork License Manager Install Folder
- Create Instructions for restarting the License Server
- Create instructions for changing the license file
Additionally, I like to have a sheet that contain all the info about the SNL with contact information and any notes that would instruct other about how to manage a SNL.
SNL Quick Info
Your SNL server ________________________
SolidWorks licenses ______________________
License File location _____________________
License file expiration ____________________
IT Contact Info _________________________
Admin Contact Info ______________________
SolidWorks VAR Contact___________________
Notes _________________________________
_______________________________________
_______________________________________
Tips from Twitter
I also asked everyone on Twitter – “What is your best solidworks installation tip?”

@solidsmack Turn off anti-virus. If you’re not gonna run multiple installs, clear the registry data before the new install.

@solidsmack ALWAYS install into specific version directory (such as “SolidWorks2009”) instead of the default.

@solidsmack Installation tip: always start with a fresh cup of coffee (of course Kyle. what else would you start with 🙂
@solidsmack Know what your doing a create a plan of attack. Be sure to create a dataset and test it out before upgrading
What about you? Do you have some installation tips people can use? Problems installing SolidWorks that you would like to discuss? Hit the comments!
Other Great Resources for Installing SolidWorks 2009
Jason Raak – How to Successfully Implement SolidWorks 2009
Mike Puckett – How to Install SolidWorks 2009 from a Web Download
Brian McElyea – SolidWorks Administrative Install Images & SLDIM – Part 1