A checklist

re: A checklist

Dean — Sat, 15 Dec 2007 19:11:47 GMT

And another thing. There is no possible way that ANYONE could install any of these complex operating systems and apps without one because there is just plain to much stuff to remember. You are going to forget AT LEAST one thing without one.

re: A checklist

Dean — Sat, 15 Dec 2007 19:09:40 GMT

Yes I do ! I have what I call a Standard Server Install document with a whole crapload of things to check off. I have a document for installing the first domain controller in a domain. I have another document for installing Exhange server and another for installing SBS 2003. And they all keep changing as I find out more info. Another reason why I hate having to move to a new operting system every time Microsoft comes out with a new one and stops selling the old one.

I also have an Exchange Disaster Recovery document that is now up to 94 pages and is only about half finished.

Checklists and Process Improvement

Greener Pastures — Fri, 14 Dec 2007 15:27:51 GMT

msmvps.com/.../a-checklist.aspx Susan brings this up, and Karl persistently

re: A checklist

Axel Larson — Fri, 14 Dec 2007 00:10:20 GMT

If checklists make you not think, you are doing them wrong. Create a new checklist for each important or complex project and do your thinking ahead of time. I worked in the State of California's largest data center. Their change control procedure required a checklist be made before any system change. It had to include a fallback procedure in case something failed. Befor the change was approved for implementation, it had to pass a peer review. These procedures were a large part of the reason our uptime percentage was well over 99%.