11-30-2009 11:19 AM
First, my setup - a rather non-descript one, with a single Exchange 2003 mailbox server in a native Windows 2003 AD domain, two DCs and BES 5.0.0 running on a Windows 2003 32bit server. Database is MSSQL 2005 running on a separate box.
The issue is this: Our DCs are updated weekly, When they reboot, the BES server can't authenticate to the database (of course) or Exchaneg servercausing a failure of the Messaging Service, until I either re-start the services or reboot the whole box.
I intend to have the DC reboots staggered next time, but if we somehow lose both DCs for a minute in the future BES will go south again. I'd rather it die completely if it can't connect to the database or Exchange for any reason. That would let me restart it after 5 minutes automatically or get a warning or something, rather than have my CIO call my cell to complain. Is there any way to configure this, or am I just going to have to monitor the situation manually?
I'm rockin the BlackBerry DTEK60, Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook,BT Headset HS-700
12-02-2009 01:55 PM
If it is weekly then run a script to reboot BES a few minutes later.
All my update/reboots are manual so BES gets booted last.
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V