Best Practices
. Make use of the FPC object for scripting the export of ISA configuration for documentation
purposes.
. Have documentation reviewed and approved by other stakeholders in the organization
to make sure that it meets their needs as well, and to simply get input from
another source. For technical procedures, the document also must be tested and
walked through.
. Consolidate and centralize documentation for the organization.
. Document the company??™s policies and procedures for security and maintenance.
. Create well thought-out and professional planning and design documentation to
avoid costly mistakes in the implementation or migration process, such as buying
too many server licenses or purchasing too many servers.
. Baseline and document the state of an ISA server so that any changes in its performance
can be identified at a later date.
. Use tools such as Microsoft Project to facilitate the creation of project plans, enable
the assignment of one or more resources per task, and enable the assignment of
durations and links to key predecessors.
. Create disaster recovery documentation that includes step-by-step procedures for
rebuilding each ISA server to minimize downtime and administration.
Pages:
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824