[cisco-voip] CCM6 with AD integration - moving users to new ADdomain

[Justin Steinberg]

This has not been my experience on 6.1.

You should be able to disable ldap synch to the old Active Directory and
repoint to the new Active Directory.  Accounts will go to the inactive state
when you disable the old active directory, but as long as you point CM back
to the new Active Directory AND the usernames in CM match the usernames in
the new AD everything will sync back up and the CM user accounts will go
from inactive to active on the next sync.  Data such as device associations,
speed dials, etc will remain.

You just have to do all of this at the same time because you have to be
cognizant of the garbage process whenever you have accounts in the
'inactive' state. (i.e. If you leave them inactive for too long they will be
deleted and if this happens you will lose all of your associations.) For
more info on the garbage process, read the SRND.

Justin

On Sun, Jan 4, 2009 at 9:28 PM, James Buchanan <jbuchanan at ctiusa.com> wrote:

> Hello,
>
> To point to the  new structure, you'll have to delete what is there
> already and re-add it. This will result in all of the existing users
> being marked inactive. At this point, if you disable the LDAP System,
> you can manually delete the users. Then, you can setup everything again
> from scratch.
>
> Prior to any of this, you should be able to go under Bulk
> Administration, Users, Export Users to export the existing user settings
> with the phone association and profile associations. You should be able
> to do an Update Users after resyncing to put everything back.
>
> Sorry that there's no easy fix.
>
> Thanks,
>
> James
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of MILLS, Mark
> Sent: Sunday, January 04, 2009 7:24 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] CCM6 with AD integration - moving users to new
> ADdomain
>
>
> Hi,
>
> Our current CCM6 installation uses Active Directory syncronisation for
> all end users to a Windows domain.
>
> In the near future, due to company acquisitions, the Windows Admin
> groups are creating a new Windows AD domain and all users will be moved
> over to the new domain and the old one turned off.  The users will be
> keeping the same username format and their telephone details etc will be
> the same in the new AD structure that is being created.
>
> Does anyone have any experience on what this would do to the users in
> CCM, and how I would go about syncing against the new domain, but
> keeping all the users, profiles and preferences the same to cause
> minimum disruption to the end users?    Im hoping it will be as simple
> as pointing CCM at the new AD servers and it will figure everything out,
> but nothing is ever as simple as I hope  :)
>
> Thanks in advanced,
>  -  Mark
> "Warning:
> The information contained in this email and any attached files is
> confidential to BAE Systems Australia. If you are not the intended
> recipient, any use, disclosure or copying of this email or any
> attachments is expressly prohibited.  If you have received this email
> in error, please notify us immediately. VIRUS: Every care has been
> taken to ensure this email and its attachments are virus free,
> however, any loss or damage incurred in using this email is not the
> sender's responsibility.  It is your responsibility to ensure virus
> checks are completed before installing any data sent in this email to
> your computer."
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1869 - Release Date:
> 1/4/2009 4:32 PM
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090104/884c6568/attachment.html>