FlexLM on Windows Server 2008 R2 virtual machine for Autodesk 2013 & 2012 products

Got Windows Server 2008 R2? Got virtualization plans? If so, check out the latest video. You can install FlexLM on guests running on Hyper-V or VMware. For this video, I’m going to be installing FlexLM using VMware Workstation, with a Windows Server 2008 R2 guest. It’s always recommended to ‘hard code’ your virtual guests’ MAC address so it doesn’t change. Complete setup and configuration in just over 6 minutes to get your license servers up and running, and your users back to work.

Here are the steps in case you feel like reading and not watching my awesome video:

  1. Load the latest FlexLM on the media of 2013 software. You should be using 11.10.xxxx. Should look similar to:
  2. On the Autocad install DVD (or any other installation DVD)  or the extracted EXE file, the path for FlexLM is named NLM.msi, under folder: C:\Autodesk\AutoCAD_2013_English_Win_64bit\x64\en-US\Tools\NLM\
  3. Note down the existing settings onto notepad and copy the files (especially the license file) off to a backup directory.  You do not want to mess up and delete your license file!!!!
  4. Remove the old version via “Programs and Features” in Control Panel.  You can also stop the service manually and do an “in place” installation.
  5. Click on the MSI file and follow the installation wizard. It’s as simple as clicking next a bunch of times.
  6. Once it’s installed, make sure the initial check box, “LMTOOLS ignores license file path environment variables” is checked. To configure as service, go to the CONFIG SERVICES tab and point/browse to those locations for LMGRD, LICENSE FILE, DEBUG FILE (you have to get the license file from Autodesk and create a debug.log file manually). Make sure the two check boxes are checked and click on SAVE SERVICE.
  7. Go to the Start/Stop/Reread tab and click on the Start Server button.
  8. Once the status shows Server Start Successful, go to the Server Status tab and click on the Perform Status Enquiry button.
  9. VOILA! You’ll see all the licenses available to you in the status window!

V-Ray dongle based floating license – installation & configuration

It hasn’t been long since we’ve partnered up with Chaos Group to offer V-Ray and my-oh-my, there has been a lot of interest!

One of the common questions I get is about those pretty blue dongles. We’re all used to setting up FlexLM to manage licenses, but all Chaos Groups’ V-Ray licenses are managed by a USB dongle. So how does it work, how will my network be affected, how will our firms’ licenses be managed? Well, here’s a quick little video that demonstrates how to install the license server and then making sure the dongle is [properly] read by the workstation (I’m using a Windows 7, 64bit machine for our licenses). It’s not as easy as just sticking the USB in so before you jump in, it’ll be good to check the video out. 

Automate ALL the things!

Just came back from a client visit and the project this time was helping to upgrade their license server. Pretty straight forward stuff, but I’ve come to realize that what I do as “straight forward” is actually pretty impressive to quite a few people.

We all know [at least you should if you follow my blog] that there are three spots that Autodesk uses to define where the license servers are.

  • Environment variables
  • Registry Entries
  • LICPATH.LIC

These are read that in that order, and when the system finds the key (ADSK_LICENSE_FILE), it will stop and put it to memory. So how does it affect my deployment? Well, if you have a license server (let’s call it OldLic1 and OldLic2) already serving up licenses and you want to upgrade/retire it and move licenses to your new, awesomely robust virtual server (NewLic1 and NewLic2), most people think you need to touch every workstation to update those values so that AutoCAD and Revit will get license from the right servers. NOT!

With the all-powerful Group Policy Management Editor and some nifty GPOs, you can make the change to all your workstations to all your branches… at once. Yes, we did this to well over a thousand machines for this project, even to their branches, WITHOUT having to touch every single machine. Thank goodness too, cuz I would’ve gone crazy!

Wait,… what? What GPOs do I need, you ask? I dropped enough clues; I’ll let your IT group figure that one out 

Follow

Get every new post delivered to your Inbox.

Join 82 other followers