Merge branch 'master' of https://github.com/MicrosoftDocs/office-docs-powershell

Author: VesaJuvonen

.openpublishing.publish.config.json

@@ -282,4 +282,4 @@
       "nuget_feed": "https://www.myget.org/F/op/api/v2"
     }
   ]
-}
+}

exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md

@@ -40,7 +40,7 @@ Exchange Online Protection PowerShell allows you to manage your Exchange Online
 
     `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.`
 
-    To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
+    To require all scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
 
     ```
     Set-ExecutionPolicy RemoteSigned
@@ -76,7 +76,7 @@ Exchange Online Protection PowerShell allows you to manage your Exchange Online
 3. Run the following command:
 
    ```
-   Import-PSSession $Session
+   Import-PSSession $Session -DisableNameChecking
    ```
 
       [!NOTE]

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md

@@ -44,11 +44,11 @@ Exchange Online PowerShell allows you to manage your Exchange Online settings fr
 
   `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.`
 
-  To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
+  To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
 
-  ```
-  Set-ExecutionPolicy RemoteSigned
-  ```
+    ```
+    Set-ExecutionPolicy RemoteSigned
+    ```
 
   You need to configure this setting only once on your computer, not every time you connect.
 
@@ -75,11 +75,17 @@ Exchange Online PowerShell allows you to manage your Exchange Online settings fr
     - For Office 365 operated by 21Vianet, use the _ConnectionUri_ value: `https://partner.outlook.cn/PowerShell`
 
     - For Office 365 Germany, use the _ConnectionUri_ value: `https://outlook.office.de/powershell-liveid/`
+    
+    - If you're behind a proxy server, run this command first: `$ProxyOptions = New-PSSessionOption -ProxyAccessType <Value>`, where the _ProxyAccessType_ value is `IEConfig`, `WinHttpConfig`, or `AutoDetect`.
+      
+      Then, add the following parameter and value to the end of the $Session = ... command: `-SessionOption $ProxyOptions`.
+      
+      For more information, see [New-PSSessionOption](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption).
 
 3. Run the following command.
 
     ```
-    Import-PSSession $Session
+    Import-PSSession $Session -DisableNameChecking
     ```
 
 > [!NOTE]

exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md

@@ -44,7 +44,7 @@ If you don't have the Exchange management tools installed on your local computer
 
      `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.`
 
-    To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
+    To require all scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
 
   ```
   Set-ExecutionPolicy RemoteSigned
@@ -76,7 +76,7 @@ If you don't have the Exchange management tools installed on your local computer
 3. Run the following command:
     
     ```
-    Import-PSSession $Session
+    Import-PSSession $Session -DisableNameChecking
     ```
 
 > [!NOTE]

exchange/docs-conceptual/exchange-server/control-remote-powershell-access-to-exchange-servers.md

@@ -33,7 +33,7 @@ For additional management tasks related to remote PowerShell, see [Connect to Ex
   
 ## Use the Exchange Management Shell to enable or disable remote PowerShell access for a user
 
-This example disable remote PowerShell access for the user named Therese Lindqvist.
+This example disables remote PowerShell access for the user named Therese Lindqvist.
 
 ```
 Set-User "Therese Lindqvist" -RemotePowerShellEnabled $false
@@ -42,7 +42,7 @@ Set-User "Therese Lindqvist" -RemotePowerShellEnabled $false
 This example enables remote PowerShell access for the user named Sirirat Kitjakarn.
 
 ```
-Set-User "Sirirat Kitjakarn" -RemotePowerShellEnabled $false
+Set-User "Sirirat Kitjakarn" -RemotePowerShellEnabled $true
 ```
 
 ## Use the Exchange Management Shell to disable remote PowerShell access for many users
