Microsoft Server 2012 & LMTOOLS v11.10

Since I had some downtime from the storm, I spent some time working with Windows Server 2012 and I have to admit, it’s pretty neat! I’ve configured the first license server in my virtual lab (using Oracle Virtual Box)  to serve up some Autodesk products without any issues. Interface to the server is neat and clean, and performance has been impressive. I’m planning to set up a virtual domain and will keep everyone posted on how it all works out!

Advertisements

LMTOOLS download

Some clients are down from the storm and have to rebuild their license servers after Hurricane Sandy. If you need the Network License Server Tools for Autodesk 2012 products, the links are below.

Most of you are using IPv4. These are the links you’ll need:

License files are generated directly by Autodesk. If you have your serial number, server name, and MAC address, you’re ready to contact Autodesk. There are two ways to do this:

  1. Go to “register.autodesk.com“, log in, and you can generate the license files automatically.
  2. You can also call Autodesk Activations at 1-800-551-1490 to speak to an Autodesk rep to get a license file.

If you run into any issues at all, do not hesitate to contact us. Our support group is up and running and ready to help!

Apply Update Release 1 to your Revit Architecture 2013 Deployments

Got a follow up video for those you responsible for making deployments in your office. Since the original  deployment was made, Autodesk has release Update Release 1; we’re going to add that update to your deployment image. We’re also going to change two file locations, the Revit Project Data path and the IES file location.

There are two reasons for this change. If you want worksharing to work properly, the folder needs to be write-able for users. Since my DFS location is locked down and I don’t want to bother with permissions and blocking inheritance, I’m going to repath it to the local workstation. The second reason is that you will always have a local copy of the Revit model you’re working on (in case the server falls off the cliff).

Hope the video helps in your deployment needs. If you have questions, feel free to leave comments in the video and I’ll answer them there. Thanks! 

V-Ray licensing is NOT the same as Autodesk!

So I got a few questions on this recently, especially from those who moved their own v-ray licenses to the new dongle based licenses from Chaos Group. I made a video on this here, but there’s some pointers to keep in mind:

1) On the server, you want to make sure the V-Ray Licensing components are setup to run on boot up, namely, to run as a service. You do this by going to the START MENU –> ALL PROGRAM –> Chaos Group –> V-Ray for _____ –> Licensing –> Administration –> Register V-Ray license service. This creates a service call VRLService on the server. You need to be an Administrator to do this. If not, you’ll get an error “VRL Service”: “Failed to open registry key”.

2) To specify which server to pick up the licenses, go to START MENU –> ALL PROGRAM –> Chaos Group –> V-Ray for _____ –> Licensing –> Administration –> Chagne V-Ray client license. This dialogue window will pop up; on the primary license server, type in the license server. You can also use IP address (as you see in the screenshot).

Deploying AutoCAD 2013 via Group Policy

I initially created a group policy as I’ve always done. Set package installation paths, point to the MSIs. Seems like that didn’t work too well. After a gpupdate /force, the workstation will look like it’s installing the software but when you log in and actually try to install it, you’ll get this errror with ACCORE.DLL crashing.

After looking through a lot of different discussions boards and PDF white papers and going through a few trial runs in our lab, AutoCAD 2013 is now installed in my training rooms, pushed automatically via OU association with Group Policy. It was a little bit of a hassle to figure out the various MSI and MST files needed for successful GPO push, but alas, all is well in the universe again 

Source: Autodesk Wiki Page on GPO deployment

Deploying 3ds Max Design 2013 – GPO Errors

Confirmed my licenses for 3ds max design 2013, and packaged the deployment in my DFS – no errors or failures. The next step was to deploy the software! My philosphy is always to automate as much as possible so I decided to use Group Policy to push the software out. Initially done on my lab, I then applied the GPO to one of my training rooms. EPIC FAILURE! Here’s the error message from the workstation:

Event ID 10005

Product: Autodesk 3ds Max Design 2013 64-bit — 1: 5 2: adlmPITSetProductInformation failed. 3:26

I searched for the solution, including renaming the .pit file from the Program Data directory but it didn’t work! I’ve been working on finding a solution for this so my GPO will push but nothing seems to work! Sounds like I’ll have to start a case with Autodesk! 😦

Beam me back to the network please! [the 2013 version]

I’ve said it before, and I’ll say it again… You can beam yourself back after you left Starship Enterprise. Okay, I’m not talking about Captain Kirk here, but rather users who disconnected from their offices and left for some sunny location to “work” and subsequently converted their licenses to standalone. Now that they’re back to reality and need to be back onto network seats, a quick and easy change in the registry will fix do the trick!

HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R19.0\ACAD-xxxx\AdLM

Civil3d-2013-reg

NOTE:  The value ACAD-xxxx may change depending on your AutoCAD vertical.  The example above is for AutoCAD Civil 3D 2013.

In that directory change the type for the installation that you require to edit Type:
1 – Network
2 – Standalone
3 – Multiseat Standalone

Revit Server 2013 – Revit model collaboration across LAN / WAN

First with 2011, Revit Server is now in it’s third year and I’m here again showing you how to set it up in your office. Understand the concepts, and then get the servers ready by installing any prerequisites. When you’re planned out and ready to go,  installing Revit Server 2013 in your network and configure your workstations! True Revit model collaboration across a LAN / WAN. Yes, it’s awesome 

Creating Deployments of Autodesk Revit Architecture 2013 / DFS / Centralized content

With every release comes a new deployment image so I thought it might be helpful for IT/CAD/BIM managers to see it done first. I’ll be making a deployment image for Revit Architecture 2013 on my Microsol Resources DFS, configuring the deployment image using central location for all templates and content. This way, all my users / Application Engineers (AE) / Support Personal / Trainers & Instructors will all get centralized content. This is especially good for larger firms since standardization is one of the keys to an efficient production environment.

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!