For those companies who are not able to align their User Principal Name (UPN) and SMTP (Email) address, such as Email: firstname.lastname@example.org and UPN: email@example.com, you may find that your Lync/Skype for Business client is unable to pull free/busy information from Exchange Online. This is due to the difference in ‘logins’ and values, so the below option gives the machine’s Lync client the ability to ‘trust’ these different domains, providing the ability to properly pull IM/Presence and Free/Busy information.
Special thanks to Edward P. for the following information!
- Sign-out from Lync and Delete Sign-in info
- Exit Lync and exit Outlook
- Delete the Tracing , CEIP and sip_user folders in this path %localappdata%\Microsoft\Office\15.0\Lync
- Delete the Lync registry key from HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\
Manually modify the TrustModelData registry value for this user, Open CMD in Elevated mode and run the cmd below. Note that the below is for Office Lync 2013 client, using the \15.0 registry key.
Reg Add “HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Lync” /V “TrustModelData” /T REG_EXPAND_SZ /D “ SMTPDOMAIN.com, SIPDOMAIN.com, online.lync.com, outlook.com, lync.glbdns.microsoft.com” /F
- Start Lync and sign back in
Note – If you are running in Exchange Hybrid Mode, you may have autodiscover.<emailDomain>.com pointing to on-premises Exchange. If this is the case, you will need to create and use a local PC HOSTS file, with autodiscover.<emailDomain>.com pointing to an IP address for this DNS A record: autodiscover.outlook.com, so your Lync client can connect into Exchange Online to properly pull the F/B information.
For those administrators who have multiple workloads/services that require migration into the cloud or Office 365, this article is for you. Special thanks to those who have helped in pulling this list together, to hopefully help those who have the challenge of migrating and moving into the Office 365 environment.
Microsoft Migration Guide for Exchange and Lync workloads here:
Third Party Migration Tools & Services:
For Lync Online Users and Administrators, you have found that your Session Initiation Protocol (SIP) sign-in address is required, such as firstname.lastname@example.org along with login information which is typically the same User Principal Name (UPN) Fully Qualified Domain Name (FQDN), such as email@example.com along with password. What many users and administrators don know is that during this login process by the Lync Client, the Lync Online Service generates and gives the logged on user an online end-user personal certificate, which is used as part of the authentication and connection process.
Note – This end-user certificate can be found within IE –> Tools –> Content –> Certificates –> Personal location. This certificate has a 180 day expiration and is required as part of the connection and authentication process. Any Online/On-Premises administrators who run a “tight ship” in regards to whether users can be granted personal certificates, need to keep this online certificate requirement in mind and not block this process, otherwise the Lync client will not be able to login to the Lync Online Services.
Login & Connection Requirements
For those using Office 365 Lync Online Services, who need to schedule meetings but are not using Outlook 2007/2010 or 2011 for Mac, you can use the “Web Scheduling” services to get these meetings created. Outlook is typically used, via the Lync 2010 Client Outlook Add-In, to create these Lync Online Conferences. However for users using OWA and/or not using Outlook, you can use the Lync Online “Web Scheduler” to create these meetings.
Lync Online Web Scheduler: https://sched.lync.com
Sample Web Scheduler – Create Meeting
For admins who must update their client PCs with the Lync 2010 client, they have questions regarding how the existing BPOS Office Communications Online (OCO) registry settings will be managed and possibly cause connection problems with the Lync client. Since BPOS manually configures Outlook, Communicator and other applications, Communicator is hard-coded to point to BPOS OCO for connectivity.
Managing IM Client Connection Settings
- Use the O365 Desktop Setup tool, which deletes these manually configured BPOS OCO registry entries and sets the client to use automatic configuration.
- This option assumes the Lync AutoDiscover DNS records are in place.
- Don’t use the O365 Desktop Setup tool, and edit these registry keys manually to point to the O365 Lync Online servers.
- You would point the internal and external server to sipdir.online.lync.com:443
As BPOS tenants start to Transition into Office 365, tenants using the BPOS Office Communications Online Instant Messaging services ma have heard that in certain conditions users can start using Lync Online 365. This thinking is primarily due to BPOS and Office 365 Transition emails which state that users can start upgrading their Communicator clients to Lync 2010, so they can be ready for the Transition and to provide the ability to use Lync Online, which requires the Lync 2010 client.
Depending on where you are in the BPOS Transition process, you may be able to use Lync Online today. Please review the below scenarios to determine whether you are a candidate for using Lync Online now or whether you will need to wait until the full BPOS to Office 365 Transition process completes:
Scenario 1: Not Scheduled for Transition
- Condition: BPOS tenant has not been scheduled for Transition, so their BPOS objects are not synchronized into Office 365, therefore usage of the Lync Online Services is not yet available.
- Result: In this scenario users can only use the BPOS Office Communications Online (OCO) Instant Messaging services.
Scenario 2: Scheduled for Transition
- Condition: The BPOS tenant has been scheduled for Office 365 Transition with the tenant’s objects, such as users, contacts, groups and domains synchronized into Office 365. The BPOS users have access into Office 365 using their synchronized accounts, however the tenant has not yet been upgraded into Lync Online.
- Result: In this scenario users can connect to either BPOS OCO or Lync Online. If users connect to Lync online, they can only chat with others using Lync Online. Similarly users continuing to use BPOS OCO will only be able to chat with other OCO users). Note that any users who use Lync Online will find their contact list will not be populated.
Scenario 3: Scheduled for Transition and Lync Upgraded
- Condition: The BPOS tenant has been scheduled for Office 365 Transition and the tenant’s objects, such as users, contacts, groups and domains synchronized into Office 365. The BPOS users have access into Office 365 using their synchronized accounts, and they have been upgraded into Lync Online environment.
- Result: In this scenario users can use either the Lync 2010 or Communicator2007 client in the Lync Online environment. User contacts will be populated in both clients, and they can communicate with users regardless of what client they are using, with all users now using the Lync Online service.
Scenario 4: Transitioned to Office 365
- Condition: Fully transitioned into Office 365
- Result: In this scenario the Lync 2010 client is the only supported client, now using Lync Online 365.
Net-Net: As BPOS tenants are moved from the OCO to Lync Online environment, they can start using the Lync 2010 client. Lync Online supports the Lync 2010 client and the Communicator 2007 client, however Communicator will be blocked from connecting into Lync Online ~5 days after the BPOS tenant transition has completed. If users move forward into Lync Online BEFORE the OCO to Lync Online upgrade has been performed, Lync Online Users will not have their contacts and will need to recreate them, at least until the OCO to Lync Online upgrade has completed, at which point the BPOS contacts now show up in Lync Online through the client. If tenants and/or users manually move into Lync Online ahead of the official OCO to Lync Online Service upgrade, BPOS OCO and Lync Online users are considered in a separate island, meaning OCO and Lync Online users cannot communicate with each other. If a BPOS tenant admin wants to allow users to move forward into Lync Online ahead of the service upgrade, all users should make the move, otherwise they will not be able to communicate with others, those who may have stayed in the BPOS Office Communications Online (OCO) environment.
Using Office 365 online services allows you to leverage one or more of these services while working. For example, while logged into Lync Online using the Lync 2010 client, you can see Presence information about others in your online company within SharePoint Online. These presence jelly-beans provide a way to see whether a user is online, offline, busy, etc and also to quickly start an IM conversation. This cross-service functionality also extends into Messaging as well, where Presence and IM conversation capabilities can be used within Outlook Web Access (OWA) and/or Outlook. To understand how this cross-service functionality works and how the Lync Client can view Presence and provide IM capabilities, the following shows the inner-workings of this client-side operation: