Fix it how? Who's the vendor that I can go to and say "fix it!"? Microsoft? Legato?
Even if I remove Legato and PCAnywhere from my servers so that it is Microsoft only, do you think Microsoft is going to send engineers out here to track down why our IS does not shut down cleanly after the server has been running for months? -----Original Message----- From: Woodruff, Michael [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 1:29 PM To: Exchange Discussions Subject: RE: scheduling automatic rebooting of server Yeah, and then you fix it. -----Original Message----- From: Ken Cornetet [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:26 PM To: Exchange Discussions Subject: RE: scheduling automatic rebooting of server The fact that some people can smoke 3 packs of Marlboros a day and still live to be 90 years old doesn't mean that cigarettes aren't dangerous. Likewise, the fact that you (and others) can run problem-free computer systems without rebooting doesn't mean there aren't bugs in the software. It simply means that people have different computer environments. Different users, different software, different networks, hell, maybe different gamma rays - who knows? The simple fact is that NT and Exchange (and other auxiliary software like backup agents and remote-control) are not bug-free, nor will they ever be. Some bugs, when tickled, create subtle "corruption" (overwriting a random memory location, locking a resource, whatever). Eventually, some vital organ is hit and the system gets sick... -----Original Message----- From: Woodruff, Michael [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 11:57 AM To: Exchange Discussions Subject: RE: scheduling automatic rebooting of server Sir, How do you explain the folks who run this stuff everyday without any (or little:-)) errors? -----Original Message----- From: Ken Cornetet [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 12:47 PM To: Exchange Discussions Subject: RE: scheduling automatic rebooting of server Because ASP gets senile quickly. If we don't reboot the OWA server weekly, we start seeing ASP errors on the OWA server. Likewise, we can count on the IMS servers to start flaking out after a month or two if we don't reboot them. Twice monthly is probably overkill, but since the reboots are "free" (ie: users never notice), we go for twice monthly. Mailbox servers tend to be a bit more stable, but prior to the reboots, we would occasionally start seeing errors, and when we tried to manually reboot, the exchange services would never go down cleanly. In honesty, we started these reboots in the NT SP5 & MSX SP2 days. We've not tried reducing them since we went to 6a & SP3. For the people on the list who insist that periodic reboots aren't needed: please save yourselves the effort of telling me how reboots aren't required if you have quality hardware and good admin practices. The boxes are HP netservers, lotsa RAM and CPU, and are running on EMC disk arrays. Likewise, our administration is VERY conservative. We do nothing to the servers unless we fully understand and test first on separate test systems. The only software on these boxes other than NT and Exchange is PCAnywhere and Legato networker client. I like Exchange. I like Exchange a lot. But it is not bug-free. I've found that periodic reboots tend to keep obscure bugs obscure. -----Original Message----- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 11:21 AM To: Exchange Discussions Subject: RE: scheduling automatic rebooting of server But why are the reboots required? -----Original Message----- From: Ken Cornetet [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 12:17 PM To: Exchange Discussions Subject: RE: scheduling automatic rebooting of server If you are into Perl, I've got a script that I use to reboot our MSX55 servers (monthly for mailbox servers, twice monthly for IMS, weekly for OWA). It could undoubtedly be tweaked for what you want. It shuts down the MSX services before the reboot (and verifies that they do indeed stop). After the reboot is complete, it verifies that any service running at the time of reboot is running after the reboot. Sends email showing the results. -----Original Message----- From: James Cornett [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 10:34 AM To: Exchange Discussions Subject: scheduling automatic rebooting of server Does anyone know how to schedule the automatic rebooting of Windows 2000 Servers. I have looked on the their website and have found next to nothing about how to do this. What I am trying to do is on our Mail server I want to have the machine reboot say every Sunday night at a certain time. If anyone knows how to do this in Windows 2000 I would greatly appreciate the information. _____________________________________ James Cornett Network Administrator New Israel Fund 1101 14th Street, NW Sixth Floor Washington, DC 20005 Phone: 202-842-0900 ext. 269 Fax: 202-842-0991 [EMAIL PROTECTED] www.newisraelfund.org _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] ---------------------------------------------------------------------------- -- The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you. ============================================================================ == _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
