![microsoft lync 2013 books microsoft lync 2013 books](https://www.oreilly.com/library/view/easy-office-2013/9780133381245/graphics/01fig01.jpg)
- #Microsoft lync 2013 books how to
- #Microsoft lync 2013 books install
- #Microsoft lync 2013 books windows
The Office Web Apps Server published application must have the same host name for ‘ExternalURL’ and ‘BackendServerURL’.There are three main things to be aware of when publishing Lync and Office Web Apps Server: $certificate = "F7F6B300FE4D569FD598E1C9722571CF9AD780DD"Īdd-WebApplicationProxyApplication -Name ‘Lync Web Services’ -ExternalPreAuthentication PassThrough -ExternalUrl " -BackendServerUrl (" -ExternalCertificateThumbprint $certificateĪdd-WebApplicationProxyApplication -Name ‘Lync Lyncdiscover’ -ExternalPreAuthentication PassThrough -ExternalUrl " -BackendServerUrl (" -ExternalCertificateThumbprint $certificateĪdd-WebApplicationProxyApplication -Name ‘Lync Dialin’ -ExternalPreAuthentication PassThrough -ExternalUrl " -BackendServerUrl (" -ExternalCertificateThumbprint $certificateĪdd-WebApplicationProxyApplication -Name ‘Lync Meet’ -ExternalPreAuthentication PassThrough -ExternalUrl " -BackendServerUrl (" -ExternalCertificateThumbprint $certificateĪdd-WebApplicationProxyApplication -Name ‘Office Web Apps Server’ -ExternalPreAuthentication PassThrough -ExternalUrl ‘’ -BackendServerUrl ‘’ -ExternalCertificateThumbprint $certificate The Lync applications can be published manually like this – note the port 4443 on the Backend server URL: Even though we are not using Preauthentication, WAP cannot be setup without being configured as an ADFS Proxy.
#Microsoft lync 2013 books windows
Note that there is a dependency on a Windows 2012 R2 Preview ADFS farm.
#Microsoft lync 2013 books install
Install the certificate and run the configuration wizard to setup the server as an ADFS proxy. Setup the Web Application Proxy by installing the Remote Access Web Application Proxy role service as mentioned in the previous post. Lync applications cannot use Preauthentication and have to use Pass-through which lets the backend server provide authentication. Office Web Apps Server for PowerPoint sharing.Lync External Web Services (which includes the Lync Web App and Lync Scheduler).Lync has a few different namespaces that need to be published: the solution to a problem I had testing this on Azure IaaS Virtual Machines.fix to make Lync mobile work ( updated 19 July 2013 with information about Windows Phone 8 SNI support).why the Office Web Apps Server published URLs must be the same.
#Microsoft lync 2013 books how to
![microsoft lync 2013 books microsoft lync 2013 books](https://www.digitalcitizen.life/wp-content/uploads/2020/10/office2013_insideout-1.jpg)
Reason=Destination URI either not enabled for SIP or does notįor example, the preceding output states that the test failed because the specified user (that is, the “Destination URI”) either does not exist or has not been enabled for Lync Server. If the specified user is not able to make this connection, the Result will be shown as Failure, and additional information will be recorded in the Error and Diagnosis properties:ĭiagnosis : ErrorCode=4005,Source=, If the specified user is able to connect to the Address Book Service you will get back output similar to this, with the Result property marked as Success: Test-CsAddressBookService -TargetFqdn ""-UserSipAddress -UserCredential $credentialįor more information, see the Help documentation for the Test-CsAddressBookService cmdlet. You must then include that credentials object and the SIP address assigned to the account when calling Test-CsAddressBookService: $credential = Get-Credential "litwareinc\kenmyer" To run this check using an actual user account, you must first create a Windows PowerShell credentials object that contains the account name and password. For example: Test-CsAddressBookService -TargetFqdn "" To run this check using a test account, all you need to do is specify the fully qualified domain name (FQDN) of the Lync Server pool being tested. The Test-CsAddressBookService cmdlet can be run using either a preconfigured test account (see Setting Up Test Accounts for Running Lync Server Tests) or the account of any user who has been enabled for Lync Server.