Motorola SB1, Руководство интегратора

Страница: 85 / 136

Staging and Deployment 4 - 27
Performing OS Updates from MSP
To push an OS Update to the SB1:
1.
Obtain an
SB1 OSUpdate
package from the SB1 page on the Motorola Solutions Support Central web
site.
2.
Create a bundle containing the following deployment steps in the exact order:
a.
SB1SaveCalibration
package.
The Force Install option should not be set for this deployment step so the package is skipped if it is
already present on the SB1.
The package is only installed if it is not already installed on the SB1. This ensures that the Touch Panel
Calibration information produced when the user successfully performed a Touch Panel Calibration is
stored persistently if it has not already been stored. Since this bundle results in two cold boots, failure
to ensure that Touch Panel Calibration information is stored persistently requires the user to perform
Touch Panel Calibration following each cold boot.
b.
WipeUserDrive
package.
This package is optional and would be installed to satisfy two key use cases.
If the intent of the bundle includes loading new content in the
UserDrive
folder, then installing this
package with the Force Install flag set to True ensures that the package is installed, and that the
UserDrive
partition is erased, regardless of whether the package is already installed on the SB1. If any
packages are used to deploy content to the
UserDrive
folder, then it is advisable to first ensure that the
UserDrive
folder is empty. This ensures a predictable result no matter what state the SB1 may be in
when staging is initiated.
If the intent of the bundle is to return the SB1 to factory default state, then installing this package with
the Force Install flag set to True ensures that the
UserDrive
partition is empty, as it is when the SB1 is
shipped from the factory. Perform an OS Update in this way places the SB1 in the state it would have
been in had it come from the factory loaded with the OS to which it was just updated.
c.
An SB1 Baseline Package, with the Force Install flag set to True.
If the intent of the bundle is to populate content into the
UserDrive
folder, and to prepare an SB1 for
production use, then a suitable SB1 Baseline Package should be installed. Installing an SB1 Baseline
Package with the Force Install flag set to True ensures that the specified content is deployed to the
UserDrive
folder whether or not the package is already on the SB1. This is especially important if the
WipeUserDrive
package was installed previously in the bundle because while the
WipeUserDrive
package removes content from the
UserDrive
folder, it does not uninstall any package(s) that may
have deployed that content. Forcing the SB1 Baseline Package to be reinstalled in such a case
guarantees that the content is always deployed.
d.
One or more SB1 application package(s), with the Force Install flag set to True.
If the intent of the bundle is to populate content into the
UserDrive
folder, and to prepare an SB1 for
production use, then one or more SB1 applications packages may be installed. Installing an SB1
application package with the Force Install flag set to True ensures that the specified content is
deployed to the
UserDrive
folder whether or not the package is already on the SB1. This is especially
important if the
WipeUserDrive
package was installed previously in the bundle because while the
WipeUserDrive
package removes content from the
UserDrive
folder, it does not uninstall any
package(s) that may have deployed that content. Forcing an SB1 application package to be reinstalled
in such a case guarantees that the content is always deployed.
e.
The
Sb1PrepareForOsUpdate
Package.
The Force Install option should be set for this deployment step, so the package is always deployed
even if it is already present on the SB1.