My previous blog entry “Anatomy of a SIP Domain Change” looked at the user impact and process of changing the domain portion (right-hand-side) of a Lync user SIP addresses. This blog entry will describe the user experiences when the left-hand-side is changed (i.e. the user name portion before the @ sign). Changes to the left-hand-side usually occur when there are changes to user name formats, or a user has a name change that affects the user name portion of the SIP Address (e.g. after a life event such as marriage).
Changing a SIP address is not an exact science. This blog post details some lessons learned after the left-hand side of the SIP address changes based on testing that fellow MVP Pat Richard and I have done. Many of the experiences are the same as when the right-hand-side (domain portion) of the SIP address change; but there are some important differences.
The user impact is best described with two sample Lync users:
LyncUserA: the Lync user whose SIP address has changed (the user name portion).
LyncUserB: another Lync user with LyncUserA in their contact list.
Here are 6 of the most significant things you need to know about changing the left-hand side of a SIP address:
#1] Scheduled Meetings will be Break
Much like changing the right-hand side (domain portion) of the SIP address will cause existing Lync Meetings any Lync user had scheduled before the SIP change to break after the SIP change, the same holds true for SIP address changes involving the left-hand side (aka user name portion). Users will have to be notified that after the new SIP address comes into affect they will need to recreate any previously scheduled meetings.
In Lync 2013 here is what a Lync user will experience when attempting to join a meeting that was previously scheduled by a Lync user whose SIP address changed:
#2] After a SIP Address Change the Lync User is Automatically Signed-Out of their Existing Lync Client Sessions
- In our example, the Lync server closes any active Lync client sessions being used by LyncUserA
- This holds true for multiple client types
- The forced sign-out happens within 30 seconds and appears to the user in the Lync client as follows:
#3] The Lync Client Sign-In Address Must be Updated for the User to Sign Back In
- This is probably best accomplished by instructing users to manually update their SIP Address before signing back in
- In our example, LyncUserA must manually update his/her SIP address in their Lync clients to sign-in again
- No client or server side address book change can make this change (or is necessary), however the change could be made without asking the user to do if:
- the user SIP address is changed on the client computer. This can be done with a registry key (via a GPO, script, etc…). In the Lync 2010 client this was the ServerSipUri registered value at HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient.
- the Lync client must be restarted.
- If the new SIP address does not match the email address in the default Outlook profile, their could be integration issues with Exchange.
- If the new SIP address (with the new left-hand-side) does not match the users UserPrincipleName (UPN) in Active Directory, the user will be prompted for credentials on sign-in, and they must use the DOMAIN\username format (i.e. not the sipUser@domain.com format). For more information and a screen shot see “Users will be Prompted for Credentials on Sign-in After the Change” in the blog post Anatomy of a SIP Domain Change.
#4] Other Lync Users will see “Presence Unknown” for a Lync User Contact whose SIP Address has Changed (the user name portion)
- In our example, in the contact list of LyncUserB the Presence of LyncUserA will change to “Presence Unknown” within 2 minutes and the SIP address for LyncUserA is not automatically updated.
- This holds true even after LyncUserA signs-in again (after being forced to sign-out because of the SIP address change)
- Here is what a Lync user will see for another Lync contact whose SIP address was changed (left-hand side):
#5] Lync Users need to Sign-Out and Sign-In Again to Update their Contact Lists
- In our example, LyncUserB must sign-out and sign-in again to have the SIP address change for LyncUserA reflected in their contact list. This is also necessary for LyncUserB to see the Presence of LyncUserA and communicate with them.
- Even if an address book update is forced on the server side and the client side, LyncUserB will not display the correct SIP address and presence until they manually sign-out and back into the client.
- Specifically, in an attempt to have the SIP change of LyncUserA automatically updated in the contact list of LyncUserB, here is what was tried on the Lync server side:
- The left-hand-side of a LyncUserA’s SIP address was changed.
- Waited 1 minute (the default time for the User Replicator configuration to update the Lync SQL db’s from AD)
- Forced an Address Book update on the server (i.e. Update-CsAddressBook –verbose)
- Waited +2 hours – no update
- It does not matter whether LyncUserA has signed back in after the SIP change (after being forced to sign-out); the new SIP address and presence is not updated in the contact list of LyncUserB until LyncUserB signs-out and back-in.
#6] After the SIP Address Change other Lync Users Cannot Communicate
- LyncUserB (and all other Lync users) cannot communicate with LyncUserA when the Presence of LyncUserA is “Presence Unknown”
- After LyncUserB signs-out and signs-back in, LyncUserB can communicate with LyncUserA
Lastly, for some tips on setting the SIP address in the Lync Management Shell see the Microsoft NetHop article: Modify the SIP Address of an Enabled Lync Server User. I hope all this has made your adventures in changing SIP addresses more clear!