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.
As the distribution of Office 365 spreads accross the planet, the need for hybrid deployments rises. In many scenarios we find that environments are partly hosted on-prem and in the cloud. The reason for such deployments vary in some degree, and when it comes to Lync deployments it’s often due to enterprise voice which is not possible in the cloud(at the moment).
To implement a hybrid configuration where Lync resides on-prem and Exchange is hosted online, we have to do some configuration in the on-prem environment.
First, if the Lync environment is a Lync 2010 installation the minimum requirement is that the March 2013 server Update is installed on the Lync servers. In addition to this, a standalone server with Lync 2013 Administrative Tools has to be deployed in order to be able to connect with Office365. All PowerShell commands against the Online environment has to be executed on the server running Lync 2013 Admin Tools.
To enable Lync On-prem integration with Exchange Online, the first step is to make sure that federation is allowed(most environments already have open federation enabled):
Identity specifies a unique string value identifier for the hosting provider that you are creating (for example, “Exchange Online”). Values that contain spaces must be in double quotes.
Enabled indicates whether the network connection between your domain and the hosting provider is enabled. This must be set to True.
EnabledSharedAddressSpace indicates whether the hosting provider will be used in a shared SIP address space scenario. This must be set to True.
HostsOCSUsers indicates whether the hosting provider is used to host Office Communications Server or Lync Server. This must be set to False.
ProxyFQDN specifies the fully qualified domain name (FQDN) for the proxy server used by the hosting provider. For Exchange Online, the FQDN is exap.um.outlook.com.
IsLocal indicates whether the proxy server used by the hosting provider is contained within your Lync Server topology. This must be set to False.
VerificationLevel Indicates the verification level allowed for messages that are sent to and from the hosted provider. Specify UseSourceVerification, which relies on the verification level included in messages sent from the hosting provider. If this level is not specified, the message will be rejected as being unverifiable.
Check replication status to verify that the changes has replicated to the access edge server:
Wrote this blogpost in May when attending the Microsoft Ignite Conference in Chicago.
Should have been posted then, but I still think it’s relevant 🙂
As you all know, the Skype4B server upgrade can be done as an in-place upgrade from Lync 2013. However, there are things to consider.
If the server is a Lync 2010 server, there is no way to do an in-place upgrade. Migration is the only way.
Lync 2013 supports the in-place upgrade as long as you can schedule downtime because the services are removed during the process.
When it comes to the server OS, you would want to concider upgrading the server if you’re on WinSrv 2008 or 2008R2. The Skype4B server install will upgrade windows fabric to the latest version, but only on 2008R2.
Recommendation: Win2008 or 2008R2 should be upgraded to 2012R2.
Implication: The upgrade process to Skype4B will have to be done as a migration if your servers are on Win2008 or Win2008R2.
Incredibly useful post by Mark Vale(@unifiedvale) on how to recover from a corrupt CMS. Please do note the points in the article about making a backup of your Lync environment. You never know when you need it.
Nice post by Rune Stoknes on a recently discovered faulty patch from Microsoft on the Lync server.
This post proves why you should never rely on Windows Update to install your Lync patches. Always use the LyncServerUpdateInstaller that comes with the CU released for Lync/Skype4B.
Keeping your servers up to date is essential, and not only the application server parts but the OS and others as well. The other day I went with a Windows Update that also included a Lync Server security update. After a short while I would get feedback from users no longer being able to use the mobile client, and later I also got reports on the Web App not working.
This headset is an excellent choice if you require something a bit more advanced than most people 🙂 The features implemented in this headset makes it a great choice for both soft phone clients and mobile phones as well as for listening to music when you’re working.
One of my favourite functions is the Auto Answering feature which lets you answer an incoming call just by putting on your headset if its in the charging cradle or lying on your desk. It will answer any incoming call wether it’s to your soft phone client or mobile phone.