MicrosoftDocs · chrisda · Aug 29, 2018 · Aug 29, 2018
diff --git a/exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md
@@ -99,7 +99,7 @@ Before you run the Set-OwaVirtualDirectory cmdlet, consider the following items:
 
 - Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see Modifying multivalued properties (https://technet.microsoft.com/library/bb684908.aspx).
 
-- Many of the Outlook on the web virtual directory settings require you to run the IISReset /noforce command before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page.
+- Many of the Outlook on the web virtual directory settings require you to restart IIS (Stop-Service WAS -Force and Start-Service W3SVC) before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page.
 
 - To switch from forms-based authentication to Basic authentication, you must first disable forms-based authentication, and then as a separate task, enable Basic authentication. You can't disable forms-based authentication and enable Basic authentication in a single task.
 

diff --git a/exchange/exchange-ps/exchange/client-access/New-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/client-access/New-OwaMailboxPolicy.md
@@ -25,7 +25,7 @@ New-OwaMailboxPolicy [-Name] <String> [-Confirm] [-DomainController <Fqdn>]
 ## DESCRIPTION
 Use the Set-OwaMailboxPolicy cmdlet to configure the new policy.
 
-Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by running the command IISRESET /noforce.
+Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC).
 
 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).
 

diff --git a/exchange/exchange-ps/exchange/client-access/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/client-access/Remove-OwaMailboxPolicy.md
@@ -23,7 +23,7 @@ Remove-OwaMailboxPolicy [-Identity] <MailboxPolicyIdParameter> [-Confirm] [-Doma
 ```
 
 ## DESCRIPTION
-Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by running the command IISRESET /noforce.
+Changes to Outlook on the web mailbox polices may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC).
 
 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).