[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-16

While it is possible to run the planning tool without documenting your existing and proposed IP addresses and Edge server FQDNs, its significantly harder to do so without configuration errors. For example, a common mistake is to reuse FQDNs from an existing Edge deployment for your Communications Server 2010 Edge deployment.

Note:
After you have run the planning tool and exported it to Topology Builder, it cannot be modified. You have to start over. This is another benefit of documenting your Edge environment.

Therefore, the recommended approach is to use the following figures to guide you through gathering the various FQDN and IP addresses you will enter into the planning tool. Documenting the current and proposed configuration helps by putting the values in context for your production environment and forces you to think about how you will configure coexistence and new features such as simple URLs, file shares, dedicated A/V conferencing servers, and and DNS load balancing.





    Figure placeholder: Data Collection Template for Communications Server 2010 Scaled Consolidated Edge (DNS Load Balanced) Environment
    Figure placeholder: Data Collection Template for Communications Server 2010 Single Consolidated Edge Environment