The Windows Rugged OS Upgrade file/action might require Run command arguments to process the action on the device. You can also change the device registry settings.

Check Device Registry Settings

If at any point an error occurs, check the device registry settings. The 5.x agent has been designed to update these settings based on the Workspace ONE ™ UEM console configuration settings. The relay server settings are a part of the job XML and are applied during provisioning just before processing the job.

If the OS Update process does not complete successfully, the following settings are checked as part as any troubleshooting effort.

HKEY_LOCAL_MACHINE\SOFTWARE\AIRBEAM\  
IGNORESERVER

string “1”

SERVERRIP string [Enter the Server URL or IP Address]
FTPUSER string [Enter the FTP(s) username]
FTPPASSWORD string [Enter the FTP(s) password] - THIS FIELD MUST BE ENCRYPTED
TFTP string "0"
PASSIVEMODE string "1"
FTPPORT string "21"
FTPS string "0" or "1"
VERIFYSERVER string "0"
SOFTKEY1 number "123"
SOFTKEY2 number "124"
ENTERKEY number "13"

Run Command Argument Information

-d option describes the Workspace ONE UEM relay server folder path containing files required to update the device. It uses the following format (with forward slashes and double quotes): "[path of your relay server]/PFILES/[file action name]_version/"

-y option describes the maximum number of retry attempts while the –z option describes the retry delay.

-q is the folder on the device that is used to download the files from the FTP server when updating Windows Mobile. This location is typically “\Temp” or “\Storage Card”. In CE updates, the files are downloaded one at a time into memory so the parameter is not used in that case.

-p is the OSUpdate project name. The project name can be whatever the user wants it to be but is usually something to indicate what the update package contains. This name should be the same as the Motorola APF file. The project (APF) should be named in such a way as to be able to identify the target device, OS type, and so forth.

For the Workspace ONE UEM process, this name will be the same as whatever you call the dummy APD file (which can be an empty text file).

  • If your command line contained –p”WT41N0”, you need to have a WT41N0.apd file put down to the device prior to doing the update. This is only needed for CE devices.
  • For Windows Mobile devices –p”MC9190WM65” is required by the command line parsing, but in effect will not be used.