[cisco-voip] Changing ou= within AD, its effect on CCM and Unity

[Voll, Scott]

What ever you do........ DON:T MOVE THE ADMINISTRATOR!!!!!!!  Found out
the hard way.  Sysadmin moved to different OU and everything started to
break.  TAC case opened and we troubleshot this issue all the way until
they asked if the administrator account had been moved...... I then
found out from the server group they did.  Moved it back and all was
good.

 

With all that being said.  So long as you don't move the Administrator /
service related accounts you should be fine.  You will need to change
your search to include the whole tree, but that is as easy as
reinstalling the plug in.  Unity doesn't care. But you might have to
rerun permissions wizard but I'm not sure.

 

We are AD 2k3 / CM 4.1.3 / Unity 4.0.5 / IPCCx 4.0.5

 

Scott

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jeff Anderson
Sent: Monday, January 08, 2007 1:18 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Changing ou= within AD, its effect on CCM and
Unity

 

I have a client who is wondering the effects of moving users out of the
default ou= within AD and putting them into different groups (They
asking this because they want to start applying group policy). They are
running CCM 4.1.3 and are AD integrated. They also have UM unity 4.x.

 

Any assistance on this matter would be much appreciated.

 

Thanks,

 

Jeff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070108/3747180e/attachment.html