Using Exchange Management Shell, OWA access can quickly be enabled or disabled for users.  To enable OWA access for a specific user type: Set-CASMailbox -Id user@domain.com OWAenabled -$true To... >> MORE INFORMATION

Personal Distribution lists have a default of approximately 100 – 130 members.  To avoid exceeding the limit, take a look at the three potential workaround: Create more than one PDLOn the server,... >> MORE INFORMATION

Additional login prompts are often the result of incorrect authentication settings.  For RSA SecurID two-factor authentication interoperation with a Client Access Server (CAS), the owa virtual... >> MORE INFORMATION

The Account lockout duration, Account lockout threshold and Reset account lockout counter after settings are configured in the Default Domain Policy.  These settings define what will happen if a... >> MORE INFORMATION

OWA 2007 provides the option to pre-configure the Default Domain in the Exchange Management Console (EMC) so users do not need to enter it.  With this configuration, users only need to enter the... >> MORE INFORMATION

When a user clicks on the Open as Web Page link to view a supported file attachment which exceeds the default WebReady Document Viewing file size limit, Outlook Web Access will display the following... >> MORE INFORMATION

Some users may have cached Exchange mode enabled.  In this configuration, Outlook works from a local copy of the user’s mailbox which is refreshed periodically.  This would explain why they can... >> MORE INFORMATION

Pasting images into messages is not an OWA feature.  There are two workarounds to getting images into your message:You can paste HTML links to images, but this means that the image needs to be... >> MORE INFORMATION

When you open an attachment, rather than view it with WebReady Document Viewing or save it to a specified location, the attachment will always be saved to the temporary internet files folder on the... >> MORE INFORMATION

Many companies who have Microsoft Exchange with the update Q911829 (released in March and April, 2006) installed and are using Outlook Web Access have been experiencing a problem addressing messages.... >> MORE INFORMATION

Summary: "For a brief period of time on August 9, 2008, a pre-release version of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580) was inadvertently made available to Microsoft Update, the Microsoft Update Catalog, and Windows Software Update Services (WSUS) servers for download. While we quickly removed the update from Microsoft Update within a short period of time, some servers using these distribution methods might have detected, downloaded and/or installed this version of the update.

Known issues exist with this pre-release version of Update Rollup 4, including issues with Exchange Web Services (EWS) that creates the potential for a continuous crashing cycle, an uninstall issue where the EWS web.config is reset, and an issue with backup validation. The final release version of Update Rollup 4 will be released in the upcoming weeks, and until then, we recommend that customers who have not already installed Update Rollup 4 wait to do so. If you have already installed Update Rollup 4, we recommend uninstalling it. (...)"
http://msexchangeteam.com/archive/2008/09/11/449787.aspx

Summary: This article, by ISA Firewall specialist Thomas Shinder, explains that earlier versions of ISA Firewall (2000 and 2004) included navigation protection.  Navigation protection ensures that if a user goes to another website, such as Google, without logging off OWA, ISA automatically logs the user off.  With navigation protection, administrators can rest assured that users are not leaving active OWA sessions behind.

ISA Firewall 2006 no longer includes navigation protection.  This is explained in more detail in an ISA Security report published by Messageware Incorporated (ISA Security Report: OWA Security Issues Undetected by ISA Server) referenced in Thomas Shinder’s article.

To read the full article, go to:
http://blogs.isaserver.org/shinder/2007/07/19/isa-firewall-auto-log-off-controls-can-be-a-security-issue-for-owa-publishing/

Summary: The article gives an overview of an OWA attachment solution called AttachView by Messageware, which lets users safely view a wide array of attachments without ever downloading the file to the local computer.  AttachView offers users secure access to attachments via an enhanced viewing window with features such as: view Microsoft Word Track Changes revisions, a hyperlinked table of contents, printer-friendly version, rotate and zoom buttons.

Administrators can set rules giving users access to users to open, save and print attachments based on criteria such as IP address, username, hostname and if they are connecting from a corporate device.

To view the full article, go to http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1310616,00.html

Summary: This article provides a low-level overview of what is new in Exchange 2007 including a feature summary. In Exchange 2007, the main focus is on security, mobility, and efficiency.
 http://technet.microsoft.com/en-us/exchange/bb736128.aspx

Summary: The article outlines the most common authentication methods and certificate consideration as well as steps to troubleshoot the 6 most common ISA Server issues (summary below).

Scenario 1: Users are re-prompted for authentication after entering username and password on the ISA FBA logon page.
Resolution: Verify that FBA is only enabled on the CAS or ISA Server.

Scenario 2: Users receive the error “Target Principle name is incorrect” after entering credentials on the FBA form.
Resolution: Verify the certificate name, the CAS name referenced on the ISA rule, and make sure the ISA server can resolve the CAS FQDN to an IP.

Scenario 3: Typing in the OWA URL without using /owa gives “403 Access Forbidden” error
Resolution: The ISA paths only allow for access to OWA with /owa.  Either update the allowed paths or use /owa in the URL.

Scenario 4: After logging into OWA users receive a “404 Not Found” error and ISA logs show a “Failed connection attempt” error
Resolution: Make sure that the ISA server can resolve the CAS FQDN to an IP, use telnet to connect to the FQDN and check if you get a response, and enable logging.

If you see a “Failed connection attempt” error in the ISA logs, also check for connection issues between ISA and the CAS such as closed or restricted ports, do a network trace, and check the IIS logs to see if the connection was received.

Scenario 5: Users get a “10061 Connection Refused” error after logging into OWA.
Resolution: Make sure that the port on the Bridging tab used by ISA to connect to Exchange matches the port configured on the OWA website in IIS.  In this scenario, the ISA logs will show a “Failed connection attempt” error.

Scenario 6: When connecting to OWA via ISA users can login but all the buttons are disabled on a new message form.  The issue does not occur when connecting to the Exchange Server directly.
Resolution: Verify if you have other 3rd party ISAPI filters on the OWA website.

To access the full article, go to http://blogs.technet.com/isablog/archive/2008/04/29/troubleshooting-owa-2007-publishing-rules-on-isa-server-2006.aspx

Summary: Microsoft’s article outlines the top 10 reasons to upgrade to Exchange 2007 from a business perspective.
http://www.microsoft.com/exchange/evaluation/topreasons.mspx

Summary: The top 10 user and administrator features in Exchange 2007 are outlined in the article by InfoWord.
http://www.infoworld.com/article/06/08/07/32FEexchange10_1.html?s=feature

Summary: This article describes how to secure and enhance OWA by installing the Messageware Suite for Exchange 2007 SP1.
http://news.thomasnet.com/fullstory/807394

Summary: This product review outlines how Messageware’s AttachView product extends WebReady Document Viewing with security and productivity features.
http://blogs.msexchange.org/walther/2008/01/16/messagewares-attachview-2007-takes-webready-document-viewing-to-new-heights/

Summary: This article discusses the configuration options available when using the Set-OwaVirtualDirectory cmdlet.  The cmdlet offers 77 configuration options some of which are available through the Exchange Management Console and some of which are only available through the Exchange Management Shell.
 

http://windowsitpro.com/article/articleid/97757/setting-client-access-server-and-owa-options.html