iPhone meet Exchange 2010 – New book

On 2012-04-12, in Exchange 2010, by Mattias Jönsson

From blog : Tony Redmond’s Exchange Unwashed

If you’re an Exchange administrator who has to cope with the slings and arrows of outrageous Apple technology, aka the iPhones and iPads that have become essential business equipment over the last few years, you could do worse by placing an early order for iPhone with Microsoft Exchange Server 2010 – Business Integration and Deployment.

The chapters are as follows:

1. Introduction to Exchange 2010 and iOS devices.
2. Implementation and Architecture Planning (for the deployment of Exchange 2010 and iOS)
3. Connecting iOS devices to Exchange 2010 (includes the basic networking configuration that’s required)
4. Connecting iOS devices to Exchange Online/Office 365 (includes setting up an Office 365 domain and testing connectivity to the new domain)
5. Creating and enforcing ActiveSync policies
6. Configuring certificate based authentication for Exchange 2010
7. Provisioning iOS client devices using the iPhone configuration utility
8. Sharing mailboxes and calendars
9. iOS client device management

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


Tagged with:

In a migration environment with exchange 2007 and exchange 2010 we have client (outlook 2007) that hangs 10 seconds when sending a meeting that books a resource mailbox residing on Exchange 2010 mailbox server.

Microsoft say:
In a support case to microsoft they acknowledge this problem as a feature in exchange 2010 when booking resourcemailboxes. They state that this is a fix (code release) for office 365 (clod exchange) where microsoft is not using public folders. This fix is for Outlook 2003 clients when connection to the clod. Outlook 2003 use public folder for accessing free/busy information and when microsoft closed this door in office 365 they had to get a workaround for outlook 2003 users. This fix is intercepting outlook 2003 calls to public folder on a mailbox server and redirecting them to webservices (EWS) on a CAS on behalf off mailuser.

Outlook 2010 is not affected like outlook 2007.

This is not a correct picture yet. A better one is coming soon.
1. Client try to get free/busy information from it’s mailboxserver holding public folder
2. Mailbox server trying to access https://webmail.org.se/EWS/Exchange.aspx for free/busy information behalf off mailuser insted of accessing public folder.
4. CAS answering mailboxservers request for information.

So this is a fix for exchange in clod only!? – Yes and No…
It is a fix release for both clod and on premise. So it is affection or local environment to and that is bad!

We noticed the following event id’s being generated on the Mailbox server MBX.org.se
Time:     2011-04-01 10:39:52
ID:       4002
Level:    Error
Source: MSExchange Availability
Machine:  MBX.org.se
Message:  Process 2796: ProxyWebRequest CrossSite from S-1-1-0 to https://webmail.org.se/EWS/Exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it

Why do we have a problem?
Our Exchange 2010 mailbox servers could not connect to https://webmail.org.se/EWS/Exchange.asmx
Well, we can not access Internal URL for EWS from our mailboxservers.
Is this correct? No!
But our network design is not letting us do this right now.
When we worked around this problem we no longer have a problem with outlook 2007. So thats good!
But this proxy fix for outlook 2003 in the clod is still affecting outlook 2007 even thou we no longer see a problem.

Patch from Microsoft
Microsoft is releasing a option in Exchange 2010 SP1 RU4. You will have a way to disable the Availability intercept by using the following registry value.

DWORD: DisableAvailabilityServiceCalls
Value: 1 ( Disable)

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: