Implementing Outlook Web Access
Once the Client Access role is installed on your Exchange Server, the OWA is available to your remote users who want to access their mailboxes using their web browsers. Although none of the settings are mandatory for the implementation of OWA, it requires you to configure various features and settings in Exchange Server 2007 for customization and efficiency. You can use various tools to configure OWA. These tools are:
* Exchange Management Console: A GUI used to manage the most common settings of OWA including Organization Configuration.
* Exchange Management Shell: A command-line interface that allows you to manage futures that cannot be managed using Exchange Management Console. It also allows you to automate administrative tasks and manage the associated command-line plug-ins.
* IIS Manager: A MMC that allows you to manage virtual directories.
* Web.config: A configuration file that must be modified using notepad. It allows you to modify OWA settings that are specific to ASP.NET.
* Registry editor: A sensitive tool that can be used to directly configure OWA settings such as the PublicClientTimeout, SSLOffloaded, and TrustedClientTimeout
To configure OWA in your Exchange server you can perform the following configurations:
* Configure OWA Virtual Directories: When the Client Access role is installed on your exchange server the following default OWA virtual directories are created under the Default Web Site in IIS on the Exchange server to allow access to Exchange content, as shown in Figure 5:
/owa: Used to allow access to mailboxes on Exchange Server 2007
/Public: Used to allow access to public folders using OWA
/Exchweb: Used to allow access to mailboxes on Exchange Server 2003 or Exchange Server 2000
/Exchange: Used to allow access to mailboxes on Exchange Server 2007, Exchange Server 2003, or Exchange Server 2000
/Exadmin: Used to allow access to administrative settings and properties to administrators.
You can manage the default virtual directories or create new virtual directories by using IIS Manager, Exchange Management Console, or Exchange Management Shell.
Related: How To Disable The Shutdown Event Tracker On Microsoft Windows Server
More Details here
Once the Client Access role is installed on your Exchange Server, the OWA is available to your remote users who want to access their mailboxes using their web browsers. Although none of the settings are mandatory for the implementation of OWA, it requires you to configure various features and settings in Exchange Server 2007 for customization and efficiency. You can use various tools to configure OWA. These tools are:
* Exchange Management Console: A GUI used to manage the most common settings of OWA including Organization Configuration.
* Exchange Management Shell: A command-line interface that allows you to manage futures that cannot be managed using Exchange Management Console. It also allows you to automate administrative tasks and manage the associated command-line plug-ins.
* IIS Manager: A MMC that allows you to manage virtual directories.
* Web.config: A configuration file that must be modified using notepad. It allows you to modify OWA settings that are specific to ASP.NET.
* Registry editor: A sensitive tool that can be used to directly configure OWA settings such as the PublicClientTimeout, SSLOffloaded, and TrustedClientTimeout
To configure OWA in your Exchange server you can perform the following configurations:
* Configure OWA Virtual Directories: When the Client Access role is installed on your exchange server the following default OWA virtual directories are created under the Default Web Site in IIS on the Exchange server to allow access to Exchange content, as shown in Figure 5:
/owa: Used to allow access to mailboxes on Exchange Server 2007
/Public: Used to allow access to public folders using OWA
/Exchweb: Used to allow access to mailboxes on Exchange Server 2003 or Exchange Server 2000
/Exchange: Used to allow access to mailboxes on Exchange Server 2007, Exchange Server 2003, or Exchange Server 2000
/Exadmin: Used to allow access to administrative settings and properties to administrators.
You can manage the default virtual directories or create new virtual directories by using IIS Manager, Exchange Management Console, or Exchange Management Shell.
Related: How To Disable The Shutdown Event Tracker On Microsoft Windows Server
More Details here
0 comments:
Post a Comment