- Microsoft office live meeting 2013 client how to#
- Microsoft office live meeting 2013 client windows#
You must add these certificates to the policy that you created. Note There are some root certificates that are required by Windows.
Microsoft office live meeting 2013 client windows#
Windows Server 2008 R2 or Windows Server 2008Īdd a trusted root certification authority to a Group Policy object Therefore, you do not have to change individual computers. When you apply this policy, affected servers and clients trust only certificates that are in the Enterprise Root Certification Authorities store. If the server that hosts the UC application is a member of a domain, you can create a policy that causes the server to ignore the list of trusted certification authorities on the computer that hosts the UC client. Method 2: Configure Group Policy to ignore the list of trusted certification authorities on the computer that hosts the UC client For more information, click the following article number to view the article in the Microsoft Knowledge Base:Ģ93781 Trusted root certificates that are required by Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Windows 2000 Information There are some root certificates that are required by Windows.
Microsoft office live meeting 2013 client how to#
InformationTo learn more about how to automate the removal and installation of the third-party Trusted Root Authority certificates that are installed on Windows Server operating systems, click the following article number to view the article in the Microsoft Knowledge Base:Ģ801679 SSL/TLS communication problems after you install KB 931125 To do this, right-click a certificate, click Delete, and then click Yes to confirm that you want to remove the certificate. Remove trusted root certificates that you do not have to have. Under Console Root in the Microsoft Management Console (MMC) snap-in, expand Certificates (Local Computer), expand Trusted Root Certification Authorities, and then click Certificates. In the Add Standalone Snap-in dialog box, click Certificates, and then click Add.Ĭlick Computer account, click Next, and then click Finish. On the File menu, click Add/Remove Snap-in, and then click Add. Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003Ĭlick Start, click Run, type mmc, and then click OK.
If some trusted root certificates are not used in your environment, you should remove them from the server that is hosting the UC application. The removal of third-party Trusted Root Authority certificates could break secure client access to applications that are hosted on the Windows-based server. Warning You should use caution when you remove Trusted Root Authority certificates. Method 1: Remove some trusted root certificates
The following methods work around the issue that is described in the "Symptoms" section. Note For more information about the Windows Server operating system’s Schannel component and the limitations of its CTL, refer to the "Windows Server 2003," "Windows Server 2008 R2 and Windows Server 2008," and "Windows Server 2012" subsections of the "More Information" section. This issue occurs because of the design of the Schannel component of the Windows Server operating system that is hosting the UC applications. The TLS connection attempt fails with the error that is described in the "Symptoms" section. The UC client that requested the secure TLS connection does not receive certification authority information that matches the entries that are contained in its installed certification authority list. The CTL is truncated as per the design limitations of the Windows Server Schannel component. The UC server passes its certificate trust list (CTL) of installed certification authority information to the UC client that requests the secure TLS connection. This issue occurs because the UC server does not pass the correct certification authority information back to the UC client during the negotiation of the TLS connection. Microsoft Office Live Meeting 2007 clientĪdditionally, you receive the following Schannel warning and description of the issue in the Windows Server event log:
Less SymptomsĮach of the following applications cannot create a Transport Layer Security (TLS) connection with that application's unified communications (UC) peer: Lync Server 2013 Lync Server 2010 Enterprise Edition Lync Server 2010 Standard Edition Exchange Server 2010 Enterprise Exchange Server 2010 Standard More.