This post is to clarify that a previously discussed feature that was intended for Exchange 2010 SP1 is not present in the SP1 final build.
Update: This feature is now live in the Exchange 2010 SP2 RU3 build of Exchange.
The feature I am referring to is the allow/block cross site RPC Client Access connections. This sometimes comes up in workshops and discussions with clients regar… Read the rest “Outlook & Restricting DAG Cross-Site Connections”
Exchange 2007 & 2010 use a different message routing design than Exchange 2003. This is an important aspect to understand when transitioning from Exchange 2003 upwards due to the change in behaviour.
TechNet has articles that discuses these concepts :
Exchange 2010 http://technet.microsoft.com/en-us/library/aa998825.aspx
Exchange 2007 http://technet.microsoft.com/en-us/library/aa998825(EXCHG.80)… Read the rest “Exchange 2007 & 2010 Least Cost Routing”
In the Exchange 2003 world and below, those administrators looking to automate and control the behaviour of MAPI profiles on user’s desktops quickly became familiar with tools like:
For a refresher on such joys of .PRF files etc. take a peek at:
Whitepaper: Configuring Outlook Profiles by Using a PR… Read the rest “Exchange & The Autodiscover Web Service”
Some featured white papers on the Exchange TechNet site:
Technical White Papers for Exchange Server 2010
White Paper: Understanding the Relative Costs of Client Access Server Workloads in Exchange Server 2010
http://technet.microsoft.com/en-us/library/ff803560.aspx
White Papers: Exchange 2010 Tested Solutions
Remote Desktop Connection Manager (RDCMan) is a great tool to consolidate multiple RDP connections into a single window to prevent desktop clutter.
Update 24-6-2021: RDCMan 2.8.1 is available. Please see here.
Update 19-11-2014: RDCMan 2.7 is now available. Please see here.
Update 29-3-2017: 2.2 is no longer available for download - please use the 2.7 download link.
The tool can be downloaded from… Read the rest “Remote Desktop Connection Manager Download (RDCMan) 2.2”
The Exchange 2010 RTM (Release To Manufacturing) build has now reached the end of its support lifecycle. Customers should upgrade to SP1 to continue to receive support (amongst many other good reasons!).
The Exchange 2010 lifecycle can be viewed here:
Full details about the Microsoft lifecycle policy can be viewed here
http://support.microsoft.com/lifecycle/
My good friend Dan wrote a great blog entry about automating the installation of the required Windows OS prerequisites for an Exchange 2010 install. You can read it here.
Over and above this, Exchange 2010 SP1 adds a new setup switch
/InstallWindowsComponents
Exchange 2010 SP1 Setup has been improved to allow you to install the required Windows roles and features. If you select th… Read the rest “Best way ever to install required OS components for Exchange 2010 SP1 install!”
Perhaps the most significant change between Exchange 2007 and Exchange 2010 is the move to channel Outlook connectivity through the CAS role. In Exchange 2007 Outlook would connect to the mailbox role, whilst other protocols (POP, OWA, IMAP etc.) would leverage the CAS role.
In Exchange 2010 this means that we now find two new services installed on the CAS role: