Table of Contents
Advertisement
Update Process - Updates to the SB1 should only be performed when the SB1 is in a cradle. Since the
•
SB1 is not intended to be used when it is in cradle, updates should be safe to perform at any time when
it is in the cradle.
The MSP Power Condition can be attached to policies to prevent updates from occurring when the SB1
is not in the cradle. The cold boot that is automatically performed at the end of an update should be safe
to perform any time the SB1 is in the cradle since it should not be in use.
• OS Update Packages - Motorola Solutions supplies OS Update packages on the Support Central
web site.
• Customer Created Packages - Customer created packages can be deployed using a package in the
same bundle as an OSUpdate package as long as it occurs before the OSUpdate package.
• Wireless Settings - Wireless Settings are persistent across an OS update.
RD Client - The RD Client application on the SB1 is not finger friendly. Careful and precise touches are
•
required when selecting options on the screen. When launching the RD Client, the message RD Client
may restart your device displays to warn the user that a cold boot is going to occur after updates are
initiated using RD Client.
MSP Agent - The MSP Agent does not display bundle messages, confirm conditions and power
•
conditions that would normally be presented to a user.
The value "MOTOROLA SB1B" is reported to MSP for the Device Attribute identity.deviceModel.
Package Building - A sample User Baseline package is provided to illustrate the Rho-based Shell
•
configuration. This can be modified as needed to change settings and/or add applications. A Package
Builder template is provided to simplify the creation of packages to deploy individual Rho-based
applications to the UserDrive folder. These packages can be incrementally deployed or removed to add
or remove their corresponding Rho-based applications. Customer-created packages should not be
created to deploy content to other destinations.
Warm Boot Implications - The following MSP methods are normally used to request an explicit warm
•
boot of a device:
• Warm boot step in a bundle
• Warm Boot Option in a package.
Both of these fail if used on an SB1 to prevent performing a cold boot when a warm boot is requested.
The MSP Agent Update package abup30 includes the Warm Boot option and fails if used alone on an
SB1.
MSP Packages
The following sections describes MSP packages that can and cannot be used with the SB1.
Recommended for Use
lists standard packages that are recommended for use on the SB1.
Table 4-1
Staging and Deployment
4 - 3
Advertisement
Table of Contents
