Yeah, you do.
Just because the DC reboots, is it serving requests through LDAP on all
interfaces? Or did one of those patches break multi-homed LDAP? (True story
- it happened.)
Just because the GC reboots, it is serving requests through LDAP and is the
NSPI interface initialized? (Without it, Exchange and older Outlook clients
won't work.)
Just because the exchange server reboots, did the IMAP service start?
Is RPC/HTTP working? Is the store listening on port 6004? Can you open a
mailbox? Can you authenticate?
If a client can use it, you need to test it.
I read this somewhere today (and copied it into my "think about pad"):
Think differently about policy
If...it isn't built into process
you have to search for it
it isn't auto-enforced ....it may as well not exist
Systems verify and enforce policy
I didn't write down the source (my bad). If you don't test for it - it's
going to fail on you, and you won't know it. There is nothing worse than a
client calling you to tell you that one of your systems are down and you
didn't already know it.
Regards,
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
From: David Lum [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26, 2008 5:26 PM
To: NT System Admin Issues
Subject: If you're monitoring your servers thoroughly....
.do you need to really check anything after patching and rebooting? I would
think if you're already monitoring all the services, shares, disk space,
event logs, data stores, etc then patch and reboot wouldn't require much
testing per se. For DC's you could even automate a DCDIAG on every restart
and have the results shot out, right?
This is a rose colored glasses look, but wondered if anyone actually pulls
this one off.
Dave Lum - Systems Engineer
[EMAIL PROTECTED] - (971)-222-1025
"When you step on the brakes your life is in your foot's hands"
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
