Or if you go by what they say in the Disaster recovery guide, it's Controller Router Dispatcher
The really crazy part is they give the same order for stopping and starting. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, February 09, 2011 11:45 AM To: [email protected] Subject: Re: [Bes-admins] Proper order to stop and restart BES services of the many times i have called rim for various bes/cdo issues the order they had me stop and restart is router dispatcher controller they explained why, that explanation has escaped me, but do it now out of habit another slick tool is process eplorer either 64 or 32 bit flavors (depends on OS) it allows you to stop a problematic agent, you need to find agent problem user is on etc. which many times is root cause of mail delivery issues. less impact than stopping and restarting the 3 key services you can get it here http://download.cnet.com/Process-Explorer/3000-2094_4-10223605.html pretty slick tool ________________________________ From: [email protected] To: [email protected] Date: Wed, 9 Feb 2011 10:49:49 -0500 Subject: Re: [Bes-admins] Proper order to stop and restart BES services Mail Store, Policy and Synchronization services start and stop automatically with the controller. I wouldn't think you'd need to use start /wait, just net starts. From: [email protected] [mailto:[email protected]] On Behalf Of Richard Lawley Sent: Wednesday, February 09, 2011 10:44 AM To: A list for BES Admin's to discuss issues, etc. Subject: Re: [Bes-admins] Proper order to stop and restart BES services Thank you! I found this one. Can y'all tell me if it looks right to you? @echo off net stop "BlackBerry Router" net stop "BlackBerry Dispatcher" net stop "BlackBerry Controller" net stop "BlackBerry Synchronization Service" net stop "BlackBerry Policy Service" net stop "BlackBerry MDS Connection Service" net stop "BlackBerry Mail Store Service" net stop "BlackBerry Attachment Service" net stop "BlackBerry Alert" net stop "BlackBerry Administrative Service - Native Code Container" net stop "BlackBerry Administrative Service - Application Server" @echo off start /wait net start "BlackBerry Controller" start /wait net start "BlackBerry Dispatcher" start /wait net start "BlackBerry Router" start /wait net start "BlackBerry Synchronization Service" start /wait net start "BlackBerry Policy Service" start /wait net start "BlackBerry MDS Connection Service" start /wait net start "BlackBerry Mail Store Service" start /wait net start "BlackBerry Administrative Service - Native Code Container" start /wait net start "BlackBerry Administrative Service - Application Server" start /wait net start "BlackBerry Attachment Service" start /wait net start "BlackBerry Alert" Richard Lawley Information Technology Department Johanson Transportation Service Direct 559-458-2245 Office 800-742-2053 Cell 559-907-6610 Fax 559-458-2236 [cid:[email protected]]<http://www.johansontrans.com/> Please visit us at our website: www.johansontrans.com<http://www.johansontrans.com/> to learn more about our company and solutions we provide From: [email protected] [mailto:[email protected]] On Behalf Of Peterson David Sent: Wednesday, February 09, 2011 7:37 AM To: A list for BES Admin's to discuss issues,etc. Subject: Re: [Bes-admins] Proper order to stop and restart BES services This is the official order, though I have seen documents even from RIM that have a different order. I've never seen anything bad happen if it's done in the wrong order, just some extra errors in the event log, but BES seems to throw warnings out just as normal business so I never really was concerned about it. Besides, the services by default aren't set with dependencies, so there's no real order to the start when the server is rebooted. http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB13718 The actual commands would be Net start blackberry router Net start blackberry dispatcher Net start blackberry controller Stopping would be net stop in reverse order. If someone thinks it really matters, I'd love to know. From: [email protected] [mailto:[email protected]] On Behalf Of Richard Lawley Sent: Wednesday, February 09, 2011 10:20 AM To: A list for BES Admin's to discuss issues, etc. Subject: [Bes-admins] Proper order to stop and restart BES services I had a batch file that went through the steps to properly stop and then restart the BES services and now it's gone. I'm not a BES guru so I don't think I can just recreate it. Does someone have one that they can copy and paste it here so I can rebuild it please? Richard Lawley Information Technology Department Johanson Transportation Service Direct 559-458-2245 Office 800-742-2053 Cell 559-907-6610 Fax 559-458-2236 [cid:[email protected]]<http://www.johansontrans.com/> Please visit us at our website: www.johansontrans.com<http://www.johansontrans.com/> to learn more about our company and solutions we provide NOTICE: This electronic mail transmission from the law firm of Dinsmore & Shohl may constitute an attorney-client communication that is privileged at law. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying it, and notify the sender by reply e-mail, so that our address record can be corrected. _______________________________________________ Bes-Admins mailing list [email protected] http://www.dataoutages.com/mailman/listinfo/bes-admins http://www.dataoutages.com http://www.dataoutagenews.com RSS Feed: http://feeds.feedburner.com/Bes-admins --------------------------------- Bes-Admins mailing list is sponsored by Dataoutagenews.com. http://www.dataoutagenews.com
<<inline: image001.jpg>>
_______________________________________________ Bes-Admins mailing list [email protected] http://www.dataoutages.com/mailman/listinfo/bes-admins http://www.dataoutages.com http://www.dataoutagenews.com RSS Feed: http://feeds.feedburner.com/Bes-admins --------------------------------- Bes-Admins mailing list is sponsored by Dataoutagenews.com. http://www.dataoutagenews.com
