October 2009 - Posts
I've just read In the UC blog an entry where the UC team states that DAG will be supported on Exchange Server 2010 Standard Edition. Isn't that cool? :)
On the server side, Exchange Server Standard will now support high availability, so all customers can take full advantage of the new database availability group capabilities. Exchange Server Enterprise enables configurations with up to 100 databases per server.
Read more at source: http://blogs.technet.com/uc/archive/2009/10/27/exchange-2010-revving-the-engines-for-launch.aspx
If you use Antigen/ForeFront Security and you are using any of these engines: AhnLab, CA, Sophos and also SpamCure, then you must read the post that the ForeFront Team published. Basically, those ones won't be longer updated as explained below:
The AhnLab, CA, and Sophos engines will be retired on Dec. 1, 2009. After December 1st, customers will not receive any updates for these retired engines. In order to make sure your Antigen and Forefront products continue to scan efficiently and effectively for malware, any customers running the AhnLab, CA, or Sophos engines must DISABLE these engines before Dec. 1, 2009 and select from the new set of five engines - Authentium, Kaspersky, Microsoft, Norman, and VirusBuster.
Read more at source: http://blogs.technet.com/fss/archive/2009/10/21/action-required-by-dec-1-2009-keep-your-protection-current.aspx
Exchange Server 2010 is just around the corner and today we are going over the witness server/directory creation in a regular member server. The first question is why? Well, we already know that in this new release we can have only 2 servers and provide high availability for all roles the essential roles with those two servers. Remember that the same thing was accomplished with 4 servers in Exchange Server 2007 (2 CAS/HUB and 2 MBX - CCR).
However DAG witness has some requirements, such as: it cannot be a member of the DAG; must be in the same forest; it can run on top of Windows Server 2003/2008/2008 R2.
So, if you have only two Exchange Servers and wants to create a DAG a member server must be used as DAG witness server. In order to do that make sure that the group Exchange Trusted Subsystem is added to the local administrators of the server that will be the witness server, as shown in the figure below. After that you will be able to create a DAG using Exchange Management Console.
Really nice post from MSExchangeTeam explaining the Exchange 2010 version-based routing. Long story short, Exchange 2010 Hub will communicate only with a Mailbox Exchange 2010, if you have an Exchange Server 2007 Mailbox a Hub 2007 is required to communicate with the legacy mailbox.
By now, you've seen a few of our Spotlight on Exchange 2010 postings. If you have, hopefully you're excited about the great work that has been going on to make Exchange 2010 the best version of Exchange yet. So then the practical side of you kicks in and starts to wonder what it is going to take to start utilizing these new features when the time comes. Certainly, rolling out a new version of Exchange is rarely an endeavor to be entered into lightly.
In the interest of making certain that you can begin planning early and as informed as possible, I want to call out a requirement that we had to put in place for Transport server roles in order to deliver a quality product with cool new features. This requirement is often referred to as "version-based routing" or just "versioned routing."
What this requirement means
Simply put, this requirement means that Exchange 2010 Hub Transport servers and Exchange 2010 Mailbox servers will only communicate with each other. Also, it means that Exchange 2007 Hub Transport servers and Exchange 2007 mailbox servers will only communicate with each other. However, any version Hub is able to communicate (via SMTP) to any other Hub server. So, for a user on Exchange 2007 to be able to send to a user on Exchange 2010 in the same site, the mail must pass through both Hub servers.
Read more at source: http://msexchangeteam.com/archive/2009/10/14/452859.aspx
Some of the ForeFront names, such as ForeFront Server Security Management Console, ForeFront Protection Manager, ILM or ForeFront Identity Manager make you crazy to figure out which is the name of current version and the next version? Well, the product family is not small and specially at this point they may cause some confusion with so many names.
This page can help you out to memorize the current product names and their future names: http://www.microsoft.com/Forefront/en/us/trial-software.aspx.
Exchange Server 2010 introduced the certificate management through Exchange Management Console. In order to manage it, just expand Server Configuration and click on the required server on the left and on the bottom you will see certificates available for that server and at the Toolbox actions you will be able to all available options.
In this post we are going to renew the certificate created during the server installation. Let's click on Renew Exchange Certificate as shown in the figure above, and in the first wizard page we can select the services associated to the certificate.
The renew of the self-signed certiicate will overwrite the current certificate, the console requires a confirmation, just click Yes.
Then, a three step will be performed in background and the results will be displayed in the Completion page. Just click Finish and enjoy your new renewed certificate.
By the way, the process to renew the self-signed certificate using Exchange Management Shell was posted a long time ago but can still be used in Exchange 2010: http://msmvps.com/blogs/andersonpatricio/archive/2008/04/08/how-to-renew-a-built-in-certificate-in-exchange-server-2007.aspx
Forefront Identity Manager 2010 (FIM), formerly known as Identity Lifecycle Manager "2" delivers an integrated identity management solution with powerful self-service capabilities for Office end-users, rich administrative tools and enhanced automation for IT professionals and .NET and WS-* based extensibility for developers. FIM 2010 provides organizations with unique workflow driven solutions to manage user accounts, passwords, groups and distribution lists as well as certificate-based credentials such as smart cards, using identity-based policies that can span across Windows and heterogeneous environments. And when you download the latest beta software, you're automatically registered to access valuable resources assembled in one convenient location.
Microsoft Forefront Identity Manager 2010 is the official name for Microsoft Identity Lifecycle Manager "2". This was announced as part of Microsoft's strategy for Business Ready Security. You will continue to see the ILM "2" name for some time including in the software available below.
Get it from here: http://technet.microsoft.com/en-us/evalcenter/cc872861.aspx