![]() ![]() ![]() Second, you might need to remove the user’s Skype license in the Office 365 Admin Center and then re-add it before the address fields will update. Set-CsUser -Identity -SipAddress much easier than editing AD attributes. (Thanks to a helpful technician at Microsoft for the Get-CSOnlineUser tip.)įirst, if you still have a Lync server on-premises, you can run this cmdlet to accomplish the same thing: I fixed the SIP address in these three attributes:Īfter syncing these changes to Office 365 and waiting a little while, the user was finally able to log into Skype. To fix this, I opened her account in Active Directory Users and Computers (with advanced features turned on) and accessed the Attribute Editor tab. The SIP address in Exchange is automatically updated by the Lync server, but changing it in the EMC doesn’t automatically change it in Lync. When a username absolutely has to be changed, the established procedure is to ignore the SIP address in the Exchange Management Console, to remove the user from the Lync server and then re-add her from the directory. OnPremSipAddress : : : former last name was still showing up in these SIP address fields! When her name was changed, someone changed her SamAccountName, UserPrincipalName, PrimarySMTPAddress, and even her SIP address as it appeared in our on-premises Exchange server, but they hadn’t changed her SIP address in the Lync 2010 console. Running “Get-CsOnlineUser -Identity | fl” showed something very interesting. Her displayname, email address, and username had all been changed to match, and we usually try to avoid changing usernames just for this reason. AI-powered Graphical Analytics Get insights into any report and understand the data better in a visually appealing manner. Multi-tenant Support Easily manage multiple office 365 tenants from a single window. There was one fact that kept nagging at me and I was sure it had to be related: She had changed her name a few months before the migration to SfB. Automatic Schedule Schedule one or more reports to run automatically at the configured time and delivered straight to your preferred mail-ids. >I uninstalled Lync and Office 2010 and installed Office 365 from the portal. >I wiped all of the locally cached Skype data from her Windows user profile and from the registry. >I reset her password and performed a manual sync from the on-premises AD. >I verified her UserPrincipalName and Skype user name in the Office 365 Admin Center. >I tried hardcoding the server names to :443. ![]() >I verified that the username, password, and domain was correct. Here are a few of the steps I attempted to fix the problem:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |