TechNet
Export (0) Print
Expand All

Get-CalendarDiagnosticLog

 

Applies to: Exchange Online, Exchange Server 2016

This cmdlet is available in on-premises Exchange Server 2016 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.

Use the Get-CalendarDiagnosticLog cmdlet to collect a range of calendar logs. The Calendar Diagnostic logs track important calendar-related event data for each mailbox and can be used to troubleshoot calendar issues that occur in mailboxes. The logs track all calendar items and meeting messages.

For information about the parameter sets in the Syntax section below, see Syntax.

Get-CalendarDiagnosticLog -Identity <MailboxIdParameter> <COMMON PARAMETERS>
Get-CalendarDiagnosticLog -Identity <MailboxIdParameter> -LogLocation <String> <COMMON PARAMETERS>
COMMON PARAMETERS: [-Credential <PSCredential>] [-DomainController <Fqdn>] [-EndDate <ExDateTime>] [-Identity <MailboxIdParameter>] [-Latest <SwitchParameter>] [-MeetingID <String>] [-ReadFromDomainController <SwitchParameter>] [-ResultSize <Unlimited>] [-StartDate <ExDateTime>] [-Subject <String>]

This example retrieves the Calendar Diagnostic logs for Tony Smith's mailbox by using the subject Weekly development meeting.

Get-CalendarDiagnosticLog -Identity Tony -Subject "Weekly development meeting"

This example retrieves the Calendar Diagnostic logs for Tony Smith's mailbox from 6/1/2012 to 6/30/2012.

Get-CalendarDiagnosticLog -Identity Tony -StartDate "6/1/2012 6:00:00 AM" -EndDate "6/30/2012 5:00:00 PM"

This example retrieves the Calendar Diagnostic log data only for the most recent calendar item in Tony Smith's mailbox with a message subject of "Weekly development meeting".

Get-CalendarDiagnosticLog -Identity Tony -Subject "Weekly development meeting" -Latest

After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see Get-CalendarDiagnosticAnalysis.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Calendar diagnostics" entry in the Recipients Permissions topic.

 

Parameter Required Type Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.MailboxIdParameter

The Identity parameter specifies the mailbox user's name. This is the name that appears in Active Directory Users and Computers. This is also the user name that appears in Recipient Properties on the User Information tab. You can use the following values:

  • Alias

  • Display name

  • Domain\Account

  • SMTP address

  • Distinguished name (DN)

  • Object GUID

  • User principal name (UPN)

  • LegacyExchangeDN

LogLocation

Required

System.String

The LogLocation parameter specifies the location of the log files. The log files are located in the Exchange Logging directory.

Credential

Optional

System.Management.Automation.PSCredential

This parameter is available only in on-premises Exchange 2016.

The Credential parameter specifies the user name and password to use to access Active Directory Domain Services (AD DS).

This parameter requires you to create a credentials object by using the Get-Credential cmdlet. For more information, see Get-Credential.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

This parameter is available only in on-premises Exchange 2016.

The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.

EndDate

Optional

Microsoft.Exchange.ExchangeSystem.ExDateTime

The EndDate parameter specifies the end date of the date range.

Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2015 to specify September 1, 2015. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2015 5:00 PM".

Latest

Optional

System.Management.Automation.SwitchParameter

The Latest switch specifies whether to return calendar log data for only the most recent calendar item.

MeetingID

Optional

System.String

This parameter is reserved for internal Microsoft use.

ReadFromDomainController

Optional

System.Management.Automation.SwitchParameter

This parameter is available only in on-premises Exchange 2016.

The ReadFromDomainController parameter specifies that the calendar diagnostic information is read from a domain controller in the user's domain. If you use this parameter, multiple reads might be necessary to get the information.

ResultSize

Optional

Microsoft.Exchange.Data.Unlimited

The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.

StartDate

Optional

Microsoft.Exchange.ExchangeSystem.ExDateTime

The StartDate parameter specifies the start date of the date range.

Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2015 to specify September 1, 2015. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2015 5:00 PM".

Subject

Optional

System.String

The Subject parameter specifies the subject of the calendar item or meeting request. You can't use this parameter in conjunction with the MeetingID parameter.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Show:
© 2016 Microsoft