Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
41 commits
Select commit Hold shift + click to select a range
02793ec
Create Get-SupervisoryReviewActivity.md
chrisda Dec 11, 2018
6535259
Update to the cmdlet per new changes
robmazz Dec 13, 2018
a893f2a
Merge pull request #2277 from robmazz/patch-1
kenwith Dec 14, 2018
87b58d8
Update for Example 1 after review with PM
robmazz Dec 17, 2018
60cf5fc
Merge pull request #2311 from robmazz/patch-2
kenwith Dec 17, 2018
345998b
Merge branch 'master' into SupRevAct-chrisda
chrisda Dec 21, 2018
bbf10fb
Added new cmdlets
chrisda Dec 21, 2018
4a06a41
Updates for cmdlet
robmazz Jan 10, 2019
4833696
Updated cmdlet information
robmazz Jan 10, 2019
95c029b
Merge pull request #2463 from robmazz/patch-3
chrisda Jan 10, 2019
4e07920
Update Get-SupervisoryReviewTopCasesReport.md
chrisda Jan 10, 2019
44ad13d
Merge pull request #2464 from robmazz/patch-4
chrisda Jan 10, 2019
756414b
Merge branch 'master' into SupRevAct-chrisda
chrisda Jan 15, 2019
3d09cc2
Merge branch 'live' into chrisda
chrisda Feb 2, 2019
311c891
Merge branch 'master' into chrisda
chrisda Feb 2, 2019
6ede08d
Update Restore-RecoverableItems to include PurgedItems switch
Lakshminarayand9 Feb 4, 2019
1132d82
Update Get-RecoverableItems to included Purgeditems parameter
Lakshminarayand9 Feb 4, 2019
304e6e2
Update Set-OrganizationConfig.md
chrisda Feb 4, 2019
b23846f
Fixed missing external help file
dariomws Feb 4, 2019
4e8b56e
Merge pull request #2738 from dariomws306/Dariomws2
kenwith Feb 4, 2019
1bd65a0
Fixed missing help file
dariomws Feb 5, 2019
0cdef6c
Merge branch 'master' into chrisda
chrisda Feb 5, 2019
ee93510
Updates to MessageID parameters per Issue #2744
chrisda Feb 5, 2019
0a9f702
Merge pull request #2740 from dariomws306/Dariomws1
kenwith Feb 5, 2019
3060a0e
Merge branch 'master' into chrisda
chrisda Feb 5, 2019
4eed418
Update Get-RecoverableItems.md
chrisda Feb 5, 2019
7c876f3
Merge branch 'master' into patch-2
chrisda Feb 5, 2019
7715628
Update Restore-RecoverableItems.md
chrisda Feb 5, 2019
ddd39db
Merge branch 'master' into patch-1
chrisda Feb 5, 2019
240fd14
Merge pull request #2734 from Lakshminarayand9/patch-2
chrisda Feb 6, 2019
ff0c55a
Merge branch 'master' into patch-1
chrisda Feb 6, 2019
9319066
Merge pull request #2733 from Lakshminarayand9/patch-1
chrisda Feb 6, 2019
5f69738
Merge branch 'master' into chrisda
chrisda Feb 6, 2019
8fe0d06
Merge pull request #2745 from MicrosoftDocs/chrisda
chrisda Feb 6, 2019
33df96c
Update Set-Mailbox.md
chrisda Feb 6, 2019
7f07717
Merge pull request #2747 from MicrosoftDocs/chrisda
chrisda Feb 6, 2019
625b8f9
Update exchange-cmdlet-syntax.md
chrisda Feb 6, 2019
d251155
Merge branch 'master' into SupRevAct-chrisda
chrisda Feb 6, 2019
36e49bb
Merge pull request #2753 from MicrosoftDocs/chrisda
chrisda Feb 6, 2019
f1b11bd
Merge branch 'master' into SupRevAct-chrisda
chrisda Feb 6, 2019
c3c349b
Merge pull request #2754 from MicrosoftDocs/SupRevAct-chrisda
chrisda Feb 6, 2019
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 31 additions & 33 deletions exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ Accept wildcard characters: False
```

### -MessageId
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string. This may include angle brackets.
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").

```yaml
Type: MultiValuedProperty
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ This example presents 50 quarantined messages per page, and returns the third pa

