Merge pull request MicrosoftDocs#3422 from MicrosoftDocs/chrisda

Chrisda to Master

Author: chrisda

exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticLog.md

@@ -22,7 +22,7 @@ For information about the parameter sets in the Syntax section below, see Exchan
 
 ### MeetingId
 ```
-Get-CalendarDiagnosticLog [-Identity] <MailboxIdParameter> -MeetingID <String> [-EndDate <ExDateTime>] [-Latest] [-StartDate <ExDateTime>] [-Subject <String>] [-EntryId <String>] [-ExactMatch <$true | $false>] [-ItemClass <String[]>] [-ItemIds <String[]>]
+Get-CalendarDiagnosticLog [-Identity] <MailboxIdParameter> -MeetingID <String>
  [-Credential <PSCredential>]
  [-DomainController <Fqdn>]
  [-LogLocation <String>]
@@ -42,6 +42,25 @@ Get-CalendarDiagnosticLog [-Identity] <MailboxIdParameter> -Subject <String>
  [<CommonParameters>]
 ```
 
+### ExportToMsg
+```
+Get-CalendarDiagnosticLog [-Identity] <MailboxIdParameter> -LogLocation <String>
+ [-Credential <PSCredential>]
+ [-DomainController <Fqdn>]
+ [-EndDate <ExDateTime>]
+ [-EntryId <String>]
+ [-ExactMatch <Boolean>]
+ [-ItemClass <String[]>]
+ [-ItemIds <String[]>]
+ [-Latest]
+ [-MeetingID <String>]
+ [-ReadFromDomainController]
+ [-ResultSize <Unlimited>]
+ [-StartDate <ExDateTime>]
+ [-Subject <String>]
+ [<CommonParameters>]
+```
+
 ## DESCRIPTION
 The output of this cmdlet contains the following information:
 
@@ -128,7 +147,40 @@ Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Ex
 Required: True
 Position: 1
 Default value: None
-Accept pipeline input: True
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+
+### -LogLocation
+The LogLocation parameter specifies the location to export the calendar items to .msg files. You can specify a local path, or a UNC path (\\\\\<Server\>\\\<Share\>). If the value contains spaces, enclose the value in quotation marks (").
+
+In the location you specify, a subfolder is automatically created for the specified mailbox that holds the exported calendar items. For example, if you specify the value "C:\\My Documents\\Calendar Export" to export calendar items from the mailbox of Shannon Steele, the .msg files are actually stored in C:\\My Documents\\Calendar Export\\[email protected].
+
+In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAnalysis cmdlet with the LogLocation parameter to analyze the exported .msg files.
+
+Note: Commands that use this parameter might fail if the calendar item doesn't have a title. If you receive errors when you use this parameter, run the command again and replace this parameter with redirection to a file (| Set-Content -Path "C:\\My Documents\\Calendar Export") or substitute the output to a PowerShell variable.
+
+```yaml
+Type: String
+Parameter Sets: ExportToMsg
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+```yaml
+Type: String
+Parameter Sets: MeetingId, MeetingSubject
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
@@ -147,7 +199,19 @@ Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Ex
 Required: True
 Position: Named
 Default value: None
-Accept pipeline input: True
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+
+```yaml
+Type: String
+Parameter Sets: ExportToMsg
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: True (ByPropertyName)
 Accept wildcard characters: False
 ```
 
@@ -158,10 +222,10 @@ Don't use this parameter with the MeetingID parameter, because the value of the
 
 ```yaml
 Type: String
-Parameter Sets: MeetingId
+Parameter Sets: MeetingSubject
 Aliases:
 Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-Required: False
+Required: True
 Position: Named
 Default value: None
 Accept pipeline input: False
@@ -170,10 +234,10 @@ Accept wildcard characters: False
 
 ```yaml
 Type: String
-Parameter Sets: MeetingSubject
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-Required: True
+Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
@@ -223,7 +287,7 @@ Use the short date format that's defined in the Regional Options settings on the
 
 ```yaml
 Type: ExDateTime
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
@@ -238,7 +302,7 @@ The EntryId parameter filters the results by entry ID. You can specify multiple
 
 ```yaml
 Type: String
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
@@ -263,7 +327,7 @@ The value of this parameter is ignored when you use the MeetingId parameter.
 
 ```yaml
 Type: $true | $false
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
@@ -280,7 +344,7 @@ You can only use this parameter with the MeetingID parameter.
 
 ```yaml
 Type: String[]
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
@@ -295,7 +359,7 @@ The ItemIds parameter filters the results by item ID. You can specify multiple v
 
 ```yaml
 Type: String[]
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
@@ -310,7 +374,7 @@ The Latest switch specifies whether to return calendar log data for only the mos
 
 ```yaml
 Type: SwitchParameter
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
@@ -320,27 +384,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -LogLocation
-The LogLocation parameter specifies the location to export the calendar items to .msg files. You can specify a local path, or a UNC path (\\\\\<Server\>\\\<Share\>). If the value contains spaces, enclose the value in quotation marks (").
-
-In the location you specify, a subfolder is automatically created for the specified mailbox that holds the exported calendar items. For example, if you specify the value "C:\\My Documents\\Calendar Export" to export calendar items from the mailbox of Shannon Steele, the .msg files are actually stored in C:\\My Documents\\Calendar Export\\[email protected].
-
-In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAnalysis cmdlet with the LogLocation parameter to analyze the exported .msg files.
-
-Note: Commands that use this parameter might fail if the calendar item doesn't have a title. If you receive errors when you use this parameter, run the command again and replace this parameter with redirection to a file (| Set-Content -Path "C:\\My Documents\\Calendar Export") or substitute the output to a PowerShell variable.
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -ReadFromDomainController
 This parameter is available only in on-premises Exchange.
 
@@ -382,7 +425,7 @@ Use the short date format that's defined in the Regional Options settings on the
 
 ```yaml
 Type: ExDateTime
-Parameter Sets: MeetingId
+Parameter Sets: ExportToMsg
 Aliases:
 Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False

exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticObjects.md

@@ -42,12 +42,18 @@ Get-CalendarDiagnosticObjects [-Identity] <UnifiedGroupOrUserMailboxIdParameter>
 ## DESCRIPTION
 Some of the more interesting properties that are returned in the results are:
 
+- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment has been received, 4 = The appointment has been cancelled, and 8 = the appointment is a forwarded appointment.
+
 - CalendarLogTriggerAction: The action that's taken on the item (for example, Create or Update).
 
 - ClientInfoString: The entity that made the change (for example, Client=OWA;\<AdditionalDetails\>, Client=WebServices;\<AdditionalDetails\>;, or Client=TBA;Service=MSExchangeMailboxAssistants;Action=ELCAssistant;).
 
+- MeetingRequestType: 1 = The meeting message is a meeting request, 65536 = The meeting message is a full update to an existing meeting, 131072 = The meeting message is an informational update to an existing meeting, 262144 = The meeting message is a silent update, 524288 = The update is outdated, or 1048576 = The meeting message is forwarded to a delegate, and the copy is marked as informational.
+
 - OriginalLastModifiedTime: Used as the primary sort field to order the events.
 
+- ResponseType: 0 = The organizer hasn't received a response, 1 = The organizer's copy of the meeting, 2 = Tentative, 3 = Accept, 4 = Decline, or 5 = The attendee hasn't responded.
+
 - ResponsibleUserName: The LegacyExchangeDN value of the user who made the change (for example, /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant or /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin).
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).