Hey there,
as you all know, when installing a new version of MobiControl you also need to upgrade the device agent on all of your devices.
I always have a lot of problems, when trying to upgrade the device agent on my Zebra MK4000 Win/CE devices. These devices have a very low amount of RAM and disk space and pretty much erase everything thats not stored in the \Application folder during a cold boot.
There is a script that gets executed everytime during cold boot, which installs applications and changes some settings around on the device to get it "ready for work". I've also included the installation of the MobiControl device agent in this script.
Unfortunately there is no specific device agent for the MK4000, I've already reached out to SOTI a while ago and asked for a agent but the support told me to use the generic one for Win/CE devices.
Everything works fine, once the new agent is on the device... but getting it on there is quite the task....
When upgrade the agent via the MobiControl console its always a gamble if the device comes back online or not. If not, I have to reach out to the user and ask him to cold boot the device... during boot the script installs the old agent again. At least Im able to remote control it again but im pretty much back to where I started.
The device logs only show a message "Agent upgrade attempt failed".
If the agent upgrade is successful I use a FileSync rule to get the new .CAB-File on the device. This always works without any errors.
Is it somehow possible to sync files with a rule when the agent on the device is outdated? If so, I could push the new agents .CAB-File to the device... tell the user to cold boot it and the bootscript installs the new agent. Done.
I hope someone reads through all this. :-)
