The Remote Device Wipe option provides the following functions:
Initiating a Remote Wipe for a Lost or a Stolen Mobile Device
To initiate a remote wipe, you can search for a user’s mobile device by specifying the user’s name. As shown in the figure below, the Remote Device Wipe Web page displays the device ID, device type, the time that the device last synchronized with the Exchange server, and the wipe status or delete status of the device for each user's mobile device. To initiate a remote wipe for a lost or stolen mobile device, you can locate the desired device and then choose Wipe. The Remote Device Wipe Web page then displays the up-to-date status for the mobile device, displaying whether and when the device was successfully wiped.
Viewing the Status on a Pending Remote Wipe for a Lost or a Stolen Mobile Device
When a remote wipe is specified for a mobile device, the remote wipe command stays active until the administrator specifies otherwise. This means that, after the initial remote wipe has been completed, the Exchange server continues to send a remote wipe directive if the same device ever tries to reconnect to the Exchange server.
Canceling a Remote Wipe If a Lost or a Stolen Mobile Device Is Recovered
If a lost mobile device is recovered and the remote wipe that you initiated has not occurred, you must cancel the wipe in order for the device to successfully connect again. To cancel the wipe, locate the mobile device that has the remote wipe command set and then click Cancel Wipe.
Deleting a Mobile Device Partnership from the Exchange server
You can use the remote wipe command to delete a mobile device partnership from the Exchange server. This action, which is primarily useful for "housekeeping" purposes, will delete from the Exchange server all states that are associated with a specified device. If a user tries to connect a mobile device to the Exchange server after the partnership between the mobile device and the Exchange server has been deleted, the mobile device user will be forced to re-establish the partnership with the Exchange server.
The following table shows the information that is compiled by the Remote Wipe transaction log regarding the critical administrative actions that are performed when you use the Exchange ActiveSync Mobile Administration Web tool.
Date and time when the action was executed
The user who executed the action
The mailbox that the action pertained to
The device that the action pertained to
The type of device that the action pertained to
The action taken by the administrator
Provisioning or Configuring the Windows Mobile 5.0-based Device
If you are working with a mobile operator or a mobile device manufacturer to deploy your Windows Mobile 5.0-based devices, you may be able to acquire mobile devices that have been pre-configured with the technologies and security settings that fit your needs.
You can use the device provisioning tools that are available in the Windows Mobile 5.0 Software Development Kit (SDK) to configure settings on the devices; to add, update, and remove software from the mobile devices; or to change the functionality of the mobile devices.
You must have either manager access to the Windows Mobile 5.0-based devices or the ability to run trusted code on them in order to use the provisioning tools. Check with your mobile operator or device manufacturer for more information on the application security settings on your devices.
For more information about managing mobile devices, see the "Managing Devices" section of the SDK for detailed information. The SDK documentation is included in the MSDN Library. The SDK documentation and tools are available at no charge from the Microsoft Download Center.
Be aware that there are two versions of Windows Mobile 5.0 software: Windows Mobile Version 5.0 software for Pocket PCs and Windows Mobile Version 5.0 software for Smartphones. Some procedures are different for these different versions of Windows Mobile 5.0 software. While working in the SDK, closely follow references and directions for the version that is on your mobile devices.
Overview of Provisioning
Provisioning a Windows Mobile 5.0-based device involves creating a provisioning XML file that contains configuration information, and then sending the file to the device. The Configuration Manager and the Configuration Service Providers configure the device based on the contents of the provisioning XML file.
The Configuration Manager is the central authority that processes the provisioning XML file. The Configuration Service Providers carry out all configuration queries and changes. After the data is passed to the Configuration Service Providers, they are responsible for carrying out the changes to the mobile device and for reporting the success or failure of the transaction.
In order to use the provisioning tools, you must have either manager access to the Windows Mobile 5.0-based devices or the ability to run trusted code on them.
The following bulleted list describes most, but not all, of the ways that you can deliver the provisioning XML file to the mobile device:
A device that is connected to a desktop by a USB connection.
Over the air (OTA).
Download from a Web site.
Placement in device ROM or persistent storage.
The Provisioning Process
The following is a walkthrough of the provisioning process using a sample XML file that you can use to configure your Windows Mobile-5.0 based devices with the path and the domain name of your Exchange server. The resulting configuration should enable your users to synchronize their mobile devices without having to enter this information.
During this sample provisioning process, you will perform the following tasks:
1. Create the provisioning XML file.
2. Prepare the provisioning XML file for delivery using ActiveSync.
3. Deliver the provisioning XML file to the device by using a USB connection or a storage card.
In this process, you will use the makecab.exe utility to create a .cab file. Makecab.exe is included with the Microsoft Windows Operating System and is available from the Command prompt.
XML provisioning files can be packaged as .cab or .cpf files. Because ActiveSync Application Manager does not recognize .cpf files, the .cab format is used in this sample.
Copy the following provisioning code for the Sync Configuration Service Provider and paste it into Notepad or other text editor.
Change \\testserver to the name of your Exchange server, and change testcompany to the domain name of your Exchange server.
Save the file as _setup.xml.
The _setup.xml file must be processed as a .cab file before it is transferred and installed on your user's mobile device with ActiveSync Application Manager.
To prepare the XML file for delivery through the Desktop
1. To create a .cab file from the _setup.xml file, run the Makecab.exe utility, using the following syntax:
makecab _setup.xml myFile.cab 2. You may want to have your mobile operator sign the .cab file. This is an optional step that will remove the possibility of your users seeing the Unknown Publisher dialog box during installation.
The provisioning .cab file can be distributed to a device that is cradled to a desktop PC. The provisioning .cab file can also be distributed to a mobile device on a variety of storage cards, such as a MultiMedia Card (MMC), a Secure Digital I/O (SDIO) card, and a Compact Flash card that are inserted into the device.
If the ActiveSync Setup wizard appears when you connect the mobile device to a desktop computer, click Cancel. It is recommended that you use Windows Explorer and File explorer to transfer the .cab file to the device.