Welcome back. Now that you've gathered all the information and download, you're ready for the upgrade.
One of the (many) advantages EPDM has over Workgroup is the client version of SolidWorks doesn’t have to match the major version of EPDM. So it’s easy to upgrade and test right away from the SolidWorks clients. So we can just focus on upgrading EPDM.
1> Download or dvd.
Keep the download handy. It is needed for all phases of the upgrade, including the clients.
2> License file
EPDM uses a license file that needs to be downloaded – like the good ol’ days of SNL (if you don’t know what SNL means, then you likely don’t remember the good ol’ days either). After an upgrade, the first thing you want to do is login to the vault, but instead of congratulations for a job well done, you get an error message:
The license file is acquired via the Customer Portal – My Support->My Products->Get License. Have that handy before upgrading … and before backing up (sorry, I couldn’t stop myself from mentioning it again). You’ll also need to know the name of the machine hosting the SQL service and the SA password for SQL.
3> Installation Guide
Have the Installation Guide handy. After unpacking the download (or loading the dvd), the guide is found at C:\yourfoldername\Support\Guides – pick your native language. I’m not sure why, but rather than “E”nglish, the English version is under “GB”. Don’t get me wrong, I know what “GB” represents, but I’m pretty sure no one in the world speaks “GB”. Anyway, the upgrade discussion starts on page 93 in the 2013 guide. Next, as the bullet list above notes, we upgrade the archives.
If your installation has everything on the same server – archives, database, and SQL, then you can upgrade the archives and the database at the same time. In either case, the process is straightforward. The download is a zip file, the dvd will fire up on its own. Once the EPDM installation gets going, you will be presented with two options on the first screen – “upgrade” and “exit”. If you don’t, then stop and figure out why you think EPDM is installed on this machine, since it isn’t.
After selecting upgrade, the installation wizard will let you know what it finds:
Again, if this list doesn’t match your expectations, stop and check it out.
Honestly, there’s not much to it after that. You’ll get a warning that the archive and database are running, but just select the default to automatically stop those services. I’ve tried it both ways and this is the easiest. If you get some errors discussing failed dll registrations, take screenshots and contact your Reseller. But even in those cases, a reboot and “repair” often fixes the problem. Once the update is complete, login to the admin tool and add-in your new license file.
After upgrading the archive and database, the clients get upgraded. Here’s the good news – it’s the same process. You saw the client upgrade in the selection list while updating the database and archives. You’ll need this same set of downloaded files (or dvd) for each client, so maybe place it on a network location.
Next, the file vaults get updated. This is a very often missed step in the upgrade. The Installation Guide discusses it, but the shortcut is to start the upgrade wizard manually from the “Upgrade” folder on the install CD (or download folder) by running Upgrade.exe. There’s no mystery in the upgrade, but note that a reboot of the SQL server is recommended after upgrading the file vaults.
Finally, update the Task Add-ins and Tasks like Convert and Print and Dispatch. Again, this often gets missed and unless you use them, you’ll never know. SWTaskAdd-in and the Convert, Design Checker, and Print tasks are copied to the C:\Program Files\SolidWorks Enterprise PDM\Default Data\ folder. Open the Convert_GB.cex and drag/drop the Task Add-ins into the Task node. All of this is covered in the Installation Guide. If you have custom dispatch scripting, don’t worry, that gets updated, but the dll's need to be replaced with new ones. However, if you have modified the Tasks, those will have to be updated manually. Besides, you have a backup if anything goes wrong.
Next, upgrade toolbox. This process can have a few variations, but keep in mind, this is only necessary if you are alos upgrading SolidWorks. The basic and most common process is check out the entire toolbox (typically the SolidWorks Data folder), use the corresponding SolidWorks upgrade to update the toolbox, then check the toolbox folder back into the vault. Is simple, no?
Now, a word about upgrading all of your SolidWorks files that are in the vault - Why? SolidWorks got rid of the annoying pop-up telling you the files is old. I agree, it’s nice – I’m OCD, too. But it's easy to over-estimate the number of files actively accessed. Consider letting everyone update the files as they are updated.
Finally, I strongly recommend against skipping major versions. I have experience with a Customer where this has caused a problem. I understand the concern about upgrading for every service pack, but skipping major versions is asking a lot of SolidWorks developers. I mean every bug fix needs to look back how far? Anyway, save yourself some trouble and update every year.