306 Chapter 9: Planning
or its resources. Unity provides the necessary authentication facilities for subscribers
to access its resources, such as Windows authentication for web access, and CoS for
the TUI and CPCA.
Performing Site Surveys
Make sure that your site surveys account for everything necessary to accommodate a Unity
deployment. If you have not updated your site survey forms in a while, now is a good time
to do so. Unity is a convergence product, so you need to survey both the telephone or voice
aspects of a site and the messaging infrastructure aspects.
Your physical site survey should include the physical space, including all the necessary
power, network connectivity, security, and air conditioning criteria that you normally would
look for with any server deployment.
If Unity is connecting to a physical circuit-switched PBX, inventory this switch to make
sure that it can support Unity’s voice-connectivity requirements, including integration and
voice ports. Verify that it has both physical capacity and system capacity. Determine
whether a software upgrade of your switch is required to support a second voice-messaging
system. If you must run voice lines for voice ports, make sure that you have rack space and
patch panel space available for them.
If Unity is connecting to CallManager, make sure that you have sufﬁcient network connec-
tivity. You can reference the CallManager product documentation to determine exactly how
much bandwidth you need between CallManager and Unity (see the information on device
weights). However, on a LAN, you should use no less than 100 Mbps full duplex.
Identify all messaging servers, domain controllers, and name resolution hosts. Include their
server names, IP addresses, domain names, and physical location. At this point, you can
identify Unity’s partner messaging server (see Chapter 13, “Unity with Microsoft Exchange,”
for more information—Unity for Domino does not use a partner server). You also should
determine which DC and GC Unity will connect to, and you should know which name
resolution host it will use. As a rule of thumb, use the same DC, GC, and name server that
your messaging servers use. If you have multiple servers of each type, select one of each
type as a target for Unity. You can change your target later when you have a better
understanding of capacity.
Survey the total number of desktops if you are doing uniﬁed messaging. Make sure that you
understand which versions of software the Unity VMO can support. Note also that VMO
supports only Windows clients; it does not support Macs or UNIX boxes.
Survey the migration components, including any legacy voice-messaging systems.
Determine backup resources and management resources.