| |
ZfH helps you make your handheld device users more productive by letting you configure all handheld devices across your organization with the same settings. Having the same configuration on all devices also helps to lower your help desk costs associated with supporting handheld devices.
ZfH provides a Configuration policy for the following platforms:
Palm: The Palm Configuration policy lets you set general preferences, such as auto-off, system sound, and beam retrieve settings; associate different software programs with the buttons on the Palm OS device; assign a feature users can access when they drag the pen from the writing area to the top of the screen on the Palm OS device; and specify which software programs are allowed or not allowed on Palm OS devices.
WinCE: The WinCE Configuration policy lets you associate different software programs or functions with the buttons on the Windows CE device; specify which programs you want to include on the Start menu (on a Pocket PC) or on the desktop (on a handheld PC); and specify power settings for Windows CE devices.
To set up the Configuration policy:
In ConsoleOne, right-click the Handheld Package object, then click Properties.
On the Policies tab, click the down-arrow, then click the desired platform:
On the Buttons: Configuration page, make the desired configuration changes.
Palm: For the Palm platform, the Button Column lists the available buttons on the Palm OS device.
To change a button's association, select a button from the Button list, click Edit, click Set to Application, browse to an application, then click OK.
The Pen Function drop-down list lets you assign a feature users can access when they drag the pen from the writing area to the top of the screen on the Palm OS device. For example, you can select Turn Off & Lock to make it easier for users to turn off and lock their Palm OS devices. To assign a feature, choose an option from the drop-down list.
WinCE: For the WinCE platform, click Add to change a button's association.
To view the button naming conventions for your particular handheld device, on the Windows CE device, click Start > Settings > Buttons. For example, on a Compaq iPAQ Pocket PC, the buttons are named Button 1, Button 2, and so forth. On a HP Jornada Pocket PC, the buttons are named Hot key 1, Hot key 2, and so forth.
Select a button, click OK, then select an option:
Reset to Default: Resets the selected button's association to the factory default association.
Set to Application: Lets you specify the application to assign to the selected button. If you specify an application that is not in the Start menu path (or subpath), you may need to restart the handheld device to see the changes.
Set to Other Function: Lets you specify a function from the drop-down list to assign a function to the selected button.
The available options include:
On the Programs page, make the desired configuration changes.
Palm: For the Palm platform, the Application column lists the applications that you want to allow on the device or remove from the device.
To add an application to the list, click Add, browse to the application, then click OK.
Select a rule to apply to the application:
WinCE: For the Windows CE platform: the Shortcut Name lists the programs that you want to include on the Start menu/desktop.
Click Add to specify a program to be added to the Shortcut list, fill in the Shortcut Name box (this is the name that will display in the Start menu or on the desktop), fill in the Target path (the full path to an application's executable file), then click OK.
Click Hide All Items in the Programs Folder to hide the names and icons of all listed programs in the Programs folder. Using this option lets the user only run applications from the Start menu (on Pocket PC devices) or on the desktop (on handheld PC devices).
If you chose the Palm platform, make the desired configuration changes on the General page.
You can change the settings for the following preferences:
Each preference in the list contains a Don't Change setting. If you choose this setting, ZfH will not change that preference on associated devices; the corresponding setting on each device will determine its behavior. For example, if you choose the Don't Change setting for Auto-Off After, each associated device will use its own preference settings to determine how long an idle Palm OS device will wait until it turns itself off. If you want to ensure consistency across all associated Palm OS devices, choose the appropriate setting.
If you chose the WinCE platform, make the desired configuration changes on the Power page.
If you select the Don't Change setting, ZfH will not change that setting on associated devices; the corresponding setting on each device will determine its behavior. For example, if you select the Don't Change setting, each associated device will use its own preference settings to determine how long an idle Windows CE device will wait until it turns itself off. If you want to ensure consistency across all associated Windows CE devices, select the appropriate setting.
If you select the Disable setting, ZfH will disable that setting on all associated Windows CE devices; idle Windows CE devices will not shut down.
Click OK to save the policy.
The Configuration policy you configured and enabled will not be in effect until you associate its policy package with a handheld device object, a handheld group object, or a container object.
NOTE: If you competed the steps in the previous scenarios, you have already associated the Handheld package to a handheld device and you can ignore the following steps.
In ConsoleOne, right-click the Handheld Package object, then click Properties.
Click the Associations tab > Add.
Browse to and select the desired Pocket PC device for associating the package, then click OK.
For this scenario, you should now synchronize your handheld device so you can see the results of the Configuration policy being enforced on the device. After the handheld device has been synchronized, you can also view the Configuration policy's status on the Policy Status page in ConsoleOne.
Using the ZfH Configuration policy, you can:
| |