Exchange 2013 – Failed to detect the BitLocker state for EDS log drive 'C:\'

BitLocker is a feature in Windows Server 2012 (and newer) for encrypting the hard drive. Most organizations are not required to encrypt the data on the server hard drives and to my experience, very few organizations choose to do so unless they are forced to do so. Therefore, to the surprise of many of us, the Windows Event Log starts filling up with BitLocker related messages on the Exchange 2013 servers after installing Cumulative Update 7 (CU7) for Exchange Server 2013.

Read More

SharePoint - The service did not start due to a logon failure

Sometimes a minor detail can lead into severe side-effects, as is the case in this posting. Our client installed a new piece of software, and one of the installation steps generated a rather seemingly harmless question. The installation software asked if it can be allowed to update a GPO (Group Policy object) in Active Directory (AD). The unsuspecting IT staff member assumed this was fine and proceeded to make the changes required to make the software work.

Read More

Exchange – High Memory Utilization

Back pressure is a system resource monitoring feature of the Microsoft Exchange Transport service that exists on Microsoft Exchange 2013 Mailbox servers and Edge Transport servers. What this means is that the Exchange server monitors key resources, such as hard drive space and memory, and under pressure, can take action to prevent service unavailability. While this can prevent system resources from being completely exhausted, back pressure can cause service degradation.

Read More

VMware ESX/ESXi – Snapshot Age

VMware is a virtualization platform many of our clients use – both VMware ESX and ESXi. VMware allows hardware resources to be utilized better and deploys new servers with much less effort than ever before. With Intelligent Monitoring you will have easy access to all key VMware performance information including information on VMware performance, resource consumption, and snapshots – just to name a few.

Read More
Subscribe to monitoring
200 OK


The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.