We use Standby Continuous Replication as part of our disaster recovery strategy. Our environment consists of an Exchange 2007 clustered mailbox server using CCR which also replicates to an SCR server. All our servers run Exchange 2007 SP2.
This week we did a test activation of the SCR replica in our test environment, but ran into an issue that we could not find a documented solution for. In the hope that it saves someone else some time and anguish I’ve written about it here.
Continuing on a theme of how to fix those niggly little problems in Exchange Server, today it’s the turn of this error when starting Outlook:
In an Active Directory domain running at the Windows Server 2003 or higher functional level the lastLogonTimestamp attribute can be used to find out if a user or computer has logged on to the domain recently. This can be useful information for finding inactive user and computer accounts so that they can be removed from AD.
With dozens of virtual servers on tens of virtual test networks here in the Exchange division, all getting hammered quite a bit with Naughty Things that Probably Shouldn’t Be Done, we tend to break things quite regularly.
One of the more common failures is Outlook Web Access under Exchange Server 2007. One way or another, it just stops working – sometimes in a minor way, sometimes more extensively. This morning, it simply presented me with a blank page after login.