<div>1. It would depend on the exact process that was used to migrate. To get the existing users to show up as bulk integrated, take a look at this doc:</div><div><br></div><div><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/user_mac/guide/8xcucmac105.html#wp1074612">http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/user_mac/guide/8xcucmac105.html#wp1074612</a>
</div>
<div><br></div><div>2. No, see design guide:</div><div><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg040.html">http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg040.html</a></div>
<div><br></div><div>"<span style="background-color:rgb(255,255,255);font-family:Arial,Helvetica,sans-serif;font-size:12px;text-align:left">To protect the integrity of data in the LDAP directory, you cannot use Connection tools to change any of the values that you import."</span></div>
<div><span style="background-color:rgb(255,255,255);font-family:Arial,Helvetica,sans-serif;font-size:12px;text-align:left"><br></span></div><div><span style="background-color:rgb(255,255,255);font-family:Arial,Helvetica,sans-serif;font-size:12px;text-align:left">3. Yes, see design guide:</span></div>
<div><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg040.html">http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg040.html</a></div><div><br class="Apple-interchange-newline">
</div><div><span style="background-color:rgb(255,255,255);font-family:Arial,Helvetica,sans-serif;font-size:12px;text-align:left"><br></span></div><div><span style="background-color:rgb(255,255,255);font-family:Arial,Helvetica,sans-serif;font-size:12px;text-align:left">"</span><span style="background-color:rgb(255,255,255);font-family:Arial,Helvetica,sans-serif;font-size:12px;text-align:left">When the LDAP user account for a Connection user is disabled or deleted, or if an LDAP directory configuration is deleted from the Connection system, the following occurs:</span></div>
<a name="wp1057472" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pNF_NumFirst" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:7px;margin-left:0.25in;margin-right:0em;margin-top:0px;text-align:left;background-color:rgb(255,255,255)">
<b>1. </b><img src="http://www.cisco.com/en/US/i/templates/blank.gif" alt="" width="10" height="2" border="0" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; border-image: initial; ">Initially, when Connection users try to sign in to a Connection web application, LDAP authentication fails because Connection is still trying to authenticate against the LDAP directory.</p>
<a name="wp1071949" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pB2_Body2" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:6px;margin-left:0.25in;margin-right:0em;margin-top:1px;text-align:left;background-color:rgb(255,255,255)">
If you have multiple LDAP directory configurations accessing multiple LDAP user search bases, and if only one configuration was deleted, only the users in the associated user search base are affected. Users in other user search bases are still able to sign in to Connection web applications.</p>
<a name="wp1071859" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pNN_NumNext" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:7px;margin-left:0.25in;margin-right:0em;margin-top:0px;text-align:left;background-color:rgb(255,255,255)">
<b>2. </b><img src="http://www.cisco.com/en/US/i/templates/blank.gif" alt="" width="10" height="2" border="0" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; border-image: initial; ">At the first scheduled synchronization, users are marked as "LDAP inactive" in Connection.</p>
<a name="wp1071898" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pB2_Body2" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:6px;margin-left:0.25in;margin-right:0em;margin-top:1px;text-align:left;background-color:rgb(255,255,255)">
Attempts to sign in to Connection web applications continue to fail.</p><a name="wp1071766" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pNN_NumNext" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:7px;margin-left:0.25in;margin-right:0em;margin-top:0px;text-align:left;background-color:rgb(255,255,255)">
<b>3. </b><img src="http://www.cisco.com/en/US/i/templates/blank.gif" alt="" width="10" height="2" border="0" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; border-image: initial; ">At the next scheduled synchronization that occurs at least 24 hours after users are marked as "LDAP inactive," all Connection users whose accounts were associated with LDAP accounts are converted to Connection standalone users.</p>
<a name="wp1071779" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pB2_Body2" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:6px;margin-left:0.25in;margin-right:0em;margin-top:1px;text-align:left;background-color:rgb(255,255,255)">
For each Connection user, the password for Connection web applications and for IMAP email access to Connection voice messages becomes the password that was stored in the Connection database when the user account was created. (This is usually the password in the user template that was used to create the user.) Connection users do not know this password, so an administrator must reset it.</p>
<a name="wp1074040" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pB2_Body2" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:6px;margin-left:0.25in;margin-right:0em;margin-top:1px;text-align:left;background-color:rgb(255,255,255)">
The numeric password (PIN) for the telephone user interface and the voice user interface remains unchanged.</p><a name="wp1073349" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pB1_Body1" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:6px;margin-left:0em;margin-right:0em;margin-top:1px;text-align:left;background-color:rgb(255,255,255)">
Note the following regarding Connection users whose LDAP user accounts were disabled or deleted, or who were synchronized via an LDAP directory configuration that was deleted from Connection:</p><a name="wp1073358" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pBu1_Bullet1" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:7px;margin-left:0.25in;margin-right:0em;margin-top:0px;text-align:left;background-color:rgb(255,255,255)">
•<img src="http://www.cisco.com/en/US/i/templates/blank.gif" alt="" width="19" height="2" border="0" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; border-image: initial; ">The users can continue to sign in to Connection by phone during the period in which Connection is converting them from an LDAP-synchronized user to a standalone user.</p>
<a name="wp1073359" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pBu1_Bullet1" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:7px;margin-left:0.25in;margin-right:0em;margin-top:0px;text-align:left;background-color:rgb(255,255,255)">
•<img src="http://www.cisco.com/en/US/i/templates/blank.gif" alt="" width="19" height="2" border="0" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; border-image: initial; ">Their messages are not deleted.</p>
<a name="wp1073363" style="font-family:Arial,Helvetica,sans-serif;font-size:13px;text-align:-webkit-left;background-color:rgb(255,255,255)"></a><p class="pBu1_Bullet1" style="font-family:Arial,Helvetica,sans-serif;font-size:12px;margin-bottom:7px;margin-left:0.25in;margin-right:0em;margin-top:0px;text-align:left;background-color:rgb(255,255,255)">
•<img src="http://www.cisco.com/en/US/i/templates/blank.gif" alt="" width="19" height="2" border="0" style="border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; border-image: initial; ">Callers can continue to leave messages for these Connection users."</p>
<div><div>
<br><div class="gmail_quote">On Tue, Apr 10, 2012 at 9:58 AM, Jeff Ruttman <span dir="ltr"><<a href="mailto:ruttmanj@carewisc.org" target="_blank">ruttmanj@carewisc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Greetings,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">A consultant migrated us from old Unity to Unity Connection. We are setup to LDAP sync with Active Directory once per day, and it works fine.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">New folks get synced into UConn and the LDAP Integration status is set TO integrate with LDAP. However the bulk of our users who were all migrated to UConn have LDAP Integration status set to NOT integrate with LDAP. That seems like an
odd configuration to me.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p><u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Is the NOT integrate status due to the migration itself? Or could the consultant have chosen to have migrated users integrated?<u></u><u></u></p>
<p><u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>If a user is set TO integrate, will changing sync-ed fields in UConn in turn change them in AD?<u></u><u></u></p>
<p><u></u><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>If a user is set to NOT integrate, and we delete them out of AD, the user remains in UConn, right?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks<span><font color="#888888"><u></u><u></u></font></span></p><span><font color="#888888">
<p class="MsoNormal">jeff<u></u><u></u></p>
</font></span></div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div></div>