Ask Learn
Preview
Please sign in to use this experience.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
4/8/2010
The Clock Configuration Service Provider is used to configure the local time zones, and system alarm settings. It sets the time zone, the alarm time and whether the alarm is on or off.
When you set the Alarm or Clock using a provisioning XML file, the Clock Configuration Service Provider expects you to provide the full date/time string in ISO 8601 standard date/time format:
[YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]
For example, 2005-10-04T13:45:59Z
represents 4 October 2005 at 1:45:59 PM. The 'Z' specifies Coordinated Universal Time (also known as UTC or Zulu time), which uses the 24-hour numbering system.
Note
This Configuration Service Provider is supported by the OMA Client Provisioning (formerly WAP Client Provisioning) protocol.
Note
Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.
The following image shows the management object used by OMA DM.
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
The Clock Configuration Service Provider is available on Windows Mobile Professional and Windows Mobile Classic as of Windows Mobile 6.1. However, on these platforms, this Configuration Service Provider supports only the Date and Time settings (Date, Time, and TimeZone), and does not support the Alarm settings (AlarmOn, AlarmOn2, AlarmTime, AlarmTime2, and AlarmTimeout).
Only the root characteristic is available.
AlarmOn
Determines the state of the first system alarm (Alarm 1). The following table lists the possible values:
Value | Description |
---|---|
0 |
Turns off the alarm |
1 |
Turns on the alarm (every day) |
2 |
Turns on the alarm (weekdays only) |
3 |
Turns on the alarm (weekends only) |
The following table shows the default settings.
Permissions |
Read/Write |
Data type |
Integer |
Label |
Alarm 1: |
Semantic type |
Short-date time |
Roles allowed to query and update setting |
Manager AuthenticatedUser |
This setting is not available on Windows Mobile Professional and Windows Mobile Classic.
AlarmOn2
Determines the state of the second system alarm (Alarm 2). This parameter has the same syntax and default values as AlarmOn, except that the default value of Label is 'Alarm 2:'.
This setting is not available on Windows Mobile Professional and Windows Mobile Classic.
AlarmTime
Sets the alarm time for the first system alarm (Alarm 1). The following table shows the default settings:
Permissions |
read/write |
Data type |
time |
Label |
Alarm 1 time: |
Semantic type |
short-date time |
Roles allowed to query and update setting |
Manager AuthenticatedUser |
Value |
GMT time format; a leading 0 is required if the hour is less than 10. For example, 06:00:00Z. Alarm time will be adjusted to the time zone set on the device. |
This setting is not available on Windows Mobile Professional and Windows Mobile Classic.
AlarmTime2
Sets the alarm time for the second system alarm (Alarm 2). This parameter has the same syntax and default values as AlarmTime, except that the default value of Label is 'Alarm 2 time:'.
This setting is not available on Windows Mobile Professional and Windows Mobile Classic.
AlarmTimeout
Specifies the interval, in minutes, after which the alarm reminder will be automatically dismissed. If this DWORD value is 0, or is not present, the alarm will have no timeout.
This setting corresponds to the AlarmTimeout registry setting**.
This setting is not available on Windows Mobile Professional and Windows Mobile Classic.
Date
Specifies the system date information. The following table shows the default settings:
Permissions |
Read/write |
Data type |
String |
Roles allowed to query and update setting |
Manager Operator Operator TPS AuthenticatedUser |
Time
Specifies the system time information. The following table shows the default settings:
Permissions |
Read/write |
Data type |
String |
Roles allowed to query and update setting |
Manager Operator Operator TPS AuthenticatedUser |
TimeZone
Sets the current time zone on the system. The following table lists the possible values:
Value | Description |
---|---|
0 |
GMT-12 Kwajalein |
1 |
GMT-11 Samoa, Midway |
2 |
GMT-10 Hawaii |
3 |
GMT-9 Alaska |
4 |
GMT-8 Pacific US |
10 |
GMT-7 Mountain US |
13 |
GMT-7 Chihuahua, La Paz |
15 |
GMT-7 Arizona |
20 |
GMT-6 Central US |
25 |
GMT-6 Saskatchewan |
30 |
GMT-6 Mexico City, Monterrey |
33 |
GMT-6 Central America |
35 |
GMT-5 Eastern US |
40 |
GMT-5 Indiana (USA) |
45 |
GMT-5 Bogota, Lima |
50 |
GMT-4 Atlantic |
55 |
GMT-4 Caracas, La Paz |
56 |
GMT-4 Santiago |
60 |
GMT-3:30 Newfoundland |
65 |
GMT-3 Brasilia |
70 |
GMT-3 Buenos Aires |
73 |
GMT-3 Greenland |
75 |
GMT-2 Mid-Atlantic |
80 |
GMT-1 Azores |
83 |
GMT-1 Cape Verde |
85 |
GMT London, Dublin |
90 |
GMT Casablanca |
95 |
GMT+1 Prague, Budapest |
100 |
GMT+1 Warsaw, Sofija |
105 |
GMT+1 Paris, Madrid |
110 |
GMT+1 Berlin, Rome |
113 |
GMT+1 West Central Africa |
115 |
GMT+2 Bucharest |
120 |
GMT+2 Cairo |
125 |
GMT+2 Helsinki, Riga |
130 |
GMT+2 Athens, Istanbul |
135 |
GMT+2 Jerusalem |
140 |
GMT+2 Pretoria |
145 |
GMT+3 Moscow |
150 |
GMT+3 Riyadh, Kuwait |
155 |
GMT+3 Nairobi |
158 |
GMT+3 Baghdad |
160 |
GMT+3:30 Tehran |
165 |
GMT+4 Abu Dhabi |
170 |
GMT+4 Baku, Tbilisi |
175 |
GMT+4:30 Kabul |
180 |
GMT+5 Yekaterinburg |
185 |
GMT+5 Islamabad |
190 |
GMT+5:30 New Delhi |
193 |
GMT+5:45 Kathmandu |
195 |
GMT+6 Astana, Dhaka |
200 |
GMT+6 Sri Lanka |
201 |
GMT+6 Almaty |
203 |
GMT+6:30 Yangoon |
205 |
GMT+7 Bangkok, Hanoi |
207 |
GMT+7 Krasnoyarsk |
210 |
GMT+8 Beijing, Hong Kong |
215 |
GMT+8 Malaysia, Singapore |
220 |
GMT+8 Taipei |
225 |
GMT+8 Perth |
227 |
GMT+8 Ulaanbataar |
230 |
GMT+9 Seoul |
235 |
GMT+9 Tokyo, Osaka |
240 |
GMT+9 Yakutsk |
245 |
GMT+9:30 Darwin |
250 |
GMT+9:30 Adelaide |
255 |
GMT+10 Sydney |
260 |
GMT+10 Brisbane |
265 |
GMT+10 Hobart |
270 |
GMT+10 Vladivostok |
275 |
GMT+10 Guam |
280 |
GMT+11 Magadan |
285 |
GMT+12 Fiji Islands |
290 |
GMT+12 New Zealand |
300 |
GMT+13 Tonga |
The following table shows the default settings:
Permissions |
Read/Write |
Data type |
Integer |
Label |
Time zone: |
Roles allowed to query and update setting |
Manager Operator Operator - TPS AuthenticatedUser |
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
Elements | Available |
---|---|
parm-query |
Yes |
noparm |
No |
nocharacteristic |
No |
characteristic-query |
No |
Use these elements to build standard OMA Client Provisioning (formerly WAP Client Provisioning) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see OMA Client Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.
Clock Configuration Service Provider Examples for OMA Client Provisioning
Configuration Service Provider Reference for Windows Mobile Devices
Please sign in to use this experience.
Sign in