Outlook Web App - Everything OWA

OWA 2010 provides users with basic tracking options allowing you to request and read a delivery receipt as well as control the importance and sensitivity of each E-mail. However, users are unable to send messages for deferred delivery or set to expire in OWA.

An important difference is that Microsoft Outlook allows users to work with e-mail, calendars, etc., even when a network connection is unavailable, whereas OWA requires a network connection to function. There is no option to work offline utilizing cached information.

Follow the steps below to set an out of office reply in OWA

1. Click on Options in the upper-right.

2.  Select Set Automatic Replies from the drop-down menu.

3.  Select Send automatic replies.

4.  If desired, select the Send Replies only during this time period check box to schedule when your out of office replies are active. If you do not specify a start and end time, auto-replies will be sent until you select the Don't send automatic replies check box. NOTE: Previously used automatic replies associated with your email account may appear in the text boxes for your use, if desired.

5.  For replies to senders inside your organization, type the response that you want to send to colleagues while you are out of the office. They will receive the notification only once.

6.  For replies to senders outside your organization, select Send automatic reply messages to senders outside my organization check box. Select whether you want Send replies only to senders in my Contacts list or Send replies to all external senders. Type the response that you want to send while you are out of the office. They will receive the notification only once.

7.  Click Save

Follow the steps below to create an email signature in OWA:

1. Click on Options in the upper-right.
2. Select See All Options from the drop-down menu.

3.  Select Settings.

4.   Compose your signature in the E-Mail Signature text box. If you have an existing signature in your mail client, copy and paste it here.

5.   Click Automatically include my signature on messages I send if you want the signature to appear by default on your outgoing email.

6.   Click Save in the lower-right portion of the screen.

7.   If you did not choose to automatically include your signature on outgoing email, you must manually insert it. In the new email window, Click the Insert Signature button. Your signature will appear in the text of your message.

You must configure the Exchange Client App server to use Basic, NTLM, or KCD authentication, because Forefront UAG does not support forms-based authentication to perform single sign-on (SSO) to Outlook Web App.

To configure Exchange to use basic authentication

1. Start the Exchange Management Console.
2. 2. In the Exchange Management Console, expand Server Configuration, and then click Client Access
3. Select your Client Access server, and then on the Outlook Web App tab, select OWA (Default Web Site).
4. In the Actions pane, under OWA (Default Web Site), click Properties.
5. On the Authentication tab, click Use one or more of the following standard authentication methods, select the Basic authentication (password is sent in clear text) check box, and then click OK.

To publish Outlook Web App on a Forefront UAG portal

1. 1. In the Forefront UAG Management console, click the portal through which you want to publish Exchange services, and then, below the Applications list, click Add. The Add Application Wizard opens.
2. 2. On the Select Application page of the wizard, in the Web list, click Microsoft Exchange Server 2010
3. 3. On the Select Exchange Services page of the wizard, in the Exchange version list, click the version of the Exchange server you want to publish. Under Exchange services, select the Outlook Web Access check box.

Note: In Outlook 2010, if you want to allow access to the Exchange Control Panel only (without other Outlook Web App functionality), run the Add Application Wizard as described, and then after finishing the wizard, edit the application properties and remove the /owa path.

1. 4. On the Configure Application page of the wizard, enter a name for the application.
2. 5. On the Select Endpoint Policies page of the wizard, select the policies to use for this application.
3. 6. On the Deploying an Application page of the wizard, choose whether to publish a single Exchange Client Access server or a farm of load-balanced Exchange Client Access servers.
4. 7. On the Web Servers page of the wizard:
   1. a. In the Addresses list, enter the IP address or host name of the Client Access server.
   2. In the Public host name box, enter the public host name for this application. The public host name must match the FQDN in the certificate. The public host name can be the same as the public host name of the trunk, if required.

(Note: When publishing OWA, Forefront UAG communicates with the Exchange Client Access server over HTTP or HTTPS.)

