[cisco-voip] 2 Unity in one AD Domain

Aaron Kent Aaron.Kent at apptis.com
Thu Mar 10 10:39:09 EST 2005


We have digital networking and license pooling working great. The
problem I am running into is explaining to the AD administrator that he
can't go moving the object IDs around or renaming them; because I don't
know the effect it will have on Unity's performance.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Thursday, March 10, 2005 9:27 AM
To: Aaron Kent
Cc: cisco-voip at puck.nether.net; Voll, Scott
Subject: Re: [cisco-voip] 2 Unity in one AD Domain

I assume you are talking about the location object IDs in the locations

OU.  You really shouldn't have to know which of those corresponds to  
which server.  In the SA for each Unity server you can add a  
description for the local server.  That will allow you to tell easily  
which server a given subscriber is on.  As a matter of fact you want  
the locations OU to be the same for all Unity servers in your AD.  This

allows them to do digital networking, and neat things like addressing  
VMs to subscribers on a different server.

Scott, there is no problem whatsoever integrating multiple Unity  
servers to the same AD.
You can find the docs for Unity Networking at  
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/ 
net/index.htm.

-Ryan
On Mar 9, 2005, at 6:08 PM, Aaron Kent wrote:

Scott,

We did not realize what we had done until it was too late. Create an OU
called Unity, under that create locations of your sites, and under that
you can create containers for each servers object.

You can see that it generated a name for each servers object, but now it
is hard to figure out which is which. If anyone knows how to correct
this let me know. Also can we change the names of these objects without
causing hard to our Unity Servers?


<example_why.png>_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip




More information about the cisco-voip mailing list