Installatoin hangs at adsklicensing-installer.exe

[licensingX4M2F]

I created a deployment for Revit, Inventor and Autocad. installing during OSD with SCCM. It appears to hang at adsklicensing-installer.exe.  The install log for the .exe is never created so i have no way to post it. If i end the task in taskmgr during OSD it will continue to install the program. and the other Auto-desk programs as well with no issue.  It only does this on what ever the first auto desk program that is ran in the task sequence. I have tried to change the order of installation but it does the same thing. 

Again i would post a log but no log is being created. 

Windows 10 1809

Autodesk 2020

any ideas?

EDIT:

Just tried again this time after ending task it failed the installation of the program. and it didnt install.  I guess its random but it seems to link back to adsklicensing-installer.exe

[EduITAdm]

Yep, would be interested to know if you make the application AVAILABLE and open Software Center and select it and install it, does it still hang or does that work OK? I forgot which behavior I was seeing but it definitely still hung if made required. Because as you noted, even though a newer version of the license service is already installed, the autocad (or whatever app) installer still runs it and it still hangs. So **** frustrating! I just ended up thick imaging AutoDesk apps into all my labs. Hoping it behaves better next go around.

[latkid]

Try this......without deploying your software, install the ADSK licensing software. then open task manager, open the services tab, and check to see if the service is actually running.

[latkid]

My apps for Autodesk are all required. No issue with installation as long as the license service is running. Definitely a strange issue for you.

[EduITAdm]

Yep, after extensive testing for me, I would...

1. Deploy latest license manager and reboot after successful installation.

2. Deploy AutoCAD2020.

I would watch the installation proceed via ProcessExplorer. It would install all the prerequisites, get to the license manger installer and just hang. Even though the license manager was installed and the service was running. Would do this every time if setup.exe was called by configmanager. If I ran it myself, it would install just fine.

[nguyenndSQN7Y]

ok, I am gonna do some tests for both required and available and will let you know how it turns out. As you said, this is extremely frustrating. We have many labs at our school and have sccm deploy autodesk as required is a must.

[latkid]

Next Question, how do you build your installation packages for Autodesk for SCCM? I use the installer and build a package for SCCM. I then use a .bat file with a script to run it. I found this information at autodesk.

[EduITAdm]

Good luck! And please keep us posted with your results..

I am lucky to also have PowerBroker for Windows here for Faculty/Staff, so I can leverage that for faculty to be able to self install the AutoDesk apps from a file share. Like I said, I just built AutoDesk into the base images for the labs to quickly get around this for the 2019/2020 Academic year. Ill be at this again come summer and the latest app releases. I am really hoping for better results then...

Did I mention that this is ONLY a Windows 10 issue???  All of these worked without issue when deployed to Windows 7, 100% of the time....

[nguyenndSQN7Y]

Same as you. I created a deployment, then use batch file to run the install.

[CTSLicensing]

Wow! this thing is getting more messed up than I thought. I created a stand-alone application for ADSK and deployed it to 2 different collections, one as available and the other one as required. Both installation method failed in different computer in different collections. Failed with the same message, pretty much saying that the ccmcache is full, even though it's not. It's completely empty, and I made sure by delete files using config mgr.

Maybe one of the posts in here was right, adsk-licensing HATES app. I'll try to create a package next and give that a try. If the package works, that means I won't be able to use it as dependency since it only works with application. One problem at a time I guess.... to be continue

[latkid]

Ok lets address your CCMCACHE. I also have a package that's deployed during OSD that raises the default cache size for programs from 5120 to 40000. I'll post a text document that has the information here as well. Large programs will not even download for installation without this modification. The text file we have set as .vbs file.

[nguyenndSQN7Y]

we have our default cache size at 25000, that should be more than enough, especially I am only trying to deploy adsk by itself and not as dependency with Autocad.

The license installer you guys using is version 9.2.2.2501 right? I saw a newer version but the description indicated that version is for single-user license.

[Mark.Lancaster]

@nguyenndSQN7Y 

The new version Autodesk Licensing Services - 9.6.0.41 is for all subscription based license, single or network.   Not just for sign in.

However there's reports that some people are having issues and I would recommend right now not to apply that new version that was just released a couple of days ago.

[nguyenndSQN7Y]

right after my post, I double check my deployment and realized what I did. My mistake, this is what happens when you try to create package on lack of sleep.

Instead of putting the license installer in its own directory/folder, I had the installer in the same/root directory as other Autodesk suites, which means when I was thinking of pulling down the installer, it would pull down EVERYTHING, which is why software center was protesting with not enough space.

After I made the change, the installer installed fine as required as application.

[latkid]

YES!!

[nguyenndSQN7Y]

So my deployment of Autocad failed for both available and required.

The Autodesk license installer installed as a stand-alone or as dependency.

I tested both way, installed it as stand-alone and dependency, its service was running (please see attached screenshot), and the deployment still failed.

Just so you know the steps I took, I created the deployment, zipped it up, then use batch file to extract it to c:\windows\temp, cd to the extracted directory and run the command: start /wait .\Img\Setup.exe /W /Q /I Img\Autocad2020.ini /language en-us

Again, service for adsk license was running at the time. 

Did you modify the autocad.ini file to prevent the adsk installer in the deployment package from running? 

[latkid]

This is the text information I used for my .bat file

"%~dp0Img\setup.exe" /W /q /I Img\Inventor 2020.ini /language en-us

I got this from a great sight for deployment of Autodesk products.

[nguyenndSQN7Y]

you gave me an idea and I took a look. You're not gonna believe this, when I created the deployment the first time, the command from the deployment package is: .\Img\Setup.exe /W /q /I Img\AutoCAD2020.ini /language en-us

the package I just made for these tests, the command is: .\Img\Setup.exe /W /q /I Img\AutoCAD.ini /language en-us

the command for the package changed from Img\AutoCAD2020.ini to AutoCAD.ini

No idea why it was changed... gonna update the content and try again...

[latkid]

Good luck. As I have progressed through the newer versions I keep the same .bat file and just change the version number 😀

[nguyenndSQN7Y]

YES!!! Success!!

Wow! I have built a whole bunch of applications but never had to fight to deploy a package like this one.

Thank you and Semert very much for your help! I really appreciate it!

TGIF and it ended on a good note. 

[g.taylor83BD8]

I've also run into this issue while deploying AutoDesk's 2020 applications. I tried all of the suggested fixes on here however the only one that worked was to break out the AutoDesk Licensing Service and deploy as a package. None of the application based installations worked when deployed as required. After the AutoDesk Licensing Service was installed the remaining Autodesk applications installed perfectly. This is a very frustrating issue when you have hundreds of computers that require Autodesk software. Thanks to everyone in this thread for your contribution.