Chapter 18 of The Practice of System and Network Administration deals with this very topic. This chapter starts with a checklist, in 14 steps, for upgrading (including patching) servers.
Chapter 17 is more fundamentally related as it deals with change management, and chapters 20 and 22 are on Maintenance Windows and Service Monitoring, respectively. If you have a comprehensive monitoring infrastructure, then probably not. However, I'll bet that you don't, *if* it's a custom app. And, just because, using your example, you run a DCDIAG, doesn't mean you've caught the problem - you will have to parse the report, or automate parsing it, and get notified that something is wrong. Kurt On Tue, Feb 26, 2008 at 2:25 PM, David Lum <[EMAIL PROTECTED]> wrote: > > > > > …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> ~
