When deploying AutoCAD products with KACE we found that they're simply too large to upload into the system. We also had a hard time with creating a deployment and then trying to move it to other locations. Even if we broke it open and made the changes it never worked quite right. So in the end we found a solution that works well for us.

1. We created a network share that everyone in the company has read and execute access to. That's where we store all the completed deployments.

2. Created an install.bat file that pointed to the deployment link on the share. We then uploaded the install.bat file to KACE as the deployment. We also did something similar in SharePoint where we have a Software Automation page that the IT group can pull up on any computer and start the deployment from there. But with KACE we were able to have it run some scripts afterwards.

For example, in our remote offices they need a special environmental variable created to make the system wait a certain time while trying to contact our licensing server. When run through KACE at that office we've got it set to run a script afterwards that creates the environment variable.

So far the data share has been very effective in addressing the issues we had experienced in getting the deployment to the users.

Since it was requested, the way we use the install.bat is by putting in the path to the lnk file where the deployment was created on a storage server. The new K1000 5.4 can supposedly unzip packages as large as an autocad deployment now, but we don't know if that's practical yet. So far this has worked for us.

If you need to you could even call the timeout vbs script in the install.bat as long as you zip them together for the K1000 to use.

\\<Server>\Apps\AutoCAD_Standard_2013_64bit\AutoCAD_2013_64bit.lnk

This script is to increase the timeout on our Branch Offices hitting out licensing server so that they can receive a network license. Save it as a .vbs

strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set objVariable = objWMIService.Get("Win32_Environment").SpawnInstance_

objVariable.Name = "FLEXLM_TIMEOUT"
objVariable.UserName = "<System>"
objVariable.VariableValue = "3000000"
objVariable.Put_

To suppress the Autodesk Privacy Statement dialog during first run:

• Generate the file by launching AutoCAD and accepting the agreement.
• Copy the file AdlmUserSettings.xml from C:\Users\%Username%\AppData\Local\Autodesk\adlm
• Add the file to your AutoCAD deployment. Make sure it gets installed to the same folder you pulled the file from. Modifying the MST generated by deployment the tool works. Make sure the user gets the file copied into his/hers profile during self-heal (first run) of the software.