FlexLM Upgrade

[michael montagne]

I'm upgrading from Acad2004 to Acad2005.
From reading this list I understand that I can upgrade flexLM to
version 9.2 (for Acad2005) by stopping the service and uninstalling the
old version and installing the new version. Or I can just copy the 4
key files from the CD. Then I can use my existing .lic file as is.
Even though my serial number is different. The end result will be that
I can serve my 18 licenses to either Acad2005 clients OR Acad2004 clients.
Do I understand this correctly?

What about the need to install a new Network Installation Wizard. I
don't build my network install images from that server, do I still need
to upgrade it? (If it even exists on that machine)

thanks,
mjm

[Allen Jessup]

No. Not if I understand you correctly. I've read that upgrade method would
work but I have not tried it. You can reuse your 2004 license whichever way
you upgrade. However you will need to obtain NEW license files for 2005 and
add these to your existing license file.

You only need to install the wizard on the server where you will create the
deployments.

Allen

"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fc20a0_3@newsprd01...

I'm upgrading from Acad2004 to Acad2005.
From reading this list I understand that I can upgrade flexLM to
version 9.2 (for Acad2005) by stopping the service and uninstalling the
old version and installing the new version. Or I can just copy the 4
key files from the CD. Then I can use my existing .lic file as is.
Even though my serial number is different. The end result will be that
I can serve my 18 licenses to either Acad2005 clients OR Acad2004 clients.
Do I understand this correctly?

What about the need to install a new Network Installation Wizard. I
don't build my network install images from that server, do I still need
to upgrade it? (If it even exists on that machine)

thanks,
mjm

[michael montagne]

Sounds like that should be right. I have an existing .lic file for 18
seats of Acad2004. I just called and got one for 18 seats of Acad2005.
But my transition will be gradual. What is the best way to manage
switching 5 seats per week? Do I need to keep calling for new .lic
files each time I change?


-mjm



Allen Jessup wrote:

No. Not if I understand you correctly. I've read that upgrade method would
work but I have not tried it. You can reuse your 2004 license whichever way
you upgrade. However you will need to obtain NEW license files for 2005 and
add these to your existing license file.

You only need to install the wizard on the server where you will create the
deployments.

Allen

"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fc20a0_3@newsprd01...

I'm upgrading from Acad2004 to Acad2005.
From reading this list I understand that I can upgrade flexLM to
version 9.2 (for Acad2005) by stopping the service and uninstalling the
old version and installing the new version. Or I can just copy the 4
key files from the CD. Then I can use my existing .lic file as is.
Even though my serial number is different. The end result will be that
I can serve my 18 licenses to either Acad2005 clients OR Acad2004 clients.
Do I understand this correctly?

What about the need to install a new Network Installation Wizard. I
don't build my network install images from that server, do I still need
to upgrade it? (If it even exists on that machine)

thanks,
mjm

[Jimmy Bergmark]

If you are on subscription you can have 2004 side by side with 2005 as long
as you don't use more than (in your cas) 18 licenses at the same time.

--
Best Regards, Jimmy Bergmark
CAD and Database Developer Manager at www.pharmadule-emtunga.com
Take a look at
JTB FlexReport (FLEXlm report tool) - www.jtbworld.com/jtbflexreport
SmartPurger (Purges automatically) - www.jtbworld.com/?/smartpurger.htm
or download some freeware at www.jtbworld.com
More on AutoCAD 2005;
www.jtbworld.com/autocad2005.htm


"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fc5a0b_3@newsprd01...

Sounds like that should be right. I have an existing .lic file for 18
seats of Acad2004. I just called and got one for 18 seats of Acad2005.
But my transition will be gradual. What is the best way to manage
switching 5 seats per week? Do I need to keep calling for new .lic
files each time I change?


-mjm



Allen Jessup wrote:

No. Not if I understand you correctly. I've read that upgrade method
would
work but I have not tried it. You can reuse your 2004 license whichever
way
you upgrade. However you will need to obtain NEW license files for 2005
and
add these to your existing license file.

You only need to install the wizard on the server where you will create
the
deployments.

Allen

"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fc20a0_3@newsprd01...

I'm upgrading from Acad2004 to Acad2005.
From reading this list I understand that I can upgrade flexLM to
version 9.2 (for Acad2005) by stopping the service and uninstalling the
old version and installing the new version. Or I can just copy the 4
key files from the CD. Then I can use my existing .lic file as is.
Even though my serial number is different. The end result will be that
I can serve my 18 licenses to either Acad2005 clients OR Acad2004
clients.
Do I understand this correctly?

What about the need to install a new Network Installation Wizard. I
don't build my network install images from that server, do I still need
to upgrade it? (If it even exists on that machine)

thanks,
mjm

[Allen Jessup]

After you upgrade FlexLM combine your license files into 1 file. This will
run under the new FlexLM. Create the deployments on whatever server you want
using the Wizard. Install on client workstations at your leisure. As
mentioned 2004 & 2005 will run concurrently.

Allen

"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fc5a0b_3@newsprd01...

Sounds like that should be right. I have an existing .lic file for 18
seats of Acad2004. I just called and got one for 18 seats of Acad2005.
But my transition will be gradual. What is the best way to manage
switching 5 seats per week? Do I need to keep calling for new .lic
files each time I change?


-mjm

[michael montagne]

But the .lic file they gave me for acad2005 is for 18 licenses and the
previous one is also for 18 licenses. Doesn't that make 36? Is it just
up to me not to exceed my limit?

-mjm

Allen Jessup wrote:

After you upgrade FlexLM combine your license files into 1 file. This will
run under the new FlexLM. Create the deployments on whatever server you want
using the Wizard. Install on client workstations at your leisure. As
mentioned 2004 & 2005 will run concurrently.

Allen

"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fc5a0b_3@newsprd01...

Sounds like that should be right. I have an existing .lic file for 18
seats of Acad2004. I just called and got one for 18 seats of Acad2005.
But my transition will be gradual. What is the best way to manage
switching 5 seats per week? Do I need to keep calling for new .lic
files each time I change?


-mjm

[Allen Jessup]

Well. Yes. I wasn't considering that because we are Subscription customers.
You'd have to read the EULA or talk to your reseller. There is usually a
grace period when you can have both running. Just run no more that 18 at
once. Use that grace period to shake out the bugs in transitioning to the
new release.

Allen

"michael montagne" <mmontagne@walkermacy.com> wrote in message
news:40fd595e_2@newsprd01...

But the .lic file they gave me for acad2005 is for 18 licenses and the
previous one is also for 18 licenses. Doesn't that make 36? Is it just
up to me not to exceed my limit?

-mjm

Allen Jessup wrote:

After you upgrade FlexLM combine your license files into 1 file. This
will
run under the new FlexLM. Create the deployments on whatever server you
want
using the Wizard. Install on client workstations at your leisure. As
mentioned 2004 & 2005 will run concurrently.

Allen

[dstein]

Allen is correct. If you want to "push" users to migrate (I just migrated 500 across 22 offices, and users fight change), you can ask Autodesk for a 2004 license that bombs out on a specific date. Back up and replace the key value with the new one (for the 2004 licenses) and add the new 2005 license key in the same file. Now you have both running but 2004 will eventually die on the specified date. Gentle method for threatening your users if they whine about upgrading. :)