@@ -135,4 +135,4 @@ To display only those users who have access to remote PowerShell, run the follow
 
 ```
 Get-User -ResultSize unlimited -Filter {RemotePowerShellEnabled -eq $true}
-```
+```

exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md

@@ -31,7 +31,7 @@ Exchange PowerShell help follows conventions that indicate what's required or op
 |-|A hyphen indicates a parameter. For example, `-Identity`.|
 |\< \>|Angle brackets indicate the possible values for a parameter. For example, `-Location <ServerName>` or `-Enabled <$true | $false>`.|
 |[ ]|Square brackets indicate optional parameters and their values. For example, `[-WhatIf <SwitchParameter>]`. Parameter-value pairs that aren't enclosed in square brackets are required.|
-|\| |Pipe symbols in parameter values indicate a choice between values. For example, `-Enabled <$true | $false>` indicates the _Enabled_ parameter can have the value `$true` or `$false`.|
+|\| |Pipe symbols in parameter values indicate a choice between values. For example, -Enabled \<$true \| $false\> indicates the _Enabled_ parameter can have the value `$true` or `$false`.|
 
 These command conventions help you understand how a command is constructed. With the exception of the hyphen that indicates a parameter, you don't use these symbols as they're described in the table when you run cmdlets in Exchange PowerShell. 
 
@@ -117,12 +117,12 @@ The following table shows the valid operators that you can use in an Exchange co
 
 |**Operator**|**Description**|
 |:-----|:-----|
-|**=** | The equal sign is used as an assignment character. The value on the right side of the equal sign is assigned to the variable on the left side of the equal sign. The following characters are also assignment characters: <br/> **+=** Add the value on the right side of the equal sign to the current value that's contained in the variable on the left side of the equal sign. <br/> **-=** Subtract the value on the right side of the equal sign from the current value that's contained in the variable on the left side of the equal sign. <br/> **\*=** Multiply the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign. <br/> **/=** Divide the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign. <br/> **%=** Modify the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign. <br/> |
+|**=** | The equal sign is used as an assignment character. The value on the right side of the equal sign is assigned to the variable on the left side of the equal sign. The following characters are also assignment characters: <br/> • **+=**: Add the value on the right side of the equal sign to the current value that's contained in the variable on the left side of the equal sign. <br/> • **-=**: Subtract the value on the right side of the equal sign from the current value that's contained in the variable on the left side of the equal sign. <br/> • **\*=**: Multiply the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign. <br/> • **/=**: Divide the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign. <br/> • **%=**: Modify the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign. |
 |**:** | A colon can be used to separate a parameter's name from the parameter's value. For example, `-Enabled:$True`. Using a colon is optional with all parameter types except switch parameters. For more information about switch parameters, see [Parameters](https://technet.microsoft.com/library/bc81f639-c822-4b2b-a692-694c43f5f57e.aspx). |
 |**!**  | The exclamation point is a logical **NOT** operator. When it is used with the equal ( **=** ) sign, the combined pair means "not equal to." |
 |**[ ]** | Brackets are used to specify the index value of an array position. Index values are offsets that start at zero. For example, `$Red[9]` refers to the tenth index position in the array, `$Red`. <br/> Brackets can also be used to assign a type to a variable (for example, `$A=[XML] "<Test><A>value</A></Test>"`). The following variable types are available: `Array`, `Bool`, `Byte`, `Char`, `Char[]`, `Decimal`, `Double`, `Float`, `Int`, `Int[]`, `Long`, `Long[]`, `RegEx`, `Single`, `ScriptBlock`, `String`, `Type`, and `XML.` |
-|**{ }** |Braces are used to include an expression in a command. For example, `Get-Process | Where {$_.HandleCount -gt 400}` |
-|**\|** |The pipe symbol is used when one cmdlet pipes a result to another cmdlet. For example, `Get-Mailbox -Server SRV1 | Set-Mailbox -ProhibitSendQuota 2GB`. |
+|**{ }** |Braces are used to include an expression in a command. For example, Get-Process \| Where {$\_.HandleCount -gt 400} |
+|**\|** |The pipe symbol is used when one cmdlet pipes a result to another cmdlet. For example, Get-Mailbox -Server SRV1 \| Set-Mailbox -ProhibitSendQuota 2GB. |
 |**\>**  |The right-angle bracket is used to send the output of a command to a file, and the contents of the file are overwritten. For example, `Get-TransportRulePredicate > "C:\My Documents\Output.txt"`. |
 |**\>\>** |Double right-angle brackets are used to append the output of a command to an existing file. If the file doesn't exist, a new file is created. For example, `Get-TransportRulePredicate >> "C:\My Documents\Output.txt"`. |
 |**"** |Double quotation marks are used to enclose text strings that contains spaces. |
@@ -132,9 +132,9 @@ The following table shows the valid operators that you can use in an Exchange co
 |**..** |Double-periods indicate a value range. For example, if an array contains several indexes, you can return the values of all indexes between the second and fifth indexes by running the command: `$Blue[2..5]`. |
 |**+** |The **+** operator adds two values together. For example, `6 + 6` equals `12`. |
 |**-** |The **-** operator subtracts one value from another value (for example, `12 - 6` equals `6`) or indicates a negative number (for example, `-6 * 6` equals `-36`). |
-|**\*** |You can use the wildcard character to match strings (for example `Get-User | Where-Object {$_.Department -like 'Sales*'}`), multiply numeric values (for example, `6 * 6` equals `36`), or repeat the string value the specified number of times (for example, `"Test" * 3` equals `TestTestTest`).|
+|**\*** |You can use the wildcard character to match strings (for example, Get-User \| Where-Object {$\_.Department -like 'Sales*'}), multiply numeric values (for example, `6 * 6` equals `36`), or repeat the string value the specified number of times (for example, `"Test" * 3` equals `TestTestTest`).|
 |**/** |The **/** operator divides one value by another. For example, `6 / 6` equals `1`. |
-|**%** |In a numerical evaluation, the **%** operator returns the remainder from a division operator. For example, `6 % 4` equals `2`.  <br/> In a pipeline, the percent character ( `%` ) is shorthand for the **ForEach-Object** cmdlet. For example, `Import-Csv c:\MyFile.csv | ForEach-Object {Set-Mailbox $_.Identity -Name $_.Name}` is the same as `Import-Csv c:\MyFile.csv | % {Set-Mailbox $_.Identity -Name $_.Name}`. For more information, see [Pipelining](https://technet.microsoft.com/library/59411ed3-926b-4eec-a462-84e6b26056c9.aspx).  <br/> |
-|**?** |The question mark character ( **?** ) is shorthand for the **Where-Object** cmdlet. For example, `Get-Alias | Where-Object {$_.Definition -eq "Clear-Host"}` is the same as `Get-Alias | ? {$_.Definition -eq "Clear-Host"}`. |
+|**%** |In a numerical evaluation, the **%** operator returns the remainder from a division operator. For example, `6 % 4` equals `2`.  <br/> In a pipeline, the percent character ( `%` ) is shorthand for the **ForEach-Object** cmdlet. For example, Import-Csv c:\MyFile.csv \| ForEach-Object {Set-Mailbox $\_.Identity -Name $\_.Name} is the same as Import-Csv c:\MyFile.csv \| % {Set-Mailbox $\_.Identity -Name $\_.Name}. For more information, see [Pipelining](https://technet.microsoft.com/library/59411ed3-926b-4eec-a462-84e6b26056c9.aspx). |
+|**?** |The question mark character ( **?** ) is shorthand for the **Where-Object** cmdlet. For example, Get-Alias \| Where-Object {$\_.Definition -eq "Clear-Host"} is the same as Get-Alias \| ? {$\_.Definition -eq "Clear-Host"}|