Initially, I was going to do this in great detail. But that’s actually very inefficient. So, I’m going to keep this short and provide links where needed. Enjoy!
1. Build a Deployment Share
Download and extract the installer package. Launch setup.exe and select the option to build a new Deployment Share.
2. Prepare Scripts or go As-Is
Use the provided sample scripts which are created under the new Deployment Share location in the “SMS_SCCM Scripts” folder, or, if you prefer, make your own script.
Basically, you’re going to copy the instructions in the deployment shortcut and add some minor tweaks. In the target field which contains the actual instruction, you will need to have your script run the same statement but with a minor change. Where it shows “/qb /I”, change it to “/q /I /W”. Leave the rest of as-is.
In my example, the deployment share is on server FS100 under a hidden share named “deploy$”. Below that is a root folder named “ADSK” and I created a folder named “IDS2015P” to create the actual deployment tree. The deployment itself is also named “IDS2015P” for Autodesk Infrastructure Design Suite Premium 2015″. Example statement…
\\FS100\deploy$\ADSK\IDS2015P\Img\Setup.exe /q /I /W \\FS100\deploy$\ADSK\IDS2015P\Img\IDS2015P.ini /language en-us
Pretty straightforward. But keep in mind there’s a limit on how long the entire statement (string value) can be. If you make it too long, it will abort with an error telling you so.
TIP: Keep the overall UNC path strings as short as possible. Use abbreviated names for shares and folders wherever possible and avoid embedding spaces in path strings.
Test everything until it’s good and ready.
3. Prepare the SCCM Deployment
Create a new SCCM Application object and specify all the attributes, requirements, conditions, etc. Be careful to consider the fixed-source aspects of an Autodesk deployment with regards to how you configure Distribution Points for your application object. For more on this topic, go here, or go here.
You can use a script instead of referencing the original files if you prefer that over SCCM conditions. If you spend a little time creating some helpful Global Conditions in SCCM you can piece together some fantastic solutions without scripting anything. You can handle all sorts of aspects from minimum hardware requirements, disk space, and computer model types, to Windows Features (.NET 3.5, etc.) and so on. For more on SCCM Global Conditions, go here.
4. Obtaining a New License File
Get the MAC and NetBIOS name of your FlexNet license server. Once you have the MAC and NetBIOS name, you can submit a request online through your Autodesk subscription web site. For more detail on this go here.
TIP: You can use the Windows GETMAC command from within a CMD console to query the MAC identification number for any Windows computer. It works locally or with remote computers as well.
Assuming you submitted the correct information and your licensing is in order, Autodesk will provide you with a license file.
5. Updating the License Server
If you have an existing FlexNet service in place and are simply updating it, it’s really easy. You open the existing license file, paste in the new authorization code that Autodesk sends you, save and close the file. Open the LMTools utility and click “Re-Read License File” and that’s it. Always verify the results by clicking the “Server Status” tab and clicking “Perform Status Enquiry”.
If you don’t have a FlexNet service in use, you will need to configure one using your new license file. For a great walk-through on this, go here.
If you have FlexNet Manager or FlexNet publisher, you can use that to update license services as well. For more information, go here.