Creating deployment using UNC

[Anonymous]

I have read many of the documents in the knowledge base, watched some youtube videos and they all state to use a UNC for the administrative image path location > yet when I put a UNC in the path as part of a deployment creation I get an error that \ is a character I can't use..  So I create the deployment to a local folder on the workstation I am creating the deployment from > then afterwards copy the deployment to my share > then modify the setup shortcut to use a UNC as well both ini files in the Img folder (section was global msi properties - I changed from a local folder to the UNC path to the deployment folder on the server.

I can right click on the setup link from a workstation and run as administrator and the install kicks off but the installation is stuck on 'Initializing' - did I create the deployment correctly?  Did I break the deployment by changing the ini settings?  I have spent a good 3 days on this and am at a loss, waiting for the support chat agent to pick up and thought I would throw this out to the forum to see if anyone can provide direction.

Autodesk revit 2016

I configure a network deployment with distributed license servers

workstation installing on is windows 10 all updated

I have no antivirus running on this test station - we use CylancePROTECT in house so will have to deal with that one after I get a base install working

I want to move this to SCCM to get benefits of wider distribution etc..

Thanks for any assistance!!

[Otto]

Hello JEDBIM2013 and welcome to the Autodesk community!

It looks like you are experiencing issues with your product on Windows 10 or want to know which Autodesk products are supported on Windows 10. Community members with similar questions found the following article(s) useful:

Windows 10 support for Autodesk products

Other threads about Windows 10 support

Change your mind about Windows 10? Here's how you can roll back

Please consider bookmarking these pages and checking back often; we'll update with new information as our testing continues.

If this information was helpful, please consider marking it as an Accepted Solution by clicking on the "Accept as Solution" link, below. Taking a moment to do this will help others with similar questions find useful answers. Thank you!

Kudos (click on the link or the "thumbs-up!" icon), are also gratefully received! (Even a bot likes praise.)

If this answer missed the mark, please let us know so that other community members can lend a hand. Any additional details might help, too: consider including relevant screenshots, log files, error messages, or system specs.

[Mark.Lancaster]

@Anonymous

Is the deployment configured to run in silent mode?  If so unselect that option again and see what happens.

[Anonymous]

Hey Mark - I unchecked it so I could see the install and it hangs on the 'Initializing' step forever.

[TravisNave · Accepted solution]

The image path should be \\Servername\Share.  Don't know why you'd get an error on the backslash...  Are you making it from a workstation?  Because you need to make it from a workstation and point the location to the server.

https://knowledge.autodesk.com/customer-service/network-license-administration/network-deployment/ov...

Might show some screen caps of what you are getting.

[Anonymous]

I am now testing from a downloaded revit2016 c:\autodesk\... folder just trying a straight up install > and it went past the Initializing window after a few seconds - so wanting to know what the difference is between this and a deployment (which contains my serial number / and both network servers for network licening).

[ukdxb012]

Did you put the UNC path with x2 \\ like this \\Servername\DeploymentFolder

I use SCCM 2012 and reference a *.bat with the following in...

::Install Autodesk Revit 2016
.\Img\Setup.exe /W /qb /I Img\Revit 2016 x64.ini /language en-us

Once ive created the Deployment Image of course.

The issue could also be .NET 4.6 on Windows 10... please refer to the following link... https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-...

Regards,

Duncan

[Anonymous]

yup I am creating a word doc with screen shots so you all can see what I am doing

[ukdxb012]

Check out the following link...The issue could also be .NET 4.6 on Windows 10... please refer to the following link... https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-...

I actually use a bit of code to avoid this in the *.bat file i mentioned previously to avoid this.

Regards,

Duncan

[Anonymous]

Problem is that I have been doing several installs of revit 2016 on windows 10 and I don't have any problems listed in that link. the problem is that it hangs on Initializing most of the time > if it gets past this step the install works fine. In my test I just did Autodesk Application Manager failed to install (log says failure is ignored, Result=1603)

