amset

.info
.co.uk - exchange consultancy
.net - internet based solutions
Have your Exchange server installed, maintained or
upgraded by Amset IT Solutions.
Exchange 2000, 2003, 2003 SBS, 2007
More Information (UK only)

Broadband - Exchange
Login Scripts - Net Admin
Outlook - Windows Mobile
Windows

Contact - Advertise

AddThis Social Bookmark Button

Exchange Server

Exchange Consultancy


Amazon Store


Basic Email Gateway Server

Company wide Contact List

Disabled User Account

Distribution Lists

DNS Configuration

Exchange and a
Dynamic IP Address

Event ID 1221

Filter Unknown Users

Global Mailbox Folder
Permissions from Server

Intelligent Message Filter

Internal Email Address
for External People

Internet Tools

Mailbox and Management
Account

Message Tracking

Migrating to a new server

Multiple Domains

Offline Address Book Errors

Options when a Staff Member
Leaves

Outlook Web Access

PDAs, OMA and EAS

Permissions Best Practises

Post Install Configuration

Public Folders

Prerequisites for Exchange
System Tools

RPC over HTTPS

Secure your SMTP Relay

Shutdown Script

SMTP Services and Exchange

SMTP Diagnostics

Spam Cleanup

Switching From POP3
to SMTP Delivery

Telnet Test

Tools for Admin of
Exchange Server

Username Change

Exchange Server
Compatibility Information
Exchange
Server Version
Compatibility
5.5 No
2000 No
2003 Yes
2007 Yes
Mobile - Deployment by Config File

Author: Simon Butler, Exchange MVP, MCSE
Last Page Review: 30/01/2008

If you need to deploy lots of devices to use Windows Mobile, or would like to make it so that users can deploy the configuration for themselves, then you can use a cabinet file to deploy the settings quickly and easily. All that the user will need to do is enter their username and password.

To create this file you need to be using Windows XP Professional, which contains the correct version of the makecab utility.

If you are using an SSL certificate that is not natively supported by the Windows Mobile device, then you can also deploy the certificate via this mechanism at the same time.

Customised Version of these Instructions

Would you like a customised version of these instructions, along with the cabinet file for YOUR company? If you are in the UK, then this is one of the services that we can provide for you. Please contact us for more information.

Part One - Create the initial XML File

Open up a new notepad document and copy and paste the following text in to that file:

Part Two - Customise the XML file.

You need to change a number of lines in the file to match your environment.

  • <parm name="AllowSSLOption" value="1" />
    Change the number 1 to 0 if you aren't using SSL.
  • <parm name="Server" value="servername.domain.com"/>
    Change servername.domain.com to the fully qualified domain name that will be used to access the Exchange server from the INTERNET. If you are using SSL, then it needs to match the common name on the SSL certificate.
  • <parm name="Domain" value="domain" />
    Change the second "domain" to match your Windows domain name. This will be the same value that you enter when logging in to OWA in the format of domain\username

Save the file as "_setup.xml" - don't use any other name, as the import process will not work correctly on the Windows Mobile device. Make sure that you save the file in to a location that is easy to get to with a command line, as you will be running a process in the next step.

Part Three - Create the Cabinet File

The Window Mobile device needs the file in a cabinet file, which is created via a tool built in to Windows XP.

Drop in to a command prompt, change to the directory where you saved the _setup.xml file and then enter the following command:

makecab _setup.xml file.cab

replace file.cab with whatever you want to call the file, as long as the name ends in .cab

Part Four - Deploy the cabinet file

To deploy the cabinet file, simply copy it to the device and click on the file. It will be automatically installed.
You can also make the file downloadable from a web site, perhaps your internal intranet.

Adding the SSL Certificate

If you are deploying a custom or additional SSL certificate, then create that xml file using the process outlined here. However don't create the cabinet file, instead copy the contents of the file in to this XML file. Remove the middle two line <wap-provisioningdoc> and </wap-provisioningdoc>. There should be one at the top of the file and one at the end of the file - nothing more. 
Then create the cabinet file as already explained.

Sponsored Links

Last Page Update:
30/01/2008

Back to the Top
Contact Us - Advertise on amset.info
Exchange Index - Home Page


Broadband - Exchange - Login Scripts - Network Admin - Outlook - Windows Mobile - Windows


© Amset IT Solutions Ltd. 1998 - 2008. All rights reserved. Reproduction of any content on this web site is prohibited without express written consent. Use of this web site is subject to our terms and conditions. All trademarks and registered trademarks are property of their respective owners. This site is not endorsed or recommended by any company or organisation mentioned on this site. This site is to provide guidance only and as such we cannot be held responsible for any consequences of following the advice given.