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

Checking Device Registry Settings

If at any point an error occurs, you should check the device registry settings. The 5.x agent has been designed to update these settings based on the AirWatch Console configuration settings. The relay server settings are a part of the job XML and will be applied during provisioning just before processing the job. This is just for informational purposes, but should the OS Update process not complete successfully, the settings below should be checked as part as any troubleshooting effort.

The following registry entries are required:

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 AirWatch 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 will be used to bring down the files from the FTP server when updating Windows Mobile. This will typically be “\Temp” or “\Storage Card”. In CE updates, the files are brought down one at a time into device memory so the parameter is not used in that case.

-p is the OSUpdate project name. It is whatever the user wants it to be. This is usually named something to indicate what the update package contains. Remember this would also be the name of the Motorola .APF file. The project (APF) should be named in such a way as to be able to know the target device, OS type, etc.

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

  • So 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.