1. 8. On the Authentication page of the wizard, select an authentication server to authenticate users to the application, and click401 request.
   1. On the Portal Link page of the wizard, configure the portal link for the application.

If you are publishing Exchange 2010 and OWA is not the initial portal application, make sure that the Open in a new window check box is selected.

10. On the Authorization page of the wizard, select which users are authorized to access this application.

11.  On the Completing the Add Application Wizard page of the wizard, click Finish.

The Add Application Wizard closes, and the application that you defined appears in the Forefront UAG Management console, in the Applications list.

12. If you want to define the Outlook Web App application as the portal home page, in the Forefront UAG Management console, in the Initial application list, click the application that you added in this procedure.

13. To apply the Outlook Web App look and feel to the Forefront UAG user interaction pages, in the Forefront UAG Management console, next to Configure trunk settings, click Configure, click the Authentication tab, and then select the Apply an Outlook Web App look and feel check box. Confirm the changes to the logon settings, and then click OK.

14.  On the toolbar of the Forefront UAG Management console, click the Activate configuration icon, and then on the Activate Configuration dialog box, click Activate.

When the configuration is activated, the message "Forefront UAG configuration activated successfully" appears.

Users receive the following message while accessing OWA

"Your mailbox appears to be offline, Try to access it again in 10 seconds"

To test that the Exchange services are running correctly, run the following cmdlet using the Exchange Management Shell on the CAS:

Test-ServiceHealth

The results will show all services not started populated under ServicesNotRunning. Under each Exchange role, check to see if RequiredServicesRunning is False

To restart the services, enter the following cmdlet using the Exchange Management Shell:

Test-ServiceHealth | Select ServicesNotRunning | foreach { Start-Service $_.ServicesNotRunning }

The language settings are determined when you log in to OWA 2010 for the first time. This setting can be changed at any time by accessing the Regional Settings from the Options page.

1. Use a Web browser to sign into a mailbox that you have full access permission to via Outlook Web App
2. Click Options, and then click Regional Settings 
3. Under Language, in the Choose language list, click the language that you want to use.
4. Click Save to save your language settings.

Once logged into OWA, select Mail from the Navigation pane. Hovering the mouse above your user name will present you with the amount of mailbox space used as well as the limit that can be used.

Microsoft is currently working on a fix for this vulnerability; in the meantime they have suggested a workaround to disable Web Ready Viewing.  To perform this action, follow the steps below:

1.       Open up the Exchange Management Shell as an Exchange Organization Administrator

2.       Type the following command: Get-OwaVirtualDirectory | where {$_.OwaVersion -eq 'Exchange2007' -or $_.OwaVersion -eq 'Exchange2010'} | Set-OwaVirtualDirectory -WebReadyDocumentViewingOnPublicComputersEnabled:$False -WebReadyDocumentViewingOnPrivateComputersEnabled:$False

Alternatively, if you are concerned about attachment security you could look at a third party product from Messageware AttachView.

For additional information view the external links below: Microsoft Security Advisory (2737111) Vulnerabilities in Microsoft Exchange and FAST Search Server 2010 for SharePoint Parsing Could Allow Remote Code Execution

http://technet.microsoft.com/security/advisory/2737111

And how can I change it to show everything by calendar date?

In OWA 2010, emails are sorted in conversations by default. Conversations collect all email with the same subject into one thread to allow easy reference to past messages and keep your inbox organized by subject.

To stop viewing conversation view in your inbox:

1. Click Conversations by Date.
2. Click Conversation in the drop-down menu. This will uncheck the box next to conversation and remove the conversation view groupings from your inbox.

These updates address an issue in which digital signatures on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655. Also see Security Advisory 2749655 and Timestamping on the Security, Research & Defense blog.

• Update Rollup 4-v2 for Exchange Server 2010 Service Pack 2 (KB2756485)
• Update Rollup 7-v2 for Exchange Server 2010 Service Pack 1 (KB2756496)
• Update Rollup 8-v2 for Exchange Server 2007 Service Pack 3 (KB2756497)

