How To Plan, Install, Manage, Maintain, Secure, Backup and Restore Small Business Server 2003 R2
Part One - Introduction
What the legal department makes us say.
This is not an official document! Nor is it a break-fix document.
This document - web site- is intended to enable a robust, secure, well maintained SBS 2003 environment, that will require a minimum of break-fix attention. Use any and all information contained in this document at your own risk. Do not proceed without having read the entire document. Or at least as much of it as you think you need for a SBS environment that you hope to have working for you, and not the other way around.
If you break anything you must fix it yourself. Your entire recourse is to start over. No warranties, expressed or implied.
This is not the do all and ends all of SBS documentation. While considering my own minor experience with SBS 2003, I noticed a dearth of documentation on how to get the base install done in a consistent and elegant manor, but an overwhelming amount of documentation on how to enhance and improve upon the base product. I hope what follows, in more or less check list form - from your purchase to the day the first mail comes rolling in, to the monthly maintenance schedule, may help to fill that perceived gap.
For improvements, enhancements, and modifications and changes for differing circumstances, please refer to the many books, blogs, web sites, both volunteer and subscription, and the news groups for further SBS 2003 assistance. For a place to begin to search, please look here.
When I began this article, I thought I could get it all into one document. I have discovered that there is too much material to accomplish this, so I have broken it down to several "chapters" and linked them separately here.
I have borrowed liberally from SBS News Group posts and whatever published sites I could find. With luck I have not "borrowed" any copyrighted material. If I have, and if the owner will contact me I will remove it, re word it, or give credit as desired. All copyrighted material, credited or not, is the property of its owner.
So to begin. I hope you find what follows to be useful.