2018 Inventor HSM Deployment

[Anonymous]

I am trying to create a silent deployment for 2018 Inventor HSM.  I have tried both from the product page of the Autodesk site and from the virtual agent.  The deployment looks like it creates normally, but when I launch it on a client machine, the Autodesk self-extractor launches (see attached screen grab).  If I cancel that, it seems to load fine.  If I turn off the silent mode, the self-extractor also launches.  How can I create a deployment where the self-extractor does not launch?  I have posted this in the Installation and Licensing Forum, but it was suggested I post here to see if anyone else is struggling with this.

[Tianq]

@Anonymous it does not pop up the dialog when I run the deployment file created through setup.exe. Can you share the deployment files?

And you can also refer to this thread to create a silent install - https://forums.autodesk.com/t5/hsm-support-forum/hsm-2018-silent-install/m-p/7091176#M18116

[Anonymous]

Hi,

Has a resolution been found to this as I am also trying to achieve the same outcome of a silent deployment with the licence already activated.

I have followed the steps provided by Dave (Qing) Tian from the linked forum post but this runs through but doesn't actually install HSMWorks.  I've also noticed that when I create a deployment using the supplied tool, I am not prompted for licence details (unlike other Autodesk deployments) and that the Product Key is different to the one I've been supplied.  I am, however, prompted to enter my licence server on launch, which is not acceptable.

This is starting to seem like a flawed package.

Rob

[Anonymous]

Thanks, Dave.  I just tried to create the deployment from the setup.exe file, and it looks like I am getting the same result when I use it to install on a client workstation.  Most of the way through the install, the Autodesk Self-Extract utility launches and I have to cancel out in order for the install to complete.

[Anonymous]

Hi, Rob.  Sorry I have no resolution yet.  It looks like the issue you are having is a bit different with HSMWorks, but it sure looks like there is a problem with the download package in both cases.  Hopefully someone at Autodesk will try to recreate our issues - mine is pretty simple to recreate and does not take much time to do so.

[jeff.pek]

What is in the self-extracting archive? I'm not aware that the deployment creation process should produce anything that needs extraction.

  Jeff

[jeff.pek]

I just tried this myself, and it worked fine. I created a "silent install" deployment. It installed fine, without any extra extraction prompts.

Not sure what you guys are seeing, or why.

Jeff

[Anonymous]

If I hit OK, it creates a folder identical to the one created when I run the file downloaded from the virtual agent.

[jeff.pek]

Hi -

If you hit OK when? Any chance you can capture a screencast of the process of creating and running the deployment?

Thanks,

  Jeff

[Anonymous]

Jeff,

Wow.  I am really puzzled.  Are you getting your initial download from the virtual agent?  I even updated my deployment with the latest patch, but same result.  

[Anonymous]

Jeff,

Yes, good idea.  I will do that an post it in a bit.

[jeff.pek]

I'm not sure what "virtual agent" you're talking about -- I worked from a download manager-initiated directory, in c:\autodesk.

  Jeff

[Tianq]

Hi Rob,

I have added the scripts to silent install inventor HSM in that thread. The one to support standard alone license is shown as below.

For Standard alone license:

C:\AppInstalls\InventorHSM\setup.exe /t /qb /language en-us /c InventorHSM: PRODUCTEDITION=INHSMP ACADSERIALPREFIX= <SerialPrefix> ACADSERIALNUMBER= <SerialPostfix> ADLM_PRODKEY=<ProdKey>

Note: "c:\AppInstalls\InventorHSM\" is the installation folder path of Inventor HSM in your disk.

Sorry that the deployment tool does not include license details. The issue is tracked with CAM-7760.

Dave

[Anonymous]

Jeff,

See attached screencast.

http://autode.sk/2taHR51

[jeff.pek]

Thanks. We'll take a look.

One thing I notice: The builds available in Virtual Manager are not current.

I would focus on the builds available in the Account Portal (under Updates).

That said, I don't think we've fixed anything here, and we are also able to use deployments created from the build that's in VM.

Jeff

[jeff.pek · Accepted solution]

OK. I think I know what is happening. The key step is the "Add Updates".

For Inventor HSM, our updates are full installs, which use the Download Manager (self-extracting archive) technology.

When you added the update it just downloaded the self-extracting EXE, and then set it up to be run during (after) the install.

This is where the extra prompt comes from.

Since each update is self-contained, you don't need to add any updates to it -- just make a deployment of the latest build,and use that.

Jeff

[Anonymous]

Yes, that was the problem.  You may want to consider removing the Add Updates button at the bottom of the last screen so this doesnt happen.  Thanks for your help!

[jeff.pek]

Yes, good idea. I'm not sure we have control over that, but perhaps @tianq can figure that out.

Good you're going again.

Jeff