Figure 11 - 6 is an example
of a simple site configuration. This example shows one subnet, 192.168.1.0/24, and two sites,
Default - First - Site - Name and Chicago.
??‘
??‘
??‘
??‘
Figure 11-6
Part III: Working with PowerShell in a Production Environment
314
The subnet is associated with the Chicago site as shown in Figure 11 - 6 . This dialog box is reached by
selecting the Chicago site, and right - clicking to select Properties. Any servers that fall within the
192.168.1.0 - 192.168.1.255 are automatically part of the Chicago Active Directory site. Overlapping subnets
should not be associated with different sites because the server will not be able to correctly determine
its site membership and this causes errors.
The process Exchange uses to determine site membership was described earlier in this chapter. The
Microsoft Exchange Active Directory Topology service is responsible for checking and maintaining site
information in Active Directory for the server object.
One easy way to determine the Active Directory site a server thinks it belongs to is to use the support
utility called Nltest. Nltest is installed from the Windows Server installation disc, in the support
directory in the supptools.msi package. After installation you can run the following command at
a command prompt:
Nltest /dsgetsite
The output in this example for a server AD100 is:
C:\Program Files\Support Tools > nltest /dsgetsite
Chicago
The command completed successfully
Dedicated Exchange Sites
It was a common practice in Exchange 2000 and Exchange 2003 to create a dedicated Active Directory
site for large organizations.
Pages:
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452