Tuesday, February 16, 2010

SBS 2008 Console Crash

I recently took over maintenance of an SBS 2008 server where the console would crash immediately on startup. Turns out it would run in safemode.

It turned out that someone had been changing the default network settings for the SBSMonitoring database instance and had enabled IP. This caused a conflict with another database running on the server that was also using port 1433. If the SBSMonitoring database was down, the console crashed.

The solution was to disable IP communication for the SBSMonitoring database. By default it uses only shared memory for communication.

Recovering from a Removed Exchange Organization

A few weeks back I got a call from an organization that had accidentally removed their Exchange Server 2007 organization. There was some confusion during the removal of the Exchange 2003 server after the migration was complete and some essential data was lost. There was no backup of Active Directory. So, a restore of AD was not possible.

Fortunately it was a relatively small environment with a single Exchange 2007 server and about 120 mailboxes.

Here's what we did:
  • use ADSI Edit to completely remove the existing Exchange organization
  • completely wipe out and reinstall Windows on the Exchange 2007 box
  • reinstall Exchange 2007 creating the same organization name
  • recreate the storage groups and copy databases into the storage groups.
  • Disable and reenable all users in EMC to recreate Exchange attributes
  • Disable and reenable all distribution groups in EMC to recreate exchange attributes
  • Configure certificate and smtp connectors.

Basically a whole rebuild. In retrospect, I should have tried just running /PrepareAD to see if that resolved the AD issues.

Note that the organization name needs to be the same during the reinstall or the databases will not mount.