Create high-level diagrams of your network topology that include any available information listed in the worksheet. The larger or more complicated your network topology, the more diagrams you will need. Later, after you make decisions about your Configuration Manager 2007 site structure and site system hardware requirements, you can determine whether any equipment upgrades or additions are necessary before your Configuration Manager 2007 deployment.
Network diagrams are also helpful when you create a representative test environment for a test lab or pilot project. Ensure that your network diagram is detailed and specific. If your network is large or complex, consider creating a similar but separate diagram for your domain structure and server topology.
Use the following guidelines to assist in preplanning tasks.
| Network topology | Example data needed, where applicable, and by location | Data Collected |
|---|---|---|
|
High-level WAN/LAN architecture |
Links, gateways, firewalls, extranets, virtual private networks, and perimeter networks |
|
|
Network size |
Number of servers and clients at each location |
|
|
Network bandwidth |
Link speeds and available bandwidth, including any known bandwidth issues |
|
|
Network usage and traffic patterns |
Categorize as Light, moderate, or heavy, and note times of day when network usage is heaviest (peak times) and scheduled times for backup and maintenance (nonpeak times) |
|
|
Network types |
Windows NT, Windows 2000, or Novell NetWare and other third-party network operating systems |
|
|
Network protocols |
TCP/IP, IPv6, NetBEUI, IPX/SPX, AppleTalk, DLC, and so on, and name resolution methods such as DNS and WINS |
|
|
IP subnet structure |
The Internet Protocol (IP) subnets on your network by subnet ID |
|
|
Active Directory site structure |
Active Directory organizational units, site names, trees, and forest |