[doctortt]

I know BES talks to one domain controller for GC and etc. I was told that if the DC that the BES communicates with gets rebooted, I need to either restart all BES services or reboot the BES server when the DC comes back up. First of all, why? Second, is there a way to make BES to talk to two DCs?

[Jadey]

Heh, I am guessing you use Exchange back end? I can't help, soz, live in domino land. Exchange BES Admins might find it useful to know your exchange / BES versions tho.

[doctortt]

Yup, I'm in Exchange world.

[fadmin]

BES is not well designed when it comes to self-recovery. Certain failures would just choke it and some won't. Unfortunately I had mixed lack with GC failover. Some BES would be able to pick other GC up and continue to work ok and some just won't. Beats me why. To answer your question, I don't think you can specify more then one anyway. It will recover when it comes disconnection from SQL,router,internet but when it comes to disconnection from exchange and GC servers not very forgiving...

[iamwiz82]

I have two DCs and have never had an issue with needing to restart the BES services. It's also never had a problem when rebooting either of our Exchange servers, that I have noticed.

In fact, just a few weeks ago I had my DCs down for maintenance, one at a time, and BES kept chugging along.

[fadmin]

I noticed that too that some of them would work and some would not. With exchange is different. It never works unless I restart services.