Use the following guidelines to assist in preplanning tasks.

Server Example data needed, where applicable, and by location Data collected

Location and function

Document the location and function of the computers that run the core services of your network, such as global catalog servers, domain controllers, DNS and WINS servers, Internet Information Services (IIS) servers, computers running Microsoft SQL Server or Terminal Services, Microsoft Exchange servers, print servers, and file servers.


Naming conventions

Document current naming conventions for products you use with Configuration Manager 2007, such as computers running Windows Server 2003 and SQL Server. This helps you establish and document naming conventions for Configuration Manager 2007 hierarchy elements. These elements include sites, site codes, servers, and the objects that are used by or created in the Configuration Manager console. Because the Configuration Manager site code is used to uniquely identify each Configuration Manager site, it is especially important that these codes be assigned and tracked by the Configuration Manager central site administrators.


Hardware, software, network

Document hardware, software, and network information for each server that might be assigned a site role in your Configuration Manager site hierarchy.

For example, you should document at least the following information from each server that will be part of your Configuration Manager 2007 hierarchy:

  • Processor type and speed

  • Amount of RAM installed

  • Disk and array controller configuration and characteristics, including size, MB of cache, and the drive models and types (for example, ultra-wide SCSI, 18 GB, 7200 RPM)

  • Platform operating system, version, and language

  • Whether the Windows Cluster service or Windows Network Load Balancing Service is enabled

  • Relevant software applications located on servers, including antivirus software


See Also