[ukdxb012]

Take it out from the Deployment Image or edit the *.INI files to remove it from here...

#==================== Install Execute & UI Sequence

EXE_SEQUENCE=RVT;RCL;GLUE_PLUGIN_REV;CMILM2016;ADDONS
INSTALL_SEQUENCE=RCL;RVT;GLUE_PLUGIN_REV;CMILM2016;ADDONS
UI_SEQUENCE=BeginDeploymentDlg;LicenseDlg;ProductInfoDlg;ProductSelectionDlg2;RVT;RCL;GLUE_PLUGIN_REV;CMILM2016;NLM;CADM;REVITSERVER;ADDONS;FullProgressDlg;InstallCompleteDlg;DeploymentCompleteDlg;DeploymentFailedDlg;ADDONS

I never include the App Manager in any Deployment Image.

Refer to the link here for more info... http://help.autodesk.com/view/INSTALL_LICENSE/2015/ENU/?guid=GUID-FAB40CCD-0A6C-4E55-A994-0D237CD954...

Can you upload the log file created for further investigation?

[TravisNave]

---

@Anonymous.Brannan wrote:

Take it out from the Deployment Image or edit the *.INI files to remove it from here...

I never include the App Manager in any Deployment Image.

---

Hahaha!  I love that!

[Anonymous]

Curious as to why you do not install it - does it not work / has more issues than value. I like the idea of keeping autodesk stuff up to date more automated..

[ukdxb012]

Do your users have the permissions to run an update advertised via the app for the products they have installed? If they dont then whats the point of installing it?

[Anonymous]

yes our users would have the ability to do that - I want to keep our software up to date in as automated fashion as possible. If you don't use app manager what is your suggestion to keep software updated?

[TravisNave]

---

@Anonymous wrote:
yes our users would have the ability to do that - I want to keep our software up to date in as automated fashion as possible. If you don't use app manager what is your suggestion to keep software updated?

---

Manual updating when a user experiences a problem resolved by a service pack or hotfix. 

Speaking as an IT Professional whose job it is to perform updates, there is absolutely zero reason to update software if it is not broken.  If it is not broken, do not fix it.  More often than not, updates will break working systems or introduce new problems that themselves need updated.  If your users are working without issue, then there is no reason to disrupt them.  If they do, download and install the hotfix for that user.

Just my 2 cents.

[Darin.Green]

I would recommend keeping the App Manager as it provide available updates and services packs for the products installed on your machine. There's no real reason to not have it. If users don't have the ability to install software on their machine, they will not only have an issue with the App Manager but their Autodesk software as well--specifically, maintaining their application profile information.

Without the App Manager, you're forced to use the old fashion way of updating... Check the Autodesk site (Autodesk Account or Update Downloads) for updates, download them, then install hoping you don't already have that update installed. 🙂  The real pain point with this is knowing if you should be installing updates for Subscription products or non sub products.

The app manager should not cause any issues, except possibly not updating the list of available updates. < -- This was a major issue prior to Autodesk Desktop App which has replaced the old app manager. 

From a CAD Manager standpoint, it would be best to test service packs and updates before rolling them out to your team, especially in a custom environment.

[Anonymous]

Agree with you to a point Travis - there is some things however that should be kept pretty up to date (like windows) or you first start to become behind / then there are series of updates that are needed and when you have to do a lot of updates that is when problems start to happen.. For autodesk products it sounds like you patch only when needed for fixes or for additional functionality that is needed.

[Anonymous]

Thanks Darin - I agree with you 100% / I am trying to move us to more dynamic updates to stay more current (and help IT become more relevant!

[TravisNave]

My policy on Windows updates is similar. I can't tell you how many Windows updates break Autodesk peoducts. There are KB articles on what updates to uninstall. Because of this I actually run my own WSUS server so that I can approve all Windows updates. Never update if you don't know what you're updating. It's managed to make this IT guy's life a lot easier. 🙂