I'm not a big fan of OCS for a whole pile of reasons, beginning with the inflexible, lacking UI and ending with restrictions on the specific deployment I use that force me to VPN to connect. Mostly issues I wouldn't have with Jabber.
With our configuration (and possibly by default) URLs were shown as plain text and not as clickable hyperlinks. You can enable this with a Group Policy - download the OCS Policies documentation and edit and import communicator.adm, or with a registry edit.
Changing the Registry
Registry edits are quick and easy, and I was only concerned about myself, so I took that route.
Save the code code below into a text file with a .reg suffix and import it, or right click the following link and and Save As to download .reg file to enable clickable URLs in OCS. Once the registry changes have been made or imported you will need to restart your OCS client.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]
"EnableURL"=dword:00000001
If you'd prefer to manually make the registry changes:
- Open regedit.ext and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator
- Create a new DWORD value called EnableURL and set the value to 1 to make the URLs clickable. Set the value to 0 to have the URLs appear as plain text.
Due Diligence
Checking in with an employee at Jabber to see if hyperlinks are enabled in MomentIM.

Good to know.
I actually love OneNote, but this window has me confused. Perhaps someone from the OneNote team could shed some light on what the progress bar is measuring? It popped up after hitting CTRL+2 to tag an item and steadily reported on the progress of some nameless task for about 5 minutes.

I recently picked up a first-generation iPhone from a friend and after playing around with it for a while I decided that I needed to have my email synchronized on it. For my business I run my BES, Exchange with RPC over HTTPS and ISA on a Server 2003 virtual machine, so my infrastructure was almost ready.
Almost, but not quite. A typical ActiveSync deployment consists of a front-end Exchange server, an ISA server and a second Exchange server. I've only got a single VM (more for convenience than anything else), so I had to make a few changes.
Assumptions
I'm assuming that you've got Exchange and ISA working, either on a single box or two individual servers. You also have a valid SSL certificate and port 443 is open.
Exchange Configuration
Enable ActiveSync
Open the Exchange System Manager (ESM) and expand the Global Settings tree. Right click on Mobile Service, choose Properties and ensure that the ActiveSync options are all checked.

IIS Configuration
These steps are identical to the ones in Microsoft KB 817379 - Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or forms-based authentication is required for Exchange Server 2003.
- Start Internet Information Services (IIS) Manager.
- Locate the Exchange virtual directory. The default location is as follows:
-
Web SitesDefault Web SiteExchange
- Right-click the Exchange virtual directory, click All Tasks, and then click Save Configuration to a File.

- In the File name box, type a name. For example, type ExchangeVDir. Click OK.
- Right-click the root of this Web site. Typically, this is Default Web Site. Click New, and then click Virtual Directory (from file).

- In the Import Configuration dialog box, click Browse, locate the file that you created in step 4, click Open, and then click Read File.
- Under Select a configuration to import, click Exchange, and then click OK.
- A dialog box will appear that states that the "virtual directory already exists."

- In the Alias box, type a name for the new virtual directory that you want Exchange ActiveSync and Outlook Mobile Access to use. For example, type ExchDAV. Click OK.
- Right-click the new virtual directory. In this example, click ExchDAV. Click Properties.
- Click the Directory Security tab.
- Under Authentication and access control, click Edit.
- Make sure that only the following authentication methods are enabled, and then click OK:
- Integrated Windows authentication
- Basic authentication

- On the Directory Security tab, under IP address and domain name restrictions, click Edit.
- Click the option for Denied access, click Add, click Single computer and type the IP address of the server that you are configuring, and then click OK.

- Under Secure communications, click Edit. Make sure that Require secure channel (SSL) is not enabled, and then click OK.

- Click OK, and then close the IIS Manager.
- Click Start, click Run, type regedit, and then click OK.
- Locate the following registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMasSyncParameters
- Right-click Parameters, click to New, and then click String Value.
- Type ExchangeVDir, and then press ENTER. Right-click ExchangeVDir, and then click Modify.
- Note ExchangeVDir is case-sensitive. If you do not type ExchangeVDir exactly as it appears in this article, ActiveSync does not find the key when it locates the ExchDAV folder.
- In the Value data box, type the name of the new virtual directory that you created in step 8. For example, type /ExchDAV. Click OK.
- Quit Registry Editor.
- Restart the IIS Admin service. To do this, follow these steps:
- Click Start, click Run, type services.msc, and then click OK.
- In the list of services, right-click IIS Admin service, and then click Restart.
ISA Configuration
You'll want to increase the heartbeat to 30 minutes per Microsoft KB 905013 - Enterprise firewall configuration for Exchange ActiveSync Direct Push Technology. If you don't do this you'll receive Event ID 3033 in your Application event log with the message:
The average of the most recent [200] heartbeat intervals used by clients is less than or equal to [540]. Make sure that your firewall configuration is set to work correctly with Exchange ActiveSync and direct push technology. Specifically, make sure that your firewall is configured so that requests to Exchange ActiveSync do not expire before they have the opportunity to be processed.
- Open ISA Server Management and click Firewall Policy.
- On the Toolbox tab, click Network Objects.
- Expand the Web Listeners node, and then view the advanced properties of the applicable Web Listener.
- Click the Preferences tab, and then click Advanced.
- Modify the Connection Timeout from the default 120 seconds (2 minutes) to 1800 seconds (30 minutes).

- Click OK two times to accept these changes.
- Click Apply.
The End
That's really all there is to it. If you've got RPC over HTTPS working then your ISA server should be ready to handle traffic on port 443, and you're only a few steps away from ActiveSync glory.
While there currently isn't any BES-like point of entry for an iPhone to gain access to a corporate network, it's trivial to establish a Cisco IPsec VPN connection.
Getting Started
You'll need the following information:
- VPN Server
- User account name
- User password
- Group name
- Group password
You should know your user account name and password and you can obtain the VPN Server, Group name and Group password from your .pcf file. A PCF file typically contains an encrypted password which you can decrypt using my Cisco VPN Password Decryption page. You can also ask your VPN administrator for the plain text password.
Sample PCF File
The VPN server can be found after Host= in the pcf file. Group Name is after GroupName=, Group Password is after enc_GroupPwd= or GroupPwd=. Asterisks added below for emphasis.
[main]
Description=Connect to Company VPN
****Host=your-vpn-server.coreygilmore.com
AuthType=1
****GroupName=accounting
GroupPwd=
****enc_GroupPwd=9196FE0075E359E6A2486905A1EFAE9A11D652B2C588EF3FBA15574237302B74C194EC7D0DD16645CB534D94CE85FEC4
EnableISPConnect=0
ISPConnectType=0
ISPConnect=
ISPCommand=
Username=
SaveUserPassword=0
UserPassword=
enc_UserPassword=
NTDomain=CorpDomain
EnableBackup=0
BackupServer=
EnableMSLogon=1
MSLogonType=1
EnableNat=1
CertStore=0
CertName=
CertPath=
CertSubjectName=
CertSerialHash=00000000000000000000000000000000
DHGroup=2
ForceKeepAlives=0
PeerTimeout=90
Adding the Connection
From the Home screen on the iPhone open the Settings application. Navigate through General > Network > VPN. Tap Add VPN Configuration and choose IPSec.

Using the information provided to you by your VPN administrator or gleaned from the PCF file, fill out the fields. If you use a SecurID for authentication leave the Password field empty and you will be prompted for it each time you connect. Below is a sample VPN connection configuration:

Connecting
Once the fields are populated and the connection is saved you can connect to your VPN server by opening
Settings > VPN and sliding the toggle into the On position.