Recipe8.15.Enabling Support for

Using VBScript

' ------ SCRIPT CONFIGURATION ------
 strOrgName = "cn=<


orgName


> "        ' e.g., "Robichaux and Associates"
 strOrgObj= strOrgName & ", cn=microsoft Exchange,cn=services,cn=configuration," &_
    "dc=<


domain


>, dc=<


TLD


>"
 strOMAObj = "cn=Outlook Mobile Access,cn=global settings," & strOrgObj
 strDCName = "<


serverName


>"    ' e.g., BATMAN
' ------ END CONFIGURATION ---------

' get the global OMA settings object 
Set objOrg = GetObject("LDAP://" & strDCName & "/" & strOMAObj)

' reset the flag value to zero, which enables OMA on the server and enables
' the unsupported device flag
objOrg.Put "msExchOmaAdminWirelessEnable", "0"
objOrg.SetInfo
WScript.Echo "Enabled unsupported devices and OMA"

Discussion

OMA supports a fairly broad range of mobile devices, but they can't support every potential device. In general, phones or handhelds that implement the Openwave browser, Microsoft's Pocket Internet Explorer, or the Ericsson, Nokia, or Symbian browsers are supported. The canonical list of supported devices is located at http://www.asp.net/mobile/testeddevices.aspx?tabindex=6. Microsoft periodically releases update packages called device updates (DUs) that add support for additional devices; you can get the latest DU from the supported device page.

If you want to try using a device that you think should be compatible, you can toggle the Enable unsupported devices flag. When the setting is off, OMA will refuse to talk to any device not supported by the DU version on that server. When you turn it on, you can connect to OMA with any device you like, and if it's not supported, OMA will ask you to click OK on a confirmation page that reminds you that your device isn't supported.

See Also

MS KB 821835 (Overview of Mobile Devices That Are Supported by Outlook Mobile Access in Exchange Server 2003), Chapter 3 of the Exchange Server 2003 Client Access Guide (Microsoft), Chapter 8 of the Exchange Server 2003 Deployment Guide (Microsoft), and http:// blogs .msdn.com/conrad/archive/2005/01/21.aspx (Disable OMA via Hosted Exchange)

Using VBScript

' This code adds a new carrier by specifying the carrier CN and
' SMTP gateway address 
' ------ SCRIPT CONFIGURATION ------
strOmaCarrierDN = "cn=Carriers,cn=Outlook Mobile Access,cn=global " &_        
   "settings,cn=<


org name


>,cn=microsoft exchange, cn=services," &_
   "cn=configuration,dc=<


domain>


,dc=


com


"
' ------ END CONFIGURATION ---------
set objCarriers = Getobject("LDAP://" & strOmaCarrierDN)

'create and name the new carrier
set objNewCarrier = objCarriers.Create("msExchOmaCarrier", _
    "<


carrierName


>"    )    ' e.g., "cn=Acme Wireless"

'populate the SMTP domain information & commit to Active Directory
objNewCarrier.Put "msExchOmaCarrierAddress", _
    "<


carrierDomain


>"    ' e.g., "@sms.acmewireless.tld"
objNewCarrier.SetInfo
Wscript.Echo "New Carrier" & objNewCarrier & "created"

Discussion

To save your users the trouble of having to figure out what their mobile phone carrier's SMTP-to-SMS gateway address is, you can preconfigure your server with the proper entries, allowing ActiveSync users to pick their carrier from a drop-down list. After selecting their carrier, users can simply type in their telephone number, and Exchange Always-Up-To-Date (AUTD) notifications will be delivered to their mobile device.

Table 8-5 lists the most commonly used Smartphone carriers in the United States; depending on your location and carrier, you may need to contact them to get the correct gateway information.

Table 8-5. Common mobile carriers

See Also

MS KB 833745 (Exchange Always Up-To-Date Notifications do not work with your mobile device)