Modifying a deployment created on manage.autodesk .com

[Nick_Hall]

Hi

I need to implement this change for a Vault Pro installation.

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-ensure-that...

In short, it requires changing a setting in one of the configuration files in the deployment.

However, this change must be made in the deployment—it can't be applied after the installation.

I can't find any documentation on the site about modifying the new-style deployments - can anyone point me in the right direction?

Any help gratefully received

Nick

[Simon_Weel]

The same way you created the deployment. Log in to your Autodesk account. In the left side column, click Custom install and your deployments will be listed to the right. Hover over the deployment to edit and select option Edit.

Select the program to edit, make your changes. Save the changes and download the installer. Run the installer to update your local deployment and you're done.

Mind you, this won't update installations you already performed.

[Nick_Hall]

Thanks, Simon

I've just tried that, but it doesn't allow me to modify the files in the deployment or execute any programs after a successful installation, which are the only ways I can think of to make the change I need.

It appears that what I want to do isn't available through the web interface.

Nick

[Simon_Weel · Accepted solution]

Ok, read the article. It's pretty straight-forward. You have to modify Connectivity.VaultPro.exe.config. Search the 'image' folder on the local deployment share for this file and make the modification.

For machines already installed, you have to change the same file.

[Nick_Hall]

Thanks again, Simon

I was hoping it would be something as simple as that, but as there’s no documentation I thought I’d ask before I tried

I’ve finished for the day, but I’ll give it a try tomorrow 

Nick

[Nick_Hall]

Hi @Simon_Weel 

I set up the deployment yesterday and ran the installation.

My initial tests failed, but that was caused by a pending reboot that I missed when checking the log.

So, it's up to the customer to see if this meets their stringent security requirements.

Thanks again for your help

Nick