Building New license server to deploy later

[elsiels]

I have a startup slowness issue when the users a pulling a license from the license server. If they borrow a license we do not have a slowness. I have done other troubleshooting and can not find the cause so I would like to build a new license server (the old one is over 6 years old the nic older), using 2009, then if everything goes fine when I deploy 2009 they will have a new license server. The thing is I will not be deploying 2009 until close to the end of the year. Will I be able to run both servers for that length of time, until I get the company upgraded?

Here is how I want to do this:
Build new license server.
Install 2009 on one PC testing speed of startup.
Once the users are ready (after the busy season), upgrade the rest of the machines to 2009.
Take down the old license server.

Again the entire process could take several months as they never allow an upgrade until frost. Which in ND usually comes around Nov, Dec.

[TravisNave]

I would simply recommend buiding your new license server now. Get your new 2009 license file ready. Then regenerate your old licenses and combine them with your new 2009 license. Retire your old License Manager and simply reconfigure each client to point to the new server. It is much more simple than you think. And when you're ready to deploy 2009, you'll already be set. That way you can rid your slowness issues now and not have to worry about it. There are too many weird issues that happen when you run more than one NLM anyway, so you want to avoid that.

In fact, if you are under Subscription with your current 2009 seats, you can actually run your older licenses going back to 2006 with your new license file. Makes it even easier.

Need more info? Let me know what you think.

[Anonymous]

Unless you get an OK from your reseller this would not be "allowed". What
would be allowed is if you make a distributed setup so you have one license
on the new server and one license less on the old server.
What you could do is to use a startup script on the clients and point to the
new server.
Here is one way I've used.
http://blog.jtbworld.com/2005/05/tips-when-changing-license-server.html

--
Jimmy Bergmark - Owner/Developer
JTB World - Software development and consulting
Website: http://www.jtbworld.com
Blog: http://blog.jtbworld.com

JTB FlexReport (FLEXnet / FLEXlm license report tool) -
www.jtbworld.com/jtbflexreport

AutoCAD 2009
http://www.jtbworld.com/autocad2009.htm

"elsiels" wrote in message news:6000987@discussion.autodesk.com...
> I have a startup slowness issue when the users a pulling a license from
> the license server. If they borrow a license we do not have a slowness.
> I have done other troubleshooting and can not find the cause so I would
> like to build a new license server (the old one is over 6 years old the
> nic older), using 2009, then if everything goes fine when I deploy 2009
> they will have a new license server. The thing is I will not be deploying
> 2009 until close to the end of the year. Will I be able to run both
> servers for that length of time, until I get the company upgraded?
>
> Here is how I want to do this:
> Build new license server.
> Install 2009 on one PC testing speed of startup.
> Once the users are ready (after the busy season), upgrade the rest of the
> machines to 2009.
> Take down the old license server.
>
> Again the entire process could take several months as they never allow an
> upgrade until frost. Which in ND usually comes around Nov, Dec.

[elsiels]

If I use DNS to point the current name to the new server I shouldn't have to configure the clients to look at the new machine then.

[TravisNave]

This is true, or even use a hosts file redirect. But it takes literally minimal effort to point them to the new host. You can create a System Environment Variable, edit the LICPATH.LIC, or even create a registry key. You can script any of these. Worst case, the software will just ask for the new server.

You could have the new NLM up and running in minutes and be ready to push your licenses right now. And all transparent to your users at that!

[foruma000294]

I encounter similar issue and need to clarify that if I have a 2009 network license , let say 5 network license. Can the 2006, 2007, 2008 and 2009 client get license from the 2009 server.

Any document support this feature from AutoCAD.

Many thanks.

Raymond

[Anonymous]

http://blog.jtbworld.com/2008/04/package-license-file-introduced-with.html

--
Jimmy Bergmark - Owner/Developer
JTB World - Software development and consulting
Website: http://www.jtbworld.com
Blog: http://blog.jtbworld.com

JTB FlexReport (FLEXnet / FLEXlm license report tool) -
www.jtbworld.com/jtbflexreport

AutoCAD 2009
http://www.jtbworld.com/autocad2009.htm

wrote in message
news:6001663@discussion.autodesk.com...
> I encounter similar issue and need to clarify that if I have a 2009
> network license , let say 5 network license. Can the 2006, 2007, 2008 and
> 2009 client get license from the 2009 server.
>
> Any document support this feature from AutoCAD.
>
> Many thanks.
>
> Raymond

[TravisNave]

Yes. But only if the network license is under subscription and your license file includes the PACKAGE increment. This will allow you to run your current license and up to 3 versions back at the total maximum number of licenses. In your example, five total max.

http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=11067735&linkID=9240617