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
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! 😦
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!
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
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
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.
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:
- Load the latest FlexLM on the media of 2013 software. You should be using 11.10.xxxx. Should look similar to:
- 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\
- 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!!!!
- Remove the old version via “Programs and Features” in Control Panel. You can also stop the service manually and do an “in place” installation.
- Click on the MSI file and follow the installation wizard. It’s as simple as clicking next a bunch of times.
- 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.
- Go to the Start/Stop/Reread tab and click on the Start Server button.
- Once the status shows Server Start Successful, go to the Server Status tab and click on the Perform Status Enquiry button.
- VOILA! You’ll see all the licenses available to you in the status window!
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.
X-rays are nice and all, but V-ray… V-ray breaks the barrier between what’s real and what’s in our imagination… wait, rather.. what’s beyond our imagination. We’re taking it to the next level of awesome cuz we’re now resellers of this amazing power! And… wow. We’re talking speed, precision, power, … power… wow, just holy moly wow. Take a look at their 2011 demo reel for some awesomeness. The official ‘press release’ is here, but I’m sure you’re more interested in what v-ray is capable of. Check it out:
I get a common question on how to make users from multiple offices share the same drawings seamlessly. They want to be able to work on files stored in New York while working from Seattle just as they were in the New York office. In the realm of WAN optimization, the biggest player is Riverbed Steelhead. Autodesk works directly with Riverbed and many firms already have it in place, but it’s important to know what actually happens.
The appliance takes data across the wire and caches it, sending only bits that haven’t been sent (incremental changes). The first 5MB file you send will take 1 minute (cold). If someone requests the same file later, that transfer will take 10-20 seconds (warm). The older DWG file format (2007 and older), along with older Autodesk software, does the full file swap when saving, negating any benefit from appliance.
- Change the “Incremental Save Percentage” (ISP) inside AutoCAD to 50.
- Use the 2010 DWG format!
- Why? The 2007 DWG format are not optimized. When you do every open/save, all the bits inside it are rearranged, data de-duplication technologies can’t recognize them, and the entire file looks new to Riverbed’s data hashing algorithms.
- 2007 is sooooo 2007. Last time I checked, it is not 2007 anymore.
Another interesting tidbit is that if you analyze the data from your Steelhead, besides AutoCAD files being optimized, a lot of the benefit comes from other things are being optimized. You’d be surprised how chatty software is.
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
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