SYMPTOMS/PROBLEM:

(Recently, users are unable to open other authorized maiboxes in OWA, even, the administrator.)

After installing e2k10 SP2 RU4, users are unable to open additional mailboxes through OWA, if the primary SMTP email address of the additional mailbox is not in the accepted domain list.

Following exception is thrown in the owa window

Request
Url: https://dotnetserver.turcich.com:443/owa/
User host address: 192.168.0.1
OWA version: 14.2.318.2

Exception
Exception type: System.ArgumentNullException
Exception message: Value cannot be null. Parameter name: organizationId

CAUSE
This is due to a design change in Exchange 2010 SP2 RU4.

MS SUPPORT RESOLUTION
Add the SMTP Primary Email Domain to the ”Accepted Domain List”

WORKAROUND
Rollback to RU3

Link:
http://support.microsoft.com/kb/2777852/EN-US?wa=wsignin1.0
Tagged with:
 

If you ever wondered how long it takes for your browser to close after opening OWA ( outlook web App) if there is no activity?  here are the measurements.

  • Public 15 minutes
  • Private 8 hours

 

For whatever reason you may have if you decide to change these default values here is the link how to get the work done. The simplest way to achieve desired goal is using PS. Let’s say we will increase the Public cookie time out settings from 15 minutes to 25 minutes.

 

set-ItemProperty ‘HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA’ -name PrivateTimeout –value 25 -type dword

 

copy and paste above PS code into  EMS ( management Shell) , adjust the time as you wish , in this case we are going to set it to “25” minutes….

Cookies to control access

The first time that the user name and password are sent to the Client Access server to authenticate an Outlook Web App session, an encrypted cookie is created that’s used to track user activity. When the user closes the Internet browser or clicks Sign Out to sign out of their Outlook Web App session, the cookie is cleared. The user name and password are sent to the Client Access server only for the initial user sign-in. After the initial sign-in is complete, only the cookie is used for authentication between the client computer and the Client Access server.

 

Links:

http://technet.microsoft.com/en-us/library/bb123719.aspx

http://www.msexchangegeek.com/2009/10/22/changing-owa-time-out-on-an-exchange-2007-computer/

http://smtp25.blogspot.se/2010/08/set-owa-private-computer-cookie-time.html

Tagged with:
 

rom Steve Goodman: http://www.stevieg.org/2010/08/publishing-imap-pop-and-smtp-settings-via-exchange-2010-owa/

Other links: http://www.howexchangeworks.com/2010/10/publishing-pop-imap-smtp-settings-in.html

In Exchange 2010 there is actually somewhere to publish these settings – and once configured your documentation won’t need to be updated if the server details change. You’ll find these settings by logging into OWA, and choosing Options. The link ”Settings for POP, IMAP, and SMTP access…” should be shown on the default ”My Account” page:

By default, nothing will be listed if you click the link:

 

To configure these links, it’s a fairly straightforward process. Before you begin, you need to know what the settings should be and in the case of the SMTP settings, which receive connector on which Hub Transport this relates to.

First, you configure the Client Access servers for the POP and IMAP settings, using the Set-POPSettings and Set-IMAPSettings cmdlets with the -ExternalConnectionSettings parameter.

For each protocol you specify a colon-separated list of values for the ExternalConnectionSettings. For POP3 with TLS, this might be ”casserver.contoso.com:110:tls” or POP3 with SSL might be ”casserver.contoso.com:995:ssl”. IMAP with TLS might be ”casserver.contoso.com:143:tls” and IMAP with SSL might be ”casserver.contoso.com:993:ssl”.

Here’s a quick example of the commands against my test setup:

Set-POPSettings -ExternalConnectionSettings "mail.contoso.com:110:tls" 
Set-IMAPSettings -ExternalConnectionSettings "mail.contoso.com:143:tls"

It’s important to remember, you need to run the command on all Client Access servers users will access.

Next, you need to allow the receive connector that you want ”published” to advertise it’s settings. You do this with the Set-ReceiveConnector cmdlet specifying the -AdvertiseClientSettings:$true parameter and value.

