Discovered that the problem was due to an option enabled on the Kemp called Enable Server NAT (SNAT). You can find this under System Configuration, Miscellanious Options, Network Options. Disabling that corrected the issue almost immediately. Seems that the NAT broke the DAG.

Activate a Blackberry 10 device between July 1st and August 31st 2013 and for each device you will get TWO free CALs. These CALS are the EMM Corporate type so will work for Blackberry 10 devices and Android/iPhone. At current prices they are worth almost £70 each.

The BES 10 software is free (trial download on the link above).

The window to claim the free CALs is quite small, so Blackberry have provided a link to be told when the registration process is open.

I was recently asked to look at an Exchange server giving the common PowerShell connection failure due to Kerberos authentication.

The following error occurred while attempting to connect to the specified Exchange server 'rpi-exchange.rp.local':

"The attempt to connect to http://rpi-exchange.rp.local/PowerShell using "Kerberos" authentication failed: Connecting to the remote server failed with the following error message: The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more information, see the about_Remote_Troubleshooting Help topic. "

The usual reasons for this error are well documented and I am not covering them here. After spending an hour going through the usual suspects, I started to look for anything else, as this was giving a Connection Refused error, which wasn't hugely documented past the Remote PowerShell permission.

I then had a brainwave. I was working on a system in a school. Schools have pretty restricted Internet access in most cases. This usually means a proxy.

Netsh winhttp show proxy

That command immediately showed there was a proxy, running

Netsh winhttp reset proxy

Cleared the proxy settings and allowed the Exchange Management Console to start correctly.

The client was then advised to check their proxy configuration settings, specifically the exceptions list so that the correct ones were in place, as I feared that next time Group Policy applied the proxy settings, the change would be reset.

You can use the transporter suite to migrate to the new version of BES with almost no downtime for the end users.

Note - this is the full BES 4.1, not the older Professional or other free options. If you are using BPS then you should move to BES Express.

The reason for Blackberry doing this is to encourage moves to Blackberry 10 devices. One of the features of the BES 10 version is able to manage both Blackberry 10 and older devices from a single interface. However for that to work the older devices need to be on a BES 5 server.

If you are using BES 4.1 now is the time to upgrade.

If you have devices still using OS 4.x then it would also be a good time to look at upgrading those, at least the OS, but preferably the device as well.

If you are in the UK, then I can assist you with this upgrade, please use my business web site to contact me: http://www.sembee.co.uk/