Great.

  I also should mention the users in the system with single inbox are currently 
in AD 1.  We need to add single inbox users who are in AD 2.  Would it work to 
do what I had said but leave the exchange server in place for the current users 
who are in AD1?

Bill


From: bmead...@gmail.com [mailto:bmead...@gmail.com] On Behalf Of Brian Meade
Sent: Monday, June 20, 2016 3:11 PM
To: Hendrix, George (Bill) @ NSS
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Move to new AD environment for CUCM and Unity 
Connection 9.1

As soon as you delete the LDAP directory, it just marks all those users as 
inactive.  The users won't be deleted until the next 3:15am period that is at 
least 24 hours later.  If it finds a matching user ID in the new LDAP 
directory, the users will automatically become active again when you do a sync.

Worst case, you just re-add the original LDAP Directory configuration then do a 
full sync to make all the users active again if you can't get the new one to 
work.

On Mon, Jun 20, 2016 at 2:00 PM, 
<george.hend...@caci.com<mailto:george.hend...@caci.com>> wrote:
Hey guys,

  We currently have CUCM and Unity Connection 9.1 LDAP integrated to MS Domain 
1 in forest 1.  All users have user accounts pre-built in new MS Domain 2 in 
forest 2.  The users were all imported from the first domain/forest.  There is 
a trust between the forests.  Since the end state will be in forest 2, I was 
thinking we could just take this approach.

Disable LDAP integration.
Delete old LDAP directory integrations
Create LDAP integration with new AD domain.
Create new Exchange entry for new domain/forest for when users migrate 
mailboxes.

  Would this work?  I noticed when I attempted to delete some NOW unused LDAP 
directories in CUCM that it warns that any user imported in that directory will 
be deleted.  Does this mean when the user was first imported or if that was the 
last directory used for the user?  What if I point to the root, which contains 
all the OU directories?

Regards,

Bill


_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to