The re-released Exchange 2010 SP2 RU4 includes the following additional fix:

Update rollup 2756987; only one result is returned after you click "view all results" in Outlook 2010 or in Outlook 2013 in an Exchange Server 2010 environment

It is not required to uninstall the previous rollups to install the re-released rollups listed above.

Juniper Networks

eightwone.com

One of the features of Exchange versions up to 2007 is Single Instance Storage (SIS). What SIS does is that it creates a single instance of messages sent to multiple recipients within the same database. Simply said, the first one gets a copy of the message in his or her mailbox, others get a referral to the message.

With the arrival of Exchange 2010 Microsoft made changes to the Extensible Storage Engine (ESE) .. again. Many of these changes are beneficiary to the performance of the system (read: less IOPS). For instance, Exchange 2010 uses larger pages and it orders database pages in the background. In an optimal situation this will result in an IOPS reduction of 70% versus Exchange 2007 (against Exchange 2003 a whopping 90%).

However, one of the victims of the new ESE is Single Instance Storage. This sounds worse than it is. Large (1 GB+) mailboxes are common nowadays, the maximum number of databases has increased and when looking at recovery times you are more likely to use multiple databases to reduce recovery times.

These developments also reduce the effectiveness of Single Instance Storage, which only works in a single database. In addition, the price of storage has dropped enormeously and focus these days is more on performance than on disk space.

To read the full article, go to:

http://eightwone.com/2009/11/25/exchange-2010-database-compression/

Microsoft Exchange Team Blog

In Exchange Server 2010, there is no more single instance storage (SIS). To help understand why SIS is gone, let's review a brief history of Exchange.

During the development of Exchange 4.0, we had two primary goals in mind, and SIS was borne out of these goals:

1. Ensure that messages were delivered as fast and as efficient as possible.
2. Reduce the amount of disk space required to store messages, as disk capacity was premium.

Exchange 4.0 (and, to a certain extent, Exchange 5.0 and Exchange 5.5) was really designed as a departmental solution. Back then, users were typically placed on an Exchange server based on their organization structure (often, the entire company was on the same server). Since there was only one mailbox database, we maximized our use of SIS for both message delivery (only store the body and attachments once) and space efficiency. The only time we created another copy within the store was when the user modified their individual instance.

For almost 19 years, the internal Exchange database table structure has remained relatively the same...

To read the full article, go to:

http://blogs.technet.com/b/exchange/archive/2010/02/22/dude-where-s-my-single-instance.aspx

windowsitpro.com

IT pros usually don't enjoy applying updates and fixes to existing software because of the chance that such "fixes" could introduce new problems. (We've all seen it happen.) So when those updates come with welcome new features, it makes the process just a little sweeter, and could even get IT shops to fast-track the implementation. Such is the case with Update Rollup 4 (RU4) for Microsoft Exchange Server 2010 SP2 because of the new support for retention policies on Calendar and Tasks.

In versions of Exchange 2010 prior to RU4, you can't apply retention tags or policies either to individual calendar or task items or to the main Calendar folder or Tasks folder. So, businesses with particularly stringent retention needs for compliance might be running into trouble relying only on Exchange's built-in features. Of course, third-party vendors that provide e-discovery or compliance solutions will tell you that Exchange 2010's retention and compliance features are limited even in the best of cases.

Nonetheless, the calendar and tasks update in RU4 is certainly being met with approval; many Exchange users have clearly been waiting for this feature. If you're using retention policies already, Calendar and Tasks will inherit the Default Policy Tag (DPT) automatically. However, you can exclude these folders from the DPT through a registry hack, if necessary, to avoid unexpected results for your end users. The process is explained in the Exchange Team Blog post about this update by Ross Smith IV.

To read the full article, go to:

http://www.windowsitpro.com/blog/exchange-and-outlook-blog-8/exchange-2013/exchange-2013-exchange-2010-sp2-ru4-address-compliance-issues-144019