To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange 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. You need to be assigned permissions before you can run this cmdlet. ![]() When you run this cmdlet, it can take as long as an hour for the settings to become effective, depending on how long it takes for Active Directory to replicate.įor more information about the different authentication methods that you can see in this article, see Understanding HTTP Authentication. This cmdlet can be successfully run only if the RPC over HTTP proxy Windows networking component is already installed. In this article Syntax Enable-Outlook AnywhereĮnabling Outlook Anywhere on the Client Access server allows the server to accept external connections by Outlook 2003 or later clients by using Outlook Anywhere. Running the Enable-OutlookAnywhere cmdlet enables the server to accept requests from Microsoft Office Outlook 2007 and Outlook 2003 client computers from the Internet by using Outlook Anywhere, also known as RPC over HTTP.įor information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax. ![]() ![]() Use the Enable-OutlookAnywhere cmdlet to enable Outlook Anywhere on a computer running Microsoft Exchange Server 2010 that has the Client Access server role installed. This cmdlet is available only in Exchange Server 2010.
0 Comments
Leave a Reply. |