SPAM or SCAM? I’m the network engineer for my firm and recently, I’ve been informed that Barracuda has black listed our IP. A fairly large customer found out when he’s stopped getting our invoices! No invoices means not getting paid. NEVER A GOOD THING! Continue reading
We have an ancient Citrix Access Gateway, version: 5.0.4 .223500, 2011-12-14. Guess who gets to upgrade and make it modern! ME! WHOOHOO! 🙂 Continue reading
Latest news!!! SHA1 is now considered insecure! Well, only theoretically insecure for the time being (as of Jan, 2016), but very soon, the keys will be broken! We actually
have had a SHA1 certificate being used by Citrix Access Gateway (version: 5.0.4 .223500, 2011-12-14). AND we were using RC4. Two issues that keep growing in importance. First problems started early 2016, when our site wouldn’t work with Chrome and kept throwing up errors in Firefox. Continue reading
Showing you what I did on a recent project with a client – moving license servers on a few hundred workstations automatically! Very useful when migrating servers or retiring servers, or even making sure workstation have a backup license server in the cloud. Using Group Policy, we make an environment variable on workstation listed on a specific OU. The environment variable will direct workstation to point the Autodesk software to point to the new server.
Autodesk Revit Server, in it’s 3rd gen, improves upon previous versions and allows users within an organization across multiple locations to simultaneously collaborate on Revit workshared projects. I’m going to explain what’s new in Revit Server 2014 and also show you how to set it up in your office. Understand the concepts, and then get the servers ready by installing any prerequisites. It might sound obvious, but before implementing Revit Server in your office, it’s highly recommended to do some planning and draw it out logically how you want / expect it to work. You don’t want to make a bunch of Revit Servers floating around your network and cluttering your VM.
For our awesome clients who have more than 120 seats of McNeel’s Rhino, there is a new build! Released on Jan 15, the new build of Zoo 5 fixes that error when you try to manage the Zoo licenses but aren’t able to because of the error “There was a problem communicating with the service” and none of the licenses show up.
Even after checking the service and reinstalling, it still fails! How frustrating! Thankfully it’s been resolved, and quite quickly too! Click on the link and install on the same machine. The previously registered licenses are retained (whew!) and everything will be quiet in the Zoo once again and you get back to creating some awesome geometry in Rhino!
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!
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:
- Go to “register.autodesk.com“, log in, and you can generate the license files automatically.
- 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!
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).
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).