This section only applies to Windows Mobile 5.x/6.x devices that are using the mSuite Framework client.
mSuite ships with a default Device Settings policy, this is applied to all users. You can modify this policy or create a new policy and deploy that to groups of users.
This policy controls the Device Settings for Windows Mobile devices.
You need to be fully familiar with Windows Mobile devices if you intend to change these settings.
Best practise is to always work at a group level and not at an individual level. The system will let you do both but the administration task will be much easier if everything is done with groups. Users inherit virtually all of their settings from the group hierarchy, when you change the setting at an individual or sub group level, it will break this inheritance for the modified setting. This means if you later change this setting at a higher group level, the modified user or group will not inherit the change, which can be confusing.
Editing an existing policy
You can edit an existing policy by expanding the navigation tree, under the node Policies, select Device Settings. The action pane will display all of the Device Settings policies that are defined. By default there is a single policy Default Device Settings Policy. Right mouse click the name of the policy that you want to modify in the action pane and then select Configuration Wizard...
Creating a new policy
To create a new policy, expand Policies and select Device Settings in the navigation tree then right mouse click an existing policy in action pane. Select All Tasks > Copy settings to new policy... then enter the Name of the new policy and click OK. The new policy is created as a clone of the existing policy - to change the settings in the new policy, follow the instructions for Editing an existing policy above.
Defining the Policy
In either case, the Policy Management Wizard will run to allow you to define the policy.
|1.||Press Next on the Welcome screen to continue.|
|2.||If you are creating a new policy, enter the name that you want to use and press Next to continue.|
|3.||On the Windows Mobile Policy Settings page of the wizard, set up the required policy elements. To lock an element, right mouse on the (parent) node in the Device Policy window. The icon in the tree will change to reflect the lock status:|
|a)||Error Reporting\Enabled - Yes or No - allows or prevents the device from sending application crash information to Microsoft.|
|b)||Region Configuration\Region - choose the appropriate value from the drop down control.|
|c)||Owner Information - Enter the Name,Company, Address, Phone, Email and Notes. Set Display Id on Startup and Display Notes on Startup to Yes or No.|
|d)||Buttons - this allows you to associate applications with hardware buttons on the device. The configuration of the buttons on each device type is different, you ideally need to standardize on one device type if you want to use this facility.|
|e)||Backlight - Timeout on Battery, Timeout on Power. Set Timeout on Battery to a lower value for better battery life on the device.|
|f)||Bluetooth\Enabled - Yes or No. Enables or disables the Bluetooth capabilities of the device.|
|g)||Infrared\Enabled - Yes or No. Enables or disables the Infrared communications capabilities of the device.|
|h)||Start Menu - allows you to configure the device's Start menu with up to 7 applications.|
|i)||Internet Explorer - these settings allow you to pre-configure the Internet Explorer application.|
|j)||Today Screen - these settings allow you to configure the Today Screen on the device. This will only work with the standard Windows Mobile Today Screen plug-ins.|
|k)||Connections - this allows you to configure up to 4 network connections for the device.|
|l)||Proxy Configuration\mSuite\Use mSuite Proxy - Yes or No. If set to yes, all HTTP/HTTPS traffic will be tunneled to a corporate web proxy via the AES encrypted tunnel between the device and the Connection Manager Server on the mSuite server. This makes sure that all web browsing can take place through a centrally audited and controlled facility. (Not available in the first release.)|
|m)|| Proxy Configuration\mSuite\Username - the username used to authenticate with the corporate web proxy.|
|n)||Proxy Configuration\mSuite\Password - the password used to authenticate with the corporate web proxy.|
|o)||Proxy Configuration\mSuite\Domain - the Domain name used when authenticating with the corporate web proxy.|
|p)||Proxy Configuration\HTTP - the proxy settings for the HTTP proxy to be used by the device, ignore this if you are using the mSuite proxy.|
|q)||Proxy Configuration\WAP - the proxy settings for the WAP proxy to be used by the device, ignore this if you are using the mSuite proxy.|
|r)||Proxy Configuration\Socks - the proxy settings for the Socks proxy to be used by the device, ignore this if you are using the mSuite proxy.|
|s)||Proxy Configuration\Secure WAP - the proxy settings for the Secure WAP proxy to be used by the device, ignore this if you are using the mSuite proxy.|
Deploying the Policy to a Group of Users or an Individual User
To deploy a new Device Settings policy or change the currently deployed policy, expand the Administration node in the navigation tree, expand Users and Groups until you can see the user or group that you want to apply the policy to.
Deploying to a Group
|1.||In the navigation tree, right mouse click the group that you want to deploy to and then select Properties.|
|2.||Select the Policies tab and select the policy from the drop down list.|
|3.||Click Apply then click OK.|
Users in the group will receive the new/changed policy next time their device connects.
Deploying to a User
|1.||In the action pane, right mouse click the user that you want to deploy the policy to and the select Properties.|
|2.||Check Show Advanced to display the advanced properties - this is sticky, once you have checked this it will remain checked until you choose to hide the advanced properties again.|
|3.||Select the Policies tab and select the policy from the drop down list.|
|4.||Click Apply then click OK.|