VMware Workspace ONE Community
EricMartinez
Contributor
Contributor

Updating Intelligent Hub Agent on Windows 10

On SaaS environment and planning to update the Intelligence Hub on Windows 10 devices? We have a mix (1903,1905) of previous versions installed on devices, but wanted to get all devices on the same version. What is best practices around this and has anyone run into this scenario before?

Thank you!
Labels (1)
Reply
0 Kudos
3 Replies
KyleSchroeder
Contributor
Contributor

Same question, 3 years later - when you try to run the MSI to update the agent, it complains that the old version is there.  But if I remove it, won't that unenroll my device?  How to upgrade in place?  I tried the method for beta updates (placing the airwatchagent.msi in the n C:\Program Files (x86)\Airwatch\AgentUI\Update folder, but running the AW.WinPC.Updater.exe throws an exception about a missing dependency:

C:\Program Files (x86)\Airwatch\AgentUI>aw.winpc.updater

Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Extensions.DependencyModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at VMware.Hub.Logging.ServiceCollectionExtensions.ConfigureLogger(IServiceCollection services, IEnumerable`1 map, LogLevel namedLoggingLevel, Boolean admin, Boolean writeToConsole, String settingsFile)
at AW.WinPC.Updater.Program.Main(String[] args)

Tags (3)
Reply
0 Kudos
ogushia
Hot Shot
Hot Shot

Hi,

I had the same requirement recently.(in my case: Hub 2107 → Hub 2203)

I have successfully updated Hub without uninstall or unenroll with the following steps:

1. Place AirwatchAgent.msi in any folder on the target device (e.g. C:\TMP).

2. Open cmd.exe with administrator privileges and run the following commands:

>C:\TMP\AirwatchAgent.msi /passive

KyleSchroeder
Contributor
Contributor

ogushia,

Outstanding, that did the trick!  Now, why the MSI can't have the logic in it to do this automatically instead of erroring out and indicating that only uninstalling can solve this - seems like a packaging bug to me!

Tags (1)
Reply
0 Kudos