The new Task Manager program makes it possible for a user to stop
programs that are running on the device. The user also can view a list
of active programs or processes and monitor memory and CPU usage
Windows Mobile can be set to configure GPRS Settings automatically,
which provides users with basic Web data access on first boot by using
the Automatic Data Configuration (ADC) application. When automatic GPRS
configuration is enabled, the ADC application matches the GSM code of
the inserted SIM card to a group of provisioning settings and then
provisions the device with these settings:
The settings are provisioned when the device is booted, when a
different SIM card is detected, or when a user chooses to repair the
Automatic GPRS data configuration can be added to an image by
including the IMGDATACONFIG flag, which will be used at MAKEIMG time.
The following table shows the settings for this flag.
The ADC functionality is configured in a standalone package that is
not included in Windows Mobile 6 Standard and Windows Mobile 6
Professional images by default.
The ADC application can run in either of two modes, Repair mode or
Boot mode. It runs at boot time in Boot mode when a new SIM card is
detected Otherwise, the user can run the application in Repair to repair
dropped connections in Windows Mobile 6 Standard and Windows Mobile 6
In Boot mode, the ADC application has a nominal computing overhead
that is added to the total boot time. The ADC application is visible to
the user only after the device is unlocked.
The user can run the ADC application in Repair mode either from the Connections
Control Panel menu under Settings or from the WelcomeCenter.
Intermediate drive should work with GPS in HC25.
Not exposed since the Navman GPS is better. It is used internally.
The WM6.1 feature "Bluetooth Phone Address Profile" is not
Previously, we were not using Microsoft's Wireless Manager control
panel as the Summit driver was not properly power managed. With the
latest Summit driver, this is no longer an issue.
With the move to WM 6.1, it has been decided to now use Microsoft's
Wireless Manager. Although the new control panel does look prettier, it
does come with a few caveats:
There are new LTK tests specific to WM6.1. Configuring the database
is different for WM6.1. Instead of RTM, AKU1 needs to be selected. None
of the current SRs for WM6 apply to WM6.1. We will have to re-apply. We
will nee to set up a new SharePoint site. Most of the N/A and hardware
limitations still apply. The new tests have been tested by the Software
department (Ajmal, October LTK) and we pass all of the new tests. Ajmal
has worked through most of the LTK for WM6.1. SCR 19517 is the only
outstanding LTK SCR for WM6.1.
This is required for "Internet Explorer Mobile 6" (IEMO6). IEMO6
enables the cursor and allows keyboard navigation using the cursor.
IEMO6 is the only application on WM6 that uses the cursor.
Since cursor support seems to be working in WM6.1 (AKU1.4), the USB
mouse component has also been added to the image. This is Microsoft's
mouse HID support which works with this cursor support.
Note that the cursor changes were made to the shared display driver,
but cursor support is still not included in WinCE 5.0 SYSGEN. The
original changes for USB_MOUSE have all been removed.
In IEMO6 - the cursor appears when the arrow keys are pressed and
disappears when the screen is tapped or screen is switched to a
When USB mouse is plugged in, the cursor does not appear until the
mouse is moved. When the screen is tapped the cursor will disappear
until the mouse is moved again. When the USB mouse is removed, the
cursor may not disappear until the screen is tapped.
There will be a new Getting Started disk for WM6.1. It has its own
LTK tests that software will run. There is not much we can change. It is
created by adding links to pictures and icons into an XML file.
Formerly called "Yona". This is a remote configuration server from
Microsoft for WM6.1. I need to add more information about it. It has
similar capabilities to MCC. It is complex to set up. Several Microsoft
servers need to be configured to make it work. Doug Wood has worked on
it a bit. The new LTK tests should ensure that WM6.1 will work with the
System Center Mobile Device Manager.
Windows Mobile provides the Mobile VPN as a virtual private network
(VPN) component. The Mobile VPN enables remote access from a Windows
Mobile powered device to
The following table describes some specific features of the Mobile
The Mobile virtual private network (VPN) is provisioned during domain
enrollment with the System Center Mobile Device Manager. The initial
provisioning settings include VPN gateway and certificate related
information that is used for the mutual authentication of the VPN client
The Mobile VPN is not active by default in Windows Mobile 6 devices.
The following table describes the settings that must be set during
enrollment with the System Center Mobile Device Manager.
The System Center Mobile Device Managers administrator customizes
Mobile VPN settings from the Group Policy console through the extension
for Mobile VPN.
The following table describes the settings and policies that can be
customized for continuous provisioning.
The Mobilevirtual private network (VPN) Application user interface
(UI) provides real time information on the status of the Mobile VPN
connection. You can access the Mobile VPN application UI through the
Control Panel. To open the Mobile VPN application UI select Start,
select Settings, and then select Connections. On touch
screen mobile devices, Mobile VPN application UI is in Settings, on the Connections
To view the Mobile VPN Detailed Status Screen:
The following table describes the elements of the Mobile VPN detailed
When active, the Mobile virtual private network (VPN), can have
several important impacts on device function.
To help guarantee a seamless integration with Mobile VPN, make sure
to consider the following guidelines:
During Mobile VPN bootstrap, the Mobile VPN component installs a
Network Driver Interface Specification (NDIS) intermediate driver that
binds the Mobile VPN to each wide area network (WAN) and each wireless
local area network (WLAN) network adapter that is present on the device.
After binding, the name of each bound network adapter changes to
include the intermediate driver prefix.
For example, after installing an NDIS intermediate driver, the
<WiFiAdapterName1> wireless LAN adapter will be displayed as
<NDISPrefix>\<WiFiAdapterName1>, where the
<NDISPrefix> tag is defined by the NDIS intermediate driver.
For example, if the device has a wireless LAN adapter named
WiFiAdapterName1, after installing an NDIS intermediate driver, the name
appears as <NDISPrefix>\WiFiAdapterName.
To help ensure a seamless binding process, you need to adhere to the
The Mobile VPN intermediate driver has the following limitations:
For more information about intermediate drivers, see the Intermediate
Drivers, Dynamic Adapter Binding, and Opening an Adapter Underlying a
Protocol Driver topics.
After Mobile VPN is activated for the device, Mobile VPN runs
automatically whenever Windows Mobile loads. This might cause the device
to take a few seconds longer to load, depending on what device platform
is installed. Every device on which Mobile VPN runs must verify that
the drivers or applications that run when Windows Mobile is loaded
behave consistently, are not time-sensitive, and do not affect the
Representational icons in title bar reflect the status of the Mobile
virtual private network (VPN). There are four icons. Each icon
corresponds to a state, or states, of the VPN. The following table shows
For non-touchscreen mobile devices, the icons will appear in the
leftmost position, sharing the slot with the missed call notification
icon. The Mobile VPN icon will be lower in priority than the missed call
notification icon. That is, the missed call notification icon will
display instead of the Mobile VPN icon when there is a missed call.
For touchscreen mobile devices, the Connected, Disconnected, and
Connecting/Disconnecting icons will appear in the data connection slot,
third from the left. These icons have top priority, and will overwrite
any other data connection icon. In touchscreen mobile devices, the title
bar icons are, in general, selectable. When the Mobile VPN status icon
is selected the Connectivity bubble will appear, displaying the list of
data connections in the connected state.
The Disabled icon will appear in the notifications slot, second from
the left. This icon will have lowest priority, and will not be visible
in the notifications slot if any other notifications appear. In this
case, when the user clicks on the notifications icon, another title bar
will appear at the bottom of the screen that displays the various
notification icons applicable. The Disabled icon for Mobile VPN will
appear in this lower title bar. If the VPN Disabled icon is selected, a
toast will appear in the lower part of the device screen, allowing the
user to re-enable the VPN.
Highlights of Internet Explorer Mobile 6 features include:
Enhanced Touch/Gestures support: As part of our effort to improve
Windows Mobile usability, AKU 1.4 includes enhanced Finger-Touch user
experience for device navigation on list views and menus.