Application Manager

[stuart_smith82]

Does anyone else find the Application Manager doesn't work? 

I have created a deployment and gone to add updates afterwards and the application manager tells me: 
"Your Autodesk Software is completely up to date - there are no updates needed."

The above statement would be fine it it were not completely wrong.

I have so many problems with the application manager on a regular basis. When I can get it to work it always lets me down by not showing updates on some products and example of which is Vault updates. I have never managed to append / add updates for Vault 2018 in the application manager it never see's the updates?? 

Why didn't Autodesk leave in the original behaviour where you appended updates when creating or modifying the deployment? i am sorry but this tool simply does not work. 

Any help on this would be great. 

[Mark.Lancaster]

@stuart_smith82

The application manager was retired awhile back.  Its called the Desktop Application.  Is that what you are referring to?

In addition I would recommend that you disregard that piece of bloatware.  It causes more issues than it resolves.  In addition you shouldn't be applying Vault updates to your deployment.  Your Vault client build # can't be newer than the Vault server build #.  One more thing about updates.  They should only be applied if the update is going to resolve an issue that you're faced with.  Why break something that's working.  Are you just applying updates because its there?  Have you tested this updates to make sure they meet your requirements?

Update:  Adding for clarification..  If the update is related to the mid-year release and you want the new functions, yes by all means add those to your deployment or add them later.  But if these updates are related to service pack or hot-fixes, then...  Well I already covered that. 

[stuart_smith82]

duplicate of below

[stuart_smith82]

It still called the Application manager when you create a deployment for 2018 product design suite. Having the updates appended to the deployment saves a huge amount of time when rolling out product to users.

I am installing the updates for inventor, vault client, vault server, and mechanical because;

• I have a test environment for vault server and client to test installation and migration process before 'go live' i would rather deploy with updates and allow them to test
• Clients have requested the new features in inventor 2018 updates 1-3
• The hotfixes are designed to fix issues in RTM software and issues detected beyond. 
• I don't think its realistic to ask users to test product for weeks and hope that they cover all features that might be used by everyone in company and then decide on which updates are needed based on their feedback before rolling out.
• Its recommended by autodesk and as you know once you cant solve the problem yourself you approach autodesk and they will want updates applied.
• Have you seen the list of issues each hotfix resolves for inventor alone? Customer would not want to have to manage and install updates on a user by user basis when they have 40+ users
• If customer starts having issues and I tell them to install update 1 on 40+ machines they would not be happy knowing we as company could have installed them during original install which we were paid for.
• They don't currently use SCCM or other systems for easily deployment of updates

I understand your sentiment on why break something that isn't broken and you can try and explain that logic to a large organisation but it wouldn't wash.

If you put two scenarios in front of a customer;

A) I didn't install any updates and there is an issue

B) I installed all updates and there is an issue  

They would be more disappointed with scenario A.  

[Mark.Lancaster]

@stuart_smith82

I fully understand where you're coming from..  By my experience in this matter..  That interface is worthless. 

Not saying you can't apply updates and mid-year releases.  But certain things break other things.  Just because there's a list of fixes doesn't mean those fixes are impacting anything you are seeing.  Yes years ago I was always updating the minute something came out but over time you realize those updates were breaking other things that are crucial to your organization.  In addition the way that mid-year releases work you have to apply those things a different way (included software option) in your deployment.  They are not considered hot-fixes and that's why it states its up-to-date.  They are subscription benefits so the deployment interface doesn't know if you are a subscription customer or not.  Its looking for updates.  The team that creates the deployment interface is behind in what's happening with how mid-year releases are being issued now to the end user.

[stuart_smith82]

My sentiments exactly have to agree to disagree. So even now you install no updates for any customer on 2018 software unless they report issue afterwards? 

My post is about updates not appearing at all in the application manager and when a Autodesk is changing to a subscription model they need to be a bit smarter with how they offering hotfixes and updates for deployments. 

I have managed to include hotfixes and mid releases in deployments before but it isn't working in this example and as previously stated never has the vault updates worked. 

[Mark.Lancaster]

---

@stuart_smith82 wrote:

My sentiments exactly have to agree to disagree.

---

That's fine..    I private message you or took the topic off-line..