Unable to expand Public Folders in Outlook on Exchange 2010

Outlook clients were unable to expand public folders with the following error being displayd

Public folders access using  OWA was fine.

After looking at the Mailbox server the RPC Client Access service was stopped

The service wouldn’t come online complaining that the port was already in use.

A reboot of the server resolved the issue

Windows Phone Can’t Connect to Zune

I just connected my Windows Phone to my PC and was ceremonially hit with the Zune error

Can’t connect to your phone. Disconnect it, Restart it, then try connecting again

After a bit of digging the resolution for me was to remove the Zune certificate from my user account personal store. Once this was done the phone connected fine

Use the following steps to resolve the issue

• Make sure that Zune is closed
• Run certmgr.msc
• Expand Personal and then Certificates
• Delete the Zune Certificate

• Open the folder C:\Users\<UserName>\AppData\Roaming\Microsoft\Crypto\RSA
• There will be a folder with a name similar to the following S-1-5-21-1615704545-2677611709-1415672177-1156
• Rename this folder by appending .old or similar to the end of the folder name
• Restart Zune

Exchange 2010 NLB and remote Subnets

While configuring an Exchange 2010 NLB I had no choice but to publish direct access to the Exchange servers from the Internet instead of using my preferred method of directing all traffic through a TMG\ISA server.

Consequently access to the published NLB wouldn’t resolve properly from external locations. All traffic on the local LAN was fine although traffic originating from outside the local subnet was dropped and no response was received by clients.

The servers were configured with dual NIC’s with a dedicated NIC on each host being assigned for NLB traffic. As the NLB NIC only has an IP and Subnet entered I suspected that the lack of default gateway to be the issue.

I changed the Firewall rules to point to an individual servers Public NIC then everything was fine although this bypassed the NLB and as such wasnt really of much use to me.

As of Windows 2008 R2 all networking uses “Strong Host Model” whereby traffic can only exit from the interface that it entered on.

A resolution for this was to allow forwarding of traffic from the NLB NIC to the public NIC via the following command.

netsh int ipv4 set int “[Name of NLB NIC]” forwarding=enabled