Network Licensing fails for AutoCAD 2023 when using a Network License and Custom Install package

[UniSA-SoftwareLicensing]

Hello All,

We have built Custom Install packages using our Portal for all the 2023 versions of our products.

We have updated our Network License Manager to the latest version for Windows Servers (NLM 11.18.0.0).

When we package our Custom installs we define our License Server in the process and customize the Autodesk path to allow for our Shared Machine environment thus avoiding User Profile content having to be moved.

When we deploy the AutoCAD 2023 package, we receive errors 2 or 0000 indicating that their is an internal programming error or that the Desktop Licensing Service is incompatible with the License Manager version.

I can get around this to a certain degree by installing a standard AutoCAD installation in silent mode, licensing the desktop manually using version 12.x.x of the ADSKLicensing-Installer. I cannot do this via the package as it does not allow me to customize the embedded ADSKLicensing binaries in the Custom package. 

Installing the product silently (Setup.exe -q), then installing the ADSKLicensing 12.x.x binaries and then patching in the Registry entries to redirect the support files to an alternative location, then patching in the License Manager address is somewhat complicated when all we really need is an ADSK client and Server that will actually talk to one another. 

Does anyone have any suggestions for modifying a Custom Install package to allow for the lesser version of the ADSK Licensing client  to be incorporated into the deployment via the Installer.exe (Content.xml) combination?

[UniSA-SoftwareLicensing]

Hello All,

We have built Custom Install packages using our Portal for all the 2023 versions of our products.

We have updated our Network License Manager to the latest version for Windows Servers (NLM 11.18.0.0).

When we package our Custom installs we define our License Server in the process and customize the Autodesk path to allow for our Shared Machine environment thus avoiding User Profile content having to be moved.

When we deploy the AutoCAD 2023 package, we receive errors 2 or 0000 indicating that their is an internal programming error or that the Desktop Licensing Service is incompatible with the License Manager version.

I can get around this to a certain degree by installing a standard AutoCAD installation in silent mode, licensing the desktop manually using version 12.x.x of the ADSKLicensing-Installer. I cannot do this via the package as it does not allow me to customize the embedded ADSKLicensing binaries in the Custom package. 

Installing the product silently (Setup.exe -q), then installing the ADSKLicensing 12.x.x binaries and then patching in the Registry entries to redirect the support files to an alternative location, then patching in the License Manager address is somewhat complicated when all we really need is an ADSK client and Server that will actually talk to one another. 

Does anyone have any suggestions for modifying a Custom Install package to allow for the lesser version of the ADSK Licensing client  to be incorporated into the deployment via the Installer.exe (Content.xml) combination?

[RobDraw]

You're better off in the Licensing and Installation forum. You can report your own post and ask for it to be moved.

[UniSA-SoftwareLicensing]

Solved this myself.

Appears that the permissions on the file ProductInformation.pit are set so that no one other than SYSTEM can READ it. This causes the ADSL License Service to throw an error.

Using a Deployment tool such as SCCM/MECM and as part of the scripted install, Take Ownership as Administrators and then use icacls to restore the permissions allows the product to read this file and then communicate with the License Manager server. 

AutoCAD installer is the only one that seems to do this. Others packaged similarly do not behave in this manner.