Category: Windows Server 2012 Essentials

[This post comes to us courtesy of Swapnil Rane from Commercial Technical Support]

This post will reduce your efforts to identify which log to refer to and where to find it. This can be very useful when you are troubleshooting issues on an Essentials server. We have compiled a list of important logs and their associated wizards below. There can be issues where we may have to refer to multiple logs.

Server-side Logs:

In Windows Server Essentials 2012 and 2012 R2, the location of the log files is under %programdata%MicrosoftWindows ServerLogs.

Service Integration Log Files:

O365/On-Premise Exchange/Intune

 

SharedServiceHost-EmailProviderServiceConfig.log

Windows Azure Backup

 

OnlineBackupGettingStartedWizard.log

Backup Log Files:

Server Backup Configuration wizard

SBCW.log

Server Backup restore wizard

ServerFFR.log

Client Backup Feature server side log

Backup-<date>.log

Client backup database cleanup

RunTask-BackupCleanup.log

Client backup database checker

RunTask-Consistency check

Storage and Devices Log Files:

User/Device management feature

SharedServiceHost-ManagementServiceConfig.log

Storage features

Storageservice.<date>.log

Storage related feature

Storageutil.<date>.log

Azure Backup Log Files:

Location: C:Program FilesWindows Azure Backup AgentTemp

Azure Backup Logs

CBEngineCurr.errlog

Failed Azure Backup Logs

LastBackupFailedFile#####.txt

Other Helpful Log Files:

DC Promo

DCPromo_date.log

Health evaluation schedule task

RunTask-AlertEvaluation.log

Macintosh Clients Status update

RunTask-MacintoshStatusReport.log

Server DNS status

ServerBeacon.log

Customer Experience Improvement

RunTask-SaveCustomerExperienceImprovementProgramData.log

Program and Service Quality Measurement Log Files:

CA Role installation

CA_ROLE_INSTALL.log

Media pack installation (2012 R2)

MediaPackInstalltionWizard.xxxx.log

Media Service (Specially with RWA)

MediaStreamingProvider.log

O365 (Assign/Un-assign Accounts)

TaskStatus-OIMAddin.log

 

Client-side Logs:

The client-side log files are located in the folder %programdata%MicrosoftWindows Serverlogs. They are as:

Client Deployment

ClientDeploy.log

Client package installation Failures

ComputerConnector.log

Client backup restore mount driver

BackupDriverInstaller.log

Client operation for File history Sync

ClientOperator.log

Main log for client launch pad

LaunchPad.log

Password synchronization feature in AAD   

PasswordSyncClientAlerts.log

Add-in feature on client

RunTask-Add-in Management.log

Health evaluation schedule task

RunTask-AlertEvaluation.log

Client Backup scheduled task

RunTask-ClientComputeBackkup.log

Connector uninstall cleanup task

RunTask-Connector cleanup.log

Update health definition file from server to client task

RunTask-HealthDefinitionUpdate.log

RDP feature for RWA

RunTask-RDP Group Configuration.log

Client VPN connectivity issues

RunTask-VPN Routes Repair.log

Client network status update

ServerLocator-<date>.log

Client deployment API call (Client deployment fails)

Setupapi.dev.log

Health alert feature

SharedServiceHost-HealthServiceConfig.log

The above logs should be able to guide you through the process of troubleshooting effectively on Essentials relevant issues.

[This post comes to us courtesy of Swapnil Rane and Rituraj Choudhary from Global Business Support]

This post explains how to increase the logging level for the individual components of Server Essentials role for troubleshooting purposes. In order to accomplish this, we need to modify the Logging.config file. This file can be located at C:Program FilesWindows ServerBin on a Windows Server 2012 Essentials machine. On a Windows Server 2012 R2 Essentials this file is present at C:WindowsSystem32Essentials.

Make sure to save a backup copy of the file before modifying it. You need to change the ownership of Logging.configfile and give the user adequate permissions to save any modifications to it. You may use the following commands on an elevated Command Prompt to make modifications to the file:

For Windows Server 2012 R2 Essentials:

takeown /f C:WindowsSystem32EssentialsLogging.config
icacls C:WindowsSystem32EssentialsLogging.config /grant administrators:F
icacls C:WindowsSystem32EssentialsLogging.config /setowner "NT ServiceTrustedInstaller"
notepad C:WindowsSystem32EssentialsLogging.config

For Windows Server 2012 Essentials:

takeown /f "C:Program FilesWindows ServerBinLogging.config"
icacls "C:Program FilesWindows ServerBinLogging.config" /grant administrators:F
icacls "C:Program FilesWindows ServerBinLogging.config" /setowner "NT ServiceTrustedInstaller"
notepad "C:Program FilesWindows ServerBinLogging.config"

The file Logging.config is now ready for editing. Search for the string level= and replace the string next to level= to All if it is set otherwise. For example:

<add level="Warning" name="ProviderFramework">
<listeners>
<add name="DefaultTraceListener" />
</listeners>
</add>

Change it as:

<add level="All" name="ProviderFramework">
<listeners>
<add name="DefaultTraceListener" />
</listeners>
</add>

Changing the level to Allenables verbose logging. There are other values that the level can be set to, but mostly verbose logging is preferred, and can be achieved as mentioned above.

When the issue is reproduced subsequently, the logs at C:ProgramDataMicrosoftWindows ServerLogsfolder should now contain verbose information.

Note: You may use the same procedure to enable verbose logging on the Essentials clients.

Contact

mattdubois.com Contact Form

Name
Email
Message

Yay! Message sent.
Error! Please validate your fields.
Updated August 2016 - Matt Dubois