Erwin Bierens

Sharing Knowledge

DNS configuration is preventing you from presenting content

It looks like the file is not automatically updating after DNS changes. Some users will get the following error: You can solve this by deleting the “EndpointConfiguratation.cache” file. Sign out of Skype for Business Click File Exit Open File Explorer Go to “C:/Users//AppData/Local/Microsoft/Office/16.0/Lync/sip_@sipdomain.com” Select File: EndpointConfiguratation.cache and delete it. Launch Skype for Business client and sign in. When you have a older version of Office running change the 16.

Cloud Connector Edition Upgrade Issues

Since i was facing some isssues last time with upgrading our company Cloud Connector Edition it’s a good thing to keep old installers (check below for Archive). We had the CCE 1.4.2 version running, due to some accounting issues the upgrade to 2.0.0 never has started. You can use Set-CcCredential -AccountType TenantAdmin to set the new global admin account. (Global admin role required for 1.4.2, from 2.0.0 and newer Skype Admin role is required) So after setting the right O365 account i tried to start upgrading the appliance.

Let’s Encrypt and Skype for Business

For my home lab I’m using the free certificates from Let’s Encrypt (Let’s Encrypt is a free, automated, and open Certificate Authority). The certificates from them have 1 big limitation, they are only valid for 3 months but you can renew them “almost” automatically. As explained In my blog last week about “Skype for Business environment running with just one public IP” I’m running my Reverse Proxy with IIS ARR (Application Request Routing).

What’s fixed in Cloud Connector Edition 2.0.1

In Cloud Connector Edition 2.0.1, the following fixes were made: Restarting Virtual Machines sometimes caused the service to stop if the restart order determined by Hyper-V was incorrect. This has been fixed. Calls for download security checks in remote PowerShell sometimes caused calls to the New-CsOnlineSession cmdlet to fail. This issue has been fixed. During automatic updates, switching to a new version sometimes caused the running version to fail. This issue has been fixed

Skype for Business environment running with just one Public IP

For quite some time I’m running a home lab, first on a big server (HP Proliant DL360) and since beginning of this year I have a Intel Nuc, saves a lot of energy costs 😂 Domain Controller and CA on Windows 2016 Core Edition Skype for Business Front-End Server on Windows Server 2012r2 standard SQL 2014 std for monitoring and persistent chat on Windows Server 2016 Exchange 2016 on Windows Server 2016 Skype for Business Edge on Windows Server 2016 IIS ARR (Reverse Proxy) on Windows 2016 PBX on Windows Server 2016 This lab was great for testing purposes but the problem was always, no connection to the outside world with Skype because of the requirement for at least 2 external IP’s with the use of Skype for Business.