Motorola CA50, Руководство для разработчиков и пользователей, Страница: 357 / 542

Staging and Deploying CA50s 12 - 7
OS/UCA Client Application Upgrades Pushed from MSP Provision
When using MSP to provision multiple CA50s in close proximity with a new operating system, saturation of the
Access Point on the network must be taken into account.
Devices need to be in an area of excellent RF coverage, so additional infrastructure may need to be installed to
enable the best coverage and data rate possible. In addition, the CA50 should be in its charging cradle and must
be powered on. When not on AC power, AirBeam / OSUpdate checks battery capacity before updating the
partitions. Battery capacity below 75% results in an Insufficient Power message. MSP Provision functionality can
be initiated either manually by scanning Rapid Deployment bar codes or automatically using an Over-the-Air
command.
By default, from the factory, the CA50 MSP agent is not enabled. The MSP agent running on the CA50 provides a
means to automate the updating of CA50 software among other features.To enable the MSP agent running on the
CA50 generate the appropriate Rapid Deployment bar code(s). For details about how to generate Rapid
Deployment bar codes, refer to the MSP user manual.
Minimizing Network Traffic from the MSP Agent
To minimize the network traffic from CA50s checking for software updates on the MSP server, generate an MSP
policy that enables the CA50 to check for MSP downloads (also called MSP jobs) only when no user is logged onto
the device (UCA client application is running but the user is logged out). The MSP policy can only function properly
if the CA50 MSP agent is enabled. Refer to the latest MSP documentation on how to create a policy with the
universal condition and how to activate the policy.
MSP Setup on the CA50 for MSP Provisioning
Perform the following steps to perform periodic check-ins based on a universal condition.
1.
Creating the universal condition for the UCAClient application
•
In a Web browser, go to http://[server-ip]/msp.web to log in to an MSP server.
•
Select the Library tab.
•
Select the Conditions tab.
•
Click the Create button.
•
Select Universal.condition.xml for the condition type.
•
Enter a name for the condition, such as UCALoggedOff.
•
Select the Next button.
•
Enter a description for the condition, such as condition for UCA.
•
Select Constraint based on the registry key or value existence for the Constraint Type.
•
Select Test for the existence of the selected item for the Test Condition.
•
Select HKEY_LOCAL_MACHINE for the Registry Base Key.
•
Enter Software\Motorola\UCAClient\LoggedOff\ for the Registry Key or Value Name. In this case it is a
registry key because of the '\' after LoggedOff.
•
Click the Finish button.
2.
Policies with the universal condition for the UCAClient application
Any policies created with this condition cause the MSP client to only perform a policy when a user is logged out.
The UCAClient application removes the universal condition registry key defined above when a user is logged in.
The UCAClient application adds the universal condition registry key defined above when a user is logged out. This
in turn allows you to instruct the MSP client to process the policy.