

Instead of modifying the web.config file on each server, Exchange now uses the New-SettingOverride PowerShell cmdlet to set the IM server and IM certificate names. The following steps are where Exchange 2016 diverges from previous versions. This can be found using the Get-ExchangeCertificate PowerShell cmdlet. You will also need the certificate thumbprint that is currently assigned to IIS. \Program Files\Microsoft\Exchange Server\V15\Scripts\Configure-EnterprisePartnerApplication.ps1 -AuthMetadataUrl "" -ApplicationType Lync Unlike Skype, Exchange does not have a built-in PowerShell cmdlet to create a partner application, but a handy script is available in the “Scripts” directory where Exchange was installed. After instant messaging has been enabled via the policies, create a partner application for Skype inside of Exchange. Also, setting the OWA virtual directory like this across servers in multiple sites can take a while, so be patient. Yes, you are setting it to “Ocs”, which is the old name for Lync, which is the old name for Skype for Business.
#Certificate error mac skype for business how to#
Discover how to empower innovation from non-traditional developers with the Microsoft Power Platform. Unleash the Potential of Power Platform With a Center of Excellenceīusiness innovation often comes from within. Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingEnabled $true -InstantMessagingType Ocs You will need to enable the instant messaging and the type of instant messenger on the OWA mailbox policies and virtual directories: Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled $true -InstantMessagingType Ocs Next, let’s move onto the Exchange configuration. Finally, publish topology using Enable-CsTopoogy and verify there are no errors. Also, the port is somewhat arbitrary, is just has to be unique within a Skype pool and cannot be reused with other applications. If you do not know the site number, run Get-CsSite and retrieve the value of SiteId. New-CsTrustedApplication -ApplicationId OutlookWebAccess -TrustedApplicationPoolFqdn -Port 5199 New-CsTrustedApplicationPool -Identity -Registrar -Site 1 -RequiresReplication $false
#Certificate error mac skype for business full#
This can be accomplished using the following three commands: New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl ""


Now we need to create a partner application for Exchange as well as a trusted application pool with a trusted application. The XML document is often used to verify access to the service, but in this case we are wanting to point to the service itself. Notice the URL ends with “.svc” and not “.xml”.

The Skype for Business Server needs to know where to find the autodiscover service, and this is set using the following command: Set-CsOauthConfiguration -ExchangeAutodiscoverUrl "" The process here has not changed from previous versions and is well documented in TechNet and other blogs. The following outlines the pieces of information needed to configure the environment and their values in our mock scenario:Įxchange Autodiscover URL: įirst, let’s review the steps needed to configure the Skype for Business environment. Gone are the days of modifying web.config files to make way for managing this via a few simple PowerShell commands. While the process on the Skype for Business side has stayed the same, Microsoft has introduced a new way to configure the IM server and certificate on the Exchange side that is simpler and easier to manage. Recently I had to perform a familiar function: integrating Skype for Business with Exchange in order to allow IM and presence functionality inside of OWA (or “Outlook on the Web” as it is now known).
