Pushing Microsoft Management App via Profile breaks remote control

SO
Shawn O'Brien
freshmarkinc

Hi 

Having an odd problem, with the newst version of Microsoft Warehouse App 4.0.26.0 its breaking Mobi Device Remote control and only way to get it back is to restart, but then when you start the app it breaks it again....

So, we control the version of Microsoft's Warehouse Management app by using Profile, then packages to specify which version we use.  I have been trying to test the latest version 4.0.26.0.  so I setup my profile with the new version and then assign to push it out to my test devices.

everything goes as it should, I remote to my test devices and start up the new version of the app, at this point the App forces a screen rotation and then freezes in the remote control window.  On the device its phyically fine, but the remote window is frozen and even disconnecting/reconnecting I can't get it back.  I have to do a soft reset to get remote control back, but then once I start the app, it freezes again.

 

Wondering if anyone else is running into this?  we are using Honeywell VM1A and Honeywell CK65 devices.  I would like to be able to upgrade the app with outhaving to physically touch the devices as we have several buildings in different areas.

Thanks,

Shawn

 

8 days ago
SOTI MobiControl
ANSWERS

Hey, 

i wonder if you tried an agent restart (triggered via script) instead of doing an entire reboot of the device.
If you don't have the script it would be this one (in this case: JS):

mobicontrol.agent.restart();
mobicontrol.agent.checkIn();

or even legacy:

restartagent

 

But in general even if you get feedback from others here, i strongly recommend to raise this as a support case as this sounds like something Soti needs to investigate why RC crashes when the other app starts. Be aware that maybe MS needs to be involved at sometime as well, depending on the outcome of the troubleshooting.

SO
Shawn O'Brien
7 days ago

Thanks for that suggestion, I will give that a try when I'm testing this versioin later today.

It's only to see if a device reboot is needed or just an agent restart which could be a possible workaround until the issue is solved finally but still my recommendation stays to open a case at Soti support.