### -------------------------- Example 3 --------------------------
```
Get-QuarantineMessage -MessageID <5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>
Get-QuarantineMessage -MessageID "<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com>"
```

This example returns the quarantined message with the Message-ID value \<5c695d7e-6642-4681-a4b0-9e7a86613cb7@contoso.com\>.
Expand Down Expand Up @@ -159,7 +159,7 @@ Accept wildcard characters: False
```

### -MessageId
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string. This may include angle brackets.
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").

```yaml
Type: String
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,20 @@ Set-OutlookAnywhere [-Identity] <VirtualDirectoryIdParameter>
[-ClientAuthenticationMethod <Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | MaxValidValue | Misconfigured>]
[-Confirm]
[-DefaultAuthenticationMethod <Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | MaxValidValue | Misconfigured>]
[-DomainController <Fqdn>] [-ExtendedProtectionFlags <MultiValuedProperty>]
[-ExtendedProtectionSPNList <MultiValuedProperty>] [-ExtendedProtectionTokenChecking <None | Allow | Require>]
[-ExternalHostname <Hostname>] [-IISAuthenticationMethods <MultiValuedProperty>] [-Name <String>]
[-SSLOffloading <$true | $false>] [-WhatIf] [-ExternalClientAuthenticationMethod <Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos | Negotiate | LiveIdNegotiate | Misconfigured>]
[-DomainController <Fqdn>]
[-ExtendedProtectionFlags <MultiValuedProperty>]
[-ExtendedProtectionSPNList <MultiValuedProperty>]
[-ExtendedProtectionTokenChecking <None | Allow | Require>]
[-ExternalClientAuthenticationMethod <Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos | Negotiate | LiveIdNegotiate | Misconfigured>]
[-ExternalClientsRequireSsl <$true | $false>]
[-ExternalHostname <Hostname>]
[-IISAuthenticationMethods <MultiValuedProperty>]
[-InternalClientAuthenticationMethod <Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos | Negotiate | LiveIdNegotiate | Misconfigured>]
[-InternalClientsRequireSsl <$true | $false>] [-InternalHostname <String>] [<CommonParameters>]
[-InternalClientsRequireSsl <$true | $false>]
[-InternalHostname <String>]
[-Name <String>]
[-SSLOffloading <$true | $false>]
[-WhatIf] [<CommonParameters>]
```

## DESCRIPTION
Expand Down Expand Up @@ -247,51 +254,55 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -ExternalHostname
The ExternalHostname parameter specifies the external hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com.
### -ExternalClientAuthenticationMethod
The ExternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate external Outlook Anywhere clients. Valid values are:

- Basic

- Ntlm

- Negotiate (This is the default value)

You can't use this parameter with the DefaultAuthenticationMethods parameter.

```yaml
Type: Hostname
Type: Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos | Negotiate | LiveIdNegotiate | Misconfigured
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -IISAuthenticationMethods
The IISAuthenticationMethods parameter specifies the authentication method that's used on the Outlook Anywhere virtual directory in IIS. Valid values are:

- Basic

- Ntlm
### -ExternalClientsRequireSsl
The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are:

- Negotiate
- $true: Clients connecting via Outlook Anywhere from outside the organization are required to use SSL.

You can specify multiple value separated by commas. By default, all values are used.
- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This is the default value.

You can't use this parameter with the DefaultAuthenticationMethods parameter.
The value of this parameter is related to the value of the SSLOffloading parameter.