In my example, I want to advertise the port 587 ”client” receive connector on my Hub Transport server:

Set-ReceiveConnector -Identity "hubtransport\Client HUBTRANSPORT" -AdvertiseClientSettings:$true

Finally, run iisreset to restart IIS on each Client Access Server, the log back into OWA (well, ECP) and test the ”Settings for POP, IMAP, and SMTP access…”  link again. It should now show the settings specified:

For further reading check out Set-IMAPSettings, Set-POPSettings and Set-ReceiveConnector.

(Just a footnote- thanks to Jag at Microsoft for providing this information)

Tagged with:
 

Announcing Exchange 2010 Service Pack 2

On 2011-10-05, in Exchange 2010, Mailserver, by Mattias Jönsson
0

The Exchange Team is pleased to announce that in the second half of calendar year 2011 we will be releasing Exchange Server 2010 Service Pack 2 (SP2) to our customers. With SP2, the following new features and capabilities will be included:

  • Outlook Web App (OWA) Mini
  • Cross-Site Silent Redirection for Outlook Web App
  • Hybrid Configuration Wizard
  • Address Book Policies
  • Customer Requested Fixes:

Read more about this at ”the exchange team blog”
http://blogs.technet.com/b/exchange/archive/2011/05/17/announcing-exchange-2010-service-pack-2.aspx

Tagged with:
 

Link: http://gsexdev.blogspot.com/2009/07/setting-single-line-view-in-owa-for.html

Early this year i posted a script for turning the reading pain off and on in OWA 2007 using some EWS proxy code in powershell. The same thing can also be done
using the EWS Managed API as well as other properties in OWA like the single line view which someone asked about this week. So here is a script that can be
used for setting both of these values.

Single Line View property,

Like the reading pain this OWA setting in controlled by a property that is set on each folder

http://schemas.microsoft.com/exchange/wcmultiline
(mer…)

Tagged with:
 

From http://blogs.technet.com/b/ucedsg/archive/2010/04/22/how-does-federated-calendar-sharing-work-in-exchange-2010.aspx

What are the benefits of Exchange 2010 Federated Sharing?

  • Easy setup of external data sharing
  • Broader reach without additional steps to setup
  • More secure with controls for admins and users

Exchange Federated Sharing is convenient

  • Sharing between two orgs or two people
  • No trusts or service accounts
  • No end user accounts and credential prompts

Exchange Federated Sharing is secure

  • Control which orgs you share with
  • Control which users can share and at what level

Exchange Federated Sharing works with online services

Tagged with:
 
Mailbox Server Role: 

1.Mailbox\Public Folder Database Status – Get-MailboxDatabase –Server “Name of the Server” –Status | ft Name, Mounted
2.Service Health – Test-ServiceHealth –Server “Name of the Server”
3.Storage group copy status – Get-StorageGroupCopyStatus –Server “Name of the Server”
4.Backup Status – Get-MailboxDatabase –Server “Name of the Server” –Status | ft Name, lastfullbackup, lastincrementalbackup
5.MAPI Connectivity – Test-MapiConnectivity
6.Replication status – Test-ReplicationStatus
7.Cluster Mailbox Status – Get-ClusterMailboxServer 

Client Access Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.OWA Connectivity – Test-OWACConnectivity
3.Active Sync Connectivity – Test-ActiveSyncConnectivity
4.POP3\IMAP4 Connectivity –Test-POP\IMAPConnectivity

Hub Transport Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.Queue Status – Get-Queue –Server “Name of the Server”
3.Mail Flow –Test-Mailflow

Unified Messaging Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.UM Connectivity Test – Test-UMConnectivity -ListenPort 5060/2061
3.Active Call Status – Get-UMActiveCalls

Edge Transport Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.Queue Status – Get-Queue –Server “Name of the Server”
3.Mail Flow – Test-Mailflow
4.Edge Synchronization –Test-EdgeSynchronization

Additional Note: Event Log info on corresponding server can be found out by: –Get-EventLog Application\System |Where { $_.Type –eq “erro” }

Tagged with: