Infrastructure Requirements for Unity Deployment
Unity uses AD when deployed in the Exchange messaging environment. The corporate directory administrator must understand the implications of this before proceeding with actual deployment. Table G-3 includes the questions to ask the corporate directory administrator to ensure that the customer understands the infrastructure requirements to deploy Unity.
1 | Deploying Unity in the existing AD requires schema extensions. Is your corporate directory team aware of this change and approve it? To see the list of schema extensions that Unity makes to the AD schema, refer to the following URL: http://www.cisco.com/en/US/partner/products/sw/voicesw/ps2237/products_white_paper09186a00800875c5.shtml | |
2 | Extending the AD schema increases the size of the AD database. Did you plan for the extra size of the database? Refer to the following URL for information on AD capacity planning: http://www.cisco.com/en/US/partner/products/sw/voicesw/ps2237/products_white_paper09186a00800e4535.shtml | |
3 | Who has the schema master right to modify the schema on the directory? | Name: Role: Phone: E-mail: |
4 | Did you integrate the CallManager directory with this AD? | |
5 | Will the Unity system be collocated with the Exchange servers? | |
6 | How many users require remote access or other special access to Unity via a VPN, a dial-up connection, or another method? For instance, traveling users with laptops generally sync up with their messaging system via remote dialup, which makes streaming an issue because of bandwidth constraints. Indicate the number of mobile users who will use Unity. | VPN Dial-up Others |
7 | If you plan to deploy Unity at a central location, do you have remote sites that access Unity at the central site? If yes, what are the typical bandwidths? | Bandwidth __________________ |
8 | Specify on what operating system you want to install Unity. |
Comments/Notes
When you deploy Unity into an existing messaging network, you need to work with the corporate directory and messaging teams and brief them about Unity's dependency on the existing directory and messaging infrastructure.