Nice post, should be carried out in every environment where internal certificates are in use. Having the Lync/Skype for Business service beeing interrupted every second year because of short term internal certificates is nothing else but annoying.
In my previous job as a hired consultant I generally wanted the Lync/Skype for Business servers to have certificates lasting beyond the two year default validity period. Why? Because I, along with the customer, would consider a Lync or Skype for Business solution to have a horizon stretching beyond two years – and therefore issuing a certificate that would expire only after two years would be meaningless.
Sometimes working with Lync and Skype for Business I see that the services are trying to contact other servers or localhost which returns an IPv6 address. If the service is set to run only on IPv4 the service will fail and not find the listening interface since it is not listening on IPv6. In these cases I do not disable IPv6 but prefer IPv4. This needs to be done in registry and a reboot is required after the change. Do not disable IPv6 on the network card because that will not work.
Here is a simple way to do it using PowerShell
Check the values below for other options
Type to re-enable all IPv6 components (Windows default setting).
Type 0xff to disable all IPv6 components except the IPv6 loopback interface. This value also configures Windows to prefer using IPv4 over IPv6 by changing entries in the prefix policy table. For more…
As you all probably know, Microsoft has enabled the possibility of having Dial-in PSTN Conferencing in Skype for Business Online. In order to do this, you either have to have an E5 license plan in O365, or you can purchase the add-on for PSTN Conferencing in your excisting E1 or E3 plan.
PSTN Conferencing is a very valuable add-on to the O365 Skype for Business as it will enhance the possibilities of joining meetings without having to use a client.
To read more about PSTN Conferencing, visit this site on Microsoft.com:
In this post I will try to keep you updated with the current releases and build numbers for Skype for Business 2015 Server.
As of now, there has been released five updates for Skype for Business Server 2015. The Microsoft download page is updated with the latest SkypeServerUpdateInstaller, so the link will always point to the most recent CU.
Januar 2019 Update – Build number 6.0.9319.537(CU8)
March 2018 Update – Build number 6.0.9319.519(CU7)
January 2018 Update – Build number 6.0.9319.514(CU6 HF1)
December 2017 Update – Build number 6.0.9319.510(CU6)
May 2017 Update – Build number 6.0.9319.281(CU5)
Be adviced: CU6 has been reported to break Web Conferencing Edge service due to updates to the .Net Framework.
Check out this TechNet article if you experience problems.
February 2017 Update – Build number 6.0.9319.277(CU4 HF1)
November 2016 Update – Build number 6.0.9319.272(CU4)
June 2016 Update – Build number 6.0.9319.239(CU3)
March 2016 Update – Build number 6.0.9319.235(CU2)
November 2015 Update – Build number 6.0.9319.102 (CU1)
Since November 2015 there has been issues with Missed Call Notification from Lync/S4B to Outlook.
There has been written many blogpost about this, but I will here try to summarize how to fix it – Until Microsoft release a permanent fix for the issue.
The following Windows Update’s are relevant for this issue.
I have been trying to solve this at several customers, but made a breaktrough today.
I have been searching for KB3101496 – Nothing to find!
Searched in Registry clearly shows that the patch is installed, but it’s not visible in Control Panel
Additional research pointet me in the direction of KB3114351.
Looking for KB3114351 in Control Panel showed that this patch was installed.
Did a Uninstall of this patch, with a following reboot.
After a reboot, the KB3101496 was again visible in Control Panel. Did a uninstall of this patch as well, following with a…
The WordPress.com stats helper monkeys prepared a 2015 annual report for this blog.
Here’s an excerpt:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 23,000 times in 2015. If it were a concert at Sydney Opera House, it would take about 9 sold-out performances for that many people to see it.
I came across this event on an Exchange 2013 CU9 server which I was configuring for a customer.
Searching for solutions to this event made me understand that this is something that’s been going on since Exchange 2013 Cu7. The fix is quite simple and does not have any impact on the Exchange system.
Simply disable the Bitlocker check on the drive where diagnostics root directory exists.
Open below file in notepad (run as admin):
C:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.Diagnostics.Service.exe.config
Change the parameter “DriveLockCheckEnabled” value=”True” to “DriveLockCheckEnabled” value=”False” and save the config-file.
<!– Settings used when checking Bitlocker state of the drive where the diagnostics root directory exists –>
<add key=”DriveLockCheckEnabled” value=”False” />
<add key=”DriveLockCheckInterval” value=”00:00:10″/>
<add key=”DriveLockMaxDuration” value=”00:04:00″/>
Restart MicrosoftExchangeDiagnostics service, and the error message is gone.
I was doing a migration between Exchange 2013 and Office 365 in a Hybrid configuration when I recieved the above error message. Couldn’t quite figure out why until I stumbled accross a forum thread that pointed me in the right direction.
This is what you have to check out and remediate if you have this error:
The ExchangeGuids of on-premise users are different to the ExchangeGuids of the corresponding users in Office 365.
Update the online user’s ExchangeGuid to match the on-premise ExchangeGuid and start migration.
This is a great post done by Skype4B enthusiast Mark Vale on Cloud PBX and Office 365 E5 which is to be launched in the US on December 1st 2015. I recommend everyone to read his thoughts and keep them in mind.