Seeking recommended general process for upgrading to 2017 Products. We are currently using: Solidworks mechanical, Solidworks Electrical, PDM Pro - All on 2016 SP4.
Can I upgrade just PDM server products along with the PDM client - and NOT upgrade Solidworks Mechanical or Electrical clients? Then later upgrade all clients to 2017 Mechanical or Electrical - along with the database. Is this a good or recommended process? Thank you.
We may go to SP3.0 when it is fully released. Wish I waited for 3.0 though...
I really enjoy 2017 as long as it doesn't hiccup (which it does a lot).
Perhaps wait for 3.0 and give it a shot?!
My apologies, yes I'll be upgrading to SP3 at least.
I'm just asking about the general upgrade process. Last year, I upgraded everything all at once and it seemed almost overwhelming. And I had people recommend the suggestion I stated above - Just doing PDM server and client ONLY, then upgrade database and all other products later. Just seeking feedback on that approach - or another good one! Thank you!
Hope this helps a little.
Scott Casale wrote:
- First, do your license server upgrade. It allows older versions to run.
This is absolutely true.
S. Casale. I saw a message today from Deepak Gupta's blog, that 2017 sp3 is released.
I can't do anything with it since I am off subscription but since you mentioned you were waiting I thought you would like to know.
Thanks for the heads up Rick McDonald. Much appreciated.
I'll watch the forums to see of any hiccups. Might roll it out next week.
Servers, licenses, PDM, and workstations all must be 2017. They must match.
IS this a new requirement for 2017?
What do you mean by "this?" there were a few different statements in the post. I do believe the first thing that has to be done is upgrading the license server. Otherwise, I wrote were suggestions I guess.
Here's the admin guide found in the customer portal>admin guides:
My apologies I didn't realize your response was to Chris, not myself.
Not that I'm aware of. I have never seen mixed versions run together. Unless, there is a trick I don't know of.
I have work with our VAR on this also. We always had to update everything to match versions (network licenses).
Robert,
To answer your original question. We upgrade the license manager server to the target version. Then we upgrade PDM (archive servers, database upgrade, clients) and eDrawings. Once the dust settles, we upgrade each other product (Mechanical, Electrical, Composer, etc.) individually with a break between each to clean up any issues.
Michael,
Do you roll out installations using an Admin Image? If so, how do you manage all of the different "pieces" w/o repetitive install/uninstall/install more, and so on?
Up to and including 2015, we used to upgrade license server, then EPDM, leaving SW on the prior version. Wait a few weeks then roll out matching SW version via Admin Image. Once SW Corp incorporated the PDM install in to the Admin Image as well, it was recommended to us to do it all at once, which with 200+ SW users on one side and 300+ PDM users on the other, this induces quite a bit of stress.
I asked if we could just use two separate images, first a PDM-only image, followed by an SW-only image. I was told that the SW-only image would effectively uninstall the PDM...but I never tested this due to time and resource constraints.
Alternately I asked if we could just stick to installing the PDM client manually through the files made available in the download's \swpdmclient folder, then follow with an SW-only Admin Image installation...was told that would be a bad idea, as the \swpdmclient folder would not contain the potential pre-reqs that a PC might need...much better to go through the Admin Image to install the PDM client.
So we're still going with the idea that we're stuck doing both at the same time via one Admin Image for both SW and PDM. Haven't had the opportunity to test otherwise.
Thanks,
Michael
We installed PDM the old fashioned way both for servers and clients. We will use the admin image for the other products.
We have not experienced file corruption with SP2.0 as others mentioned. Lucky I guess?
Dagnabit. I didn't mean to "Answer" this yet. Can I undo that?
Can't you just deselect the correct button?
We may go to SP3.0 when it is fully released. Wish I waited for 3.0 though...
I really enjoy 2017 as long as it doesn't hiccup (which it does a lot).
Perhaps wait for 3.0 and give it a shot?!