A few weeks ago I got interviewed by RunAsRadio, who delivers weekly IT Pro podcasts.
The topic for my interview was Federation in Exchange 2010.
Information workers frequently need to collaborate with external recipients, vendors, partners, and customers and share their free/busy (also known as calendar availability) and contact information.
While federation has been around for a while in Exchange, the 2010 goes into a web services model that allows simple, limited visibility for other organizations Exchange 2010 users into your calendar and contacts. The trust is established based on the Microsoft Federation Gateway (a trust broker), which makes it easier for the admin guys to set it up.
Listen to the Podcast here: Peter Schmidt Federates Exchange 2010!
Read more about Exchange 2010 Federation on TechNet.
Here is some notes from a recent issue error that I encountered this week with an Exchange 2010 server configured for Outlook Anywhere. For some reason Outlook Anywhere stopped working and the Outlook Anywhere (RPC over HTTP) clients were no longer able to connect.
After checking all the basics in Exchange, like:
- Confirming the OA settings
- Certificates (not expired and common name)
- Firewall rules
- Autodiscover etc.
Testing Http Authentication Methods for URL https://mail.MyDomain.com/rpc/rpcproxy.dll
The HTTP authentication test failed.
Additional Details
An HTTP 500 response was returned from Unknown
For Outlook Anywhere confirm the following:
- That your domain “mail.mydomain.com” is the common name in the certificate and that the output is correct in the EXPR provider
- That redirection is not configured on the IIS virtual directory
- Check the SSL settings of /RPC virtual directory, it should be: Require SSL (Checked), Require 128-bit SSL (Unchecked), Client certificates: Ignore
If the above does not help, you may have to reinstall the RPC Proxy component, I found that reinstalling the RPC Proxy component solved my problem and according to several searches on Google Bing, it seems several others have experienced similar problems with OA and Exchange 2007 and the solution was the same.
The process of reinstalling RPC Proxy is:
- Disable Outlook Anywhere using EMC or EMS
- Remove RPC proxy component using the command: servermanagercmd -r rpc-over-http-proxy
- Reboot the server
- Install RPC proxy component using the command: servermanagercmd -i rpc-over-http-proxy
- Enable Outlook Anywhere
- Restart Microsoft Active Directory Topology service
- Check if the issue still exists
The reinstall of the RPC Proxy component solved the problem for me.
A video has been posted on the Microsoft Master Blog showing off the level of details, that you would go through when attending the Microsoft Certified Master Training on Exchange.
Have you ever wondered what we actually do in the classroom during Microsoft Certified Master rotations? Well, here is a 30 minute summary of the Exchange 2010 header firewall from Brian Reid, one of our regular MCM instructors.
The video is made by Brian Reid, one of the MCM instructors.
See the 30 min. video on the Master Blog: MCM Exchange Video Preview.
An article has been published on the TechNet wiki by Henrik Walther about “Exchange ActiveSync Considerations When Using Windows Phone 7 Clients”.
There was a previously article “Exchange ActiveSync comparison table”, which listed all the EAS features of the different phones.
This new article goes through EAS features and Windows Phone 7, since it is important to note that Windows Phone 7 devices only support a subset of the Exchange ActiveSync (EAS) policies available with Exchange 2003 SP2, Exchange 2007, and Exchange 2010.
Read the full wiki article: “Exchange ActiveSync Considerations When Using Windows Phone 7 Clients”.
Microsoft has released Exchange 2010 Visio Stencils.
Use this stencil to create Visio drawings that contain Exchange 2010 objects. These shapes include icons for the following:
- Exchange 2010 server roles
- Features new to Exchange 2010 SP1
- Networking, telephony, and Unified Messaging objects
- Active Directory and directory service objects
- Client computers and devices
- Other Exchange organization elements
Download: Microsoft Exchange 2010 Visio Stencil
Great blog post by Robert Gilles (MSFT) on You has me at EHLO, the post “Robert’s Rules of Exchange: The Scenario” is his first post in a series of scenario based and real life inspired blog posts on Exchange 2010 implementations.
Today we kick off Robert’s Rules of Exchange, a series of blog posts in which we take a fictitious company, describe their existing Exchange implementation, and then walk through the thought processes behind the design, installation, and configuration of their Exchange 2010 environment. Robert’s Rules of Exchange: Table of Blog Contents will serve as a reference for all posts in this series.
Read his first post “Robert’s Rules of Exchange: The Scenario”.
Exchange SP1 fails during the install of the mailbox role, with the following error:
"Couldn't resolve the user or group "mydomain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.".
Couldn't resolve the user or group "mydomain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.
The setup where I experienced this issue, is a new Exchange 2010 install, installed into an existing Exchange 2007 environment. But I have seen that others have similar issues, when upgrading to SP1.
There does not seem to be any official KBs on the issue. Just a lot of people experiencing the same issue. (reference from google). But I found a valid solution to the issue.
Read more…
I have seen this issue at several customers, when migrating from Notes (Domino) to Exchange 2010 using the Quest Notes Migrator for Exchange (Quest NME).
The problem is ActiveSync not working correct on Nokia phones. Only new calendar items (after the migration) is synced to the Nokia phones. All older and therefore migrated calendar items are not synchronized to the Nokia phones.
I have now come across a great script from Kent, which corrects the calendar items.
Read his blog post and get the script here.
Follow Me