```yaml
Type: MultiValuedProperty
Type: $true | $false
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Name
The Name parameter specifies the name of the Outlook Anywhere virtual directory. The default value is Rpc (Default Web Site). If the value you specify contains spaces, enclose the value in quotation marks (").
### -ExternalHostname
The ExternalHostname parameter specifies the external hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com.

```yaml
Type: String
Type: Hostname
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Expand All @@ -302,21 +313,21 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -SSLOffloading
The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are:
### -IISAuthenticationMethods
The IISAuthenticationMethods parameter specifies the authentication method that's used on the Outlook Anywhere virtual directory in IIS. Valid values are:

- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This is the default value.
- Basic

- $false: Outlook Anywhere clients using SSL maintain an SSL connection along the entire network path to the Exchange server. Only SSL connections are allowed to the Outlook Anywhere virtual directory.
- Ntlm

This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it may take several minutes before the change is visible in IIS Manager.
- Negotiate

You need to use the value $true for this parameter if you don't require SSL connections for internal or external Outlook Anywhere clients.
You can specify multiple value separated by commas. By default, all values are used.

The value of this parameter is related to the values of the ExternalClientsRequireSsl and InternalClientsRequireSsl parameters.
You can't use this parameter with the DefaultAuthenticationMethods parameter.

```yaml
Type: $true | $false
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Expand All @@ -327,29 +338,14 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -WhatIf
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -ExternalClientAuthenticationMethod
The ExternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate external Outlook Anywhere clients. Valid values are:
### -InternalClientAuthenticationMethod
The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are:

- Basic

- Ntlm
- Ntlm (This is the default value)

- Negotiate (This is the default value)
- Negotiate

You can't use this parameter with the DefaultAuthenticationMethods parameter.

Expand All @@ -365,12 +361,12 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -ExternalClientsRequireSsl
The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are:
### -InternalClientsRequireSsl
The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are:

- $true: Clients connecting via Outlook Anywhere from outside the organization are required to use SSL.
- $true: Clients connecting via Outlook Anywhere from inside the organization are required to use SSL.

- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This is the default value.
- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This is the default value.

The value of this parameter is related to the value of the SSLOffloading parameter.

Expand All @@ -386,58 +382,69 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -InternalClientAuthenticationMethod
The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are:

- Basic

- Ntlm (This is the default value)
### -InternalHostname
The InternalHostname parameter specifies the internal hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com.

- Negotiate
```yaml
Type: String
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

You can't use this parameter with the DefaultAuthenticationMethods parameter.
### -Name
The Name parameter specifies the name of the Outlook Anywhere virtual directory. The default value is Rpc (Default Web Site). If the value you specify contains spaces, enclose the value in quotation marks (").

```yaml
Type: Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos | Negotiate | LiveIdNegotiate | Misconfigured
Type: String
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -InternalClientsRequireSsl
The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are:
### -SSLOffloading
The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are:

- $true: Clients connecting via Outlook Anywhere from inside the organization are required to use SSL.
- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This is the default value.

- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This is the default value.
- $false: Outlook Anywhere clients using SSL maintain an SSL connection along the entire network path to the Exchange server. Only SSL connections are allowed to the Outlook Anywhere virtual directory.

The value of this parameter is related to the value of the SSLOffloading parameter.
This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it may take several minutes before the change is visible in IIS Manager.

You need to use the value $true for this parameter if you don't require SSL connections for internal or external Outlook Anywhere clients.

The value of this parameter is related to the values of the ExternalClientsRequireSsl and InternalClientsRequireSsl parameters.

```yaml
Type: $true | $false
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -InternalHostname
The InternalHostname parameter specifies the internal hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com.
### -WhatIf
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

```yaml
Type: String
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Aliases: wi
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
Default value: None
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ This example returns the encryption revocation status for the specified message.
## PARAMETERS

### -MessageId
The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string. This may include angle brackets.
The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").

You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Office 365 Security & Compliance Center.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ This example revokes encryption for the specified message.
## PARAMETERS

### -MessageId
The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string. This may include angle brackets.
The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").

You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Office 365 Security & Compliance Center.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ Accept wildcard characters: False
```

### -MessageId
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string. This may include angle brackets.
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").

```yaml
Type: String
Expand Down
Loading