Motorola SB1, Integrator Manual

Page: 86 / 136

4 - 28 SB1 Integrator Guide
Every bundle that installs an
OSUpdate
package to an SB1 must include the
Sb1PrepareForOsUpdate
package just before the
OSUpdate
package. Installing the
Sb1PrepareForOsUpdate
package places the SB1 into a state in which the OS Update can be
successfully performed. Since the
Sb1PrepareForOsUpdate
package might have been previously
installed on the SB1 during a prior OS Update, installing it with the Force Install flag set to True
ensures that the SB1 is placed the state required to allow the OS Update to be performed.
The
Sb1PrepareForOsUpdate
package causes an explicit cold boot to occur which is mandatory in
order to place the SB1 into the state required to allow the OS Update to be performed. After the cold
boot, the processing of the bundle by the
RD Client
continues. As previously noted, the
SB1SaveCalibration
package should generally be used to suppress the need for the user to perform
Touch Panel Calibration following that cold boot.
f.
SB1WipeCalibration
package (optional), with the Force Install flag set to True.
If the intent of the bundle is to return a SB1 to factory default state, then it may be desirable to remove
any Touch Panel Calibration information that was saved. If the
SB1WipeCalibration
package is
installed between the
Sb1PrepareForOsUpdate
package and the
OSUpdate
package, then Touch
Panel Calibration is suppressed on the cold boot initiated by the
Sb1PrepareForOsUpdate
package
(before the OS
Update
package) but Touch Panel Calibration is be required after the OS Update is
complete, as it would be on a fresh out of the box device.
Since the
SB1WipeCalibration
package may have been previously installed on the SB1, installing the
SB1WipeCalibration
package with the Force Install flag set to True ensures that the Touch Panel
Calibration information is always removed. Note that unless it is specifically desired to require that
Touch Panel Calibration be performed by the user, then this package should not be included in the
bundle.
g.
The
OSUpdate
package from step 1.
In some cases, an
OSUpdate
package might be applied more than once to the same SB1. For
example, a package might be used to return an SB1 to the factory default state even if the OS in the
SB1 was previously deployed using that same package. Installing an
OSUpdate
package with the
Force Install flag set to True ensures that the OS Update is always performed and that the SB1 is
always placed into the desired state.
3.
Create a Policy or Action to deploy the bundle from step 2.
•
When a Job to execute the bundle from step 2 is executed, the SB1 reboots into a mode where the
Rho-based Shell is not running. This allows the
Application
partition and OS to be safely updated.
When the OS Update is complete, the SB1 reboots again into a mode where the Rho-based Shell and PTT
Express are running. Under normal circumstances, Wireless Settings connectivity and manageability by MSP
is preserved across the application and OS Update.
In the event that the OS Update reformats the
Application
and/or
UserDrive
folders, then Wireless Settings
connectivity and/or manageability by MSP may not be preserved across the application and OS Update.
Pushing an MSP Agent Update
To update the MSP Agent using MSP:
1.
Choose the most appropriate MSP Agent Update package.
•
Most commonly, the
abup30
package with a version of ddd_xxx should be used.
•
Alternately, the
abup30
package with a version of ddp_xxx could be used, if support for Detached Jobs
is required. Refer to the
MSP Client Software Guide
for more information).
2.
Create a bundle containing the desired deployment steps: