Including the background of meetings and brainstorming sessions that led up to the decisions
for the end state of the project provides the groundwork for the detailed designs
provided later in the document. For example, a decision may have been made ???because
the CEO wants it that way,??? which affects the post-migration environment. Other decisions
may have come about after many hours of debates over the particulars and required
technical research to come up with the ???right??? answer. Recording this level of information
can be extremely useful in the future if performance issues are encountered or additional
changes to the network are being considered.
The description of the end state to be implemented can be very high level or can drill
down to more specific configurations of each server, depending on the document??™s audience.
However, it is recommended that the design document not include step-by-step
procedures or other details of how the process is to be accomplished. This level of detail is
better handled, in most cases, in dedicated configuration or training documents, as
discussed later in this chapter.
Formalizing ISA Server Configuration with As-Built Documentation
The configuration document, often referred to as an as-built, details a snapshot configuration
of the ISA Server 2006 system as it is built.
Pages:
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797