AdskLicensing-installer.exe unattended install

[MartinFortCeps]

Hi,

Unatteded instation AdskLicensing-installer fail under system account on Windows LTSB. The process AdskLicensing-installer.exe never end. Manual install is right.

Do you anyone help me?

I try to install under system account:
AdskLicensing-installer.exe --mode unattended --unattendedmodeui none - this is a command from script file for SCCM

[natasha.l]

Hello @MartinFortCeps, 

You mention that the install is being conducted by a SCCM script. 

Please make sure the Autodesk deployment was created successfully, try testing it on a local computer. Also take a look at our Best Practices for creating a Autodesk deployment. We also provide a SCCM Guide with step by step suggestions, if you require more assistance with SCCM contact Microsoft. 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[MartinFortCeps]

This is in SCCM script:

"Img\x86\AdskLicensing\AdskLicensing-installer.exe --mode unattended --unattendedmodeui none"

But this command works only if I log to pc as account with Admin rights. If I run this command under the System account it doesn't works.

I was try this:

1. run CMD.exe as a Administrator

2. run psexec under System account: PsExec.exe -accepteula -s cmd.exe

3. run AdskLicensinsing Img\x86\AdskLicensing\AdskLicensing-installer.exe --mode unattended --unattendedmodeui none

[MartinFortCeps]

AdskLicensing installer log file from Windows\temp

[mokHNFVB]

i have similar issue. How did you solve this ? I have tried 9.4.0.2899 of adsklicensing-installer.exe - if keeps hanging during SCCM deployment under SYSTEM

[grundey]

We are having the same issue.  AdskLicensing-installer.exe hangs if it is deployed with SCCM as "required" and runs as System.  If deployed as voluntary and a user initiates the SCCM install, it works but that is not a practical solution...

Autodesk, is there a solution to deploying this as a required install in SCCM?

[natasha.l]

Hello @grundey, 

Before using SCCM & a Autodesk software deployment. Please make sure to test the Autodesk deployment first on a local computer. After verifying that it works on the local computer only then should you include it in the SCCM package. 

If the Autodesk deployment works its an issue with SCCM which would mean Microsoft would need to provide further support on this. 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[grundey]

@natasha.l  The issue is specifically with AdskLicensing-installer.exe, thus an AutoCAD deployment is not even relevant to this discussion.  Given that AutoDesk specifically has instructions on how to deploy their products with SCCM, I'm hopeful that your installation group actually has SCCM and the ability to test deploying this app as a mandatory install and can then properly diagnose the issue for either a fix in a new AdskLicensing-installer.exe, or supplying the needed root cause to Microsoft and also suitable workaround for AutoDesk's customers who are currently stuck trying to deploy the Autodesk 2020 products.

[natasha.l]

Hello @grundey, 

The suggestions & links to best practices provided are supposed to help you discover on a micro level what the issue is, it could be as silly as the required Admin permissions to install & run Autodesk software. 

If you have Enterprise Priority Support with us they can specifically help you with SCCM. The SCCM guidelines provided by Autodesk come from the Enterprise Priority Support team, they have access to SCCM. 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Jean-Michel.Lemieux]

I've got the same probleme as you with the AdskLicensing-installer.exe application in SCCM. My only workaround for now is to run the SCCM application with "Install for user" and "Only when a user is logged on" in the User experience. But, with this configuration, I cannot use the application throught a Task Sequence. The application doesn't like to be pushed by the SYSTEM account. Any fix so far?!

[cspicer]

I ran into this same issue when trying to deploy AutoCAD 2020 with SCCM. The install would work fine if I ran it interactively through Software Center, but would hang up and eventually time out when run during OS Deployment or when deployed as a required app. Others here are correct, it really has nothing to do with SCCM itself. The problem is with AdskLicensing-installer.exe. If run in any unattended context, that install will hang up at the following step:

Executing cmd /C mklink /D "C:\Program Files (x86)\Common Files/Autodesk Shared/AdskLicensing/Current" "C:\Program Files (x86)\Common Files/Autodesk Shared/AdskLicensing/9.0.1.1462"

After Googling around a bunch, I see there is a general issue with running the mklink command from the System context, which is why this is hanging up. So, I pulled up c:\windows\temp\AdskLicensing-install.log from a successful interactive install, and rolled my own Adsklicensing setup. This involved the following:

1 - From a successful install, I zipped up the following three directories and made them part of my SCCM package content: 

C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing

C:\Program Files (x86)\Common Files\Autodesk Shared\Adlm\R17

C:\ProgramData\autodesk\Adlm

2 - In my SCCM install batch file, I added steps to extract the contents of those three zip files and copy them to the same paths

3 - I located the sc.exe commands that are listed in AdskLicensing-intall.log, and added those same commands to my batch script to manually create the service

That finally did the trick, because my script was able to create the service without using the mklink command that is failing on the "real" service installer. I've attached my install script in case it helps, it would be great if Autodesk can update the Licensing Service installer to either get rid of the mklink command or work around this known behavior.

[Hotter_R]

Hi @cspicer ,

the version 9.0.1.1462 is from 2019. So please download the latest version 10.1.1.66 from here or download the latest AutoCAD 2020 installer from your Autodesk Account.

This should help fixing your issues and you don't need to do the trick. 

[dorian.prospero]

I am having this same issue with the current 11.0.0.4854. Has autocad still not fixed this bug? Everything that was noted by several users in this thread is still an issue today a 1.5 years later. cspicer seems like he has a working 'hack' to force the app into compliance but it seems stange that autodesk has yet to address this seeming basic issue of using a command that is not supported in a system context. I am hoping from a responce from @Hotter_R  or other autodesk support on the progress of a fix for this issue.

[dorian.prospero]

Hmm ok it looks like its working now. spoke too soon i guess. been having the same posted issue for 2 days and it mysteriously went away.