November 2007 - Posts
Now is official, Exchange Server 2007 will be released on November 30, and we will be able to get it from here: http://go.microsoft.com/fwlink/?LinkId=104387
All new features were summarized on this page: http://go.microsoft.com/?linkid=7844544
The Microsoft Office Communications Server 2007 Best Practices Analyzer is designed for administrators who want to determine the overall health of their Office Communications Server 2007 servers and topology.
The Microsoft Office Communications Server 2007 Best Practices Analyzer Tool is a diagnostic tool that gathers configuration information from a Microsoft Office Communications Server 2007 environment and determines whether the configuration is set according to Microsoft best practices. You can install the tool on a client computer that runs Microsoft .NET Framework 2.0, or on a server that runs Office Communications Server 2007.
Note: Although you can install the Office Communications Server 2007 Best Practices Analyzer directly on the computer that runs Office Communications Server 2007 Server, we recommend that you install and run this tool on a client computer.
The tool uses set of configuration files to gather information from the Office Communications Server 2007 environment. It compares this data against a set of pre-defined rules for Office Communications Server 2007, and reports potential issues. For every issue reported, the tool provides the current configuration in the Office Communications Server 2007 environment, and the recommended configuration.
With the proper network access, the tool can examine your Active Directory and Office Communications Server 2007 servers to do the following:
- Proactively perform health checks, verifying that the configuration is set according to recommended best practices
- Generate a list of issues, such as suboptimal configuration settings or unsupported or not recommended options
- Judge the general health of a system
- Help troubleshoot specific problems
- Prompt you to download updates if they are available
- Provide online and local documentation about reported issues, including troubleshooting tips
- Generate configuration information that can be captured for later review
You can download it from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=1B90993C-072A-4C84-B385-B76D23B2F27C&displaylang=en
This download contains a stand-alone version of the Microsoft Exchange Server 2007 SP1 Release Notes.
Get it from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=5770BD59-376E-42EC-B940-BE6225CD97FF&displaylang=en
Today was released an article about how to set up the webservices URLs in Exchange Server 2007, this article can be found at http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-exchange-server-2007-web-services-urls.html
If you have any questions or suggestions about this article, please drop me a line or leave a comment.
I will describe below some points that you should validate in your Exchange Server 2003/2000 to allow the message flow, here are they:
- Validate which IP address Exchange Server 2007 resolves from the Exchange 2000/2003 server, try to connect in the port 25 of that server
- Validate if the SMTP Virtual Server in Exchange 2000/2003 is listening in the correct IP Address (same IP that Exchange Server 2007 is resolving)
- Validate if there is any connection filter blocking connection from Exchange Server 2007
- If you are still having problems, try to stop your Antivirus software and validate if it works
- If you have more than one Exchange 2003/2000 you can manage them in the Routing Group Connector, you can do that through Set-RoutingGroupConnector cmdlet in Exchange Server 2007
Do you have another point to be considerating during the troubleshooting, please post a comment and I will be adding to this current list.
I have been working during this week in a transitioning from Exchange 2000 to Exchange Server 2007, then I've decided to talk a little bit about the process using some key points that can be helpful for you when you need it to do the same.
During this transitioning I currently have: 2 DCs running Windows 2000 SP4 and 1 Exchange Server 2000 with SP4.
My main steps were:
Run ExBPA to fix all the issues before installing Exchange Server 2007 (some issues such as: Exchange 200 Native mode for Active Directory, Exchange Organization as native mode, remove the ADC Connector and etc..)
Upgrade the current Forest and Domain to support 2003 DCs, you can be using this kb: http://support.microsoft.com/kb/325379/
Build at least one DC/Global Catalog running Windows 2003 SP2
Move FSMO for DCs 2003, you can be using this kb http://support.microsoft.com/kb/223787
Transfer at least Schema Master for this new server
When we have DCs and GCs Windows 2000 we have to install Exchange 2007 through command line, so here are the command syntax:
setup.com /mode:install /role:ht,mb,ca /dc:<dc-wk3> /legacyroutingserver:<2k or 2k3 exchange server name>
To move mailbox we have to use command line as well, as it follows:
Move-mailbox <alias> -TargetDatabase "<Exchange Server 2007 mailbox database name>" -DomainController <DC 2003 name> -GlobalCatalog <DC 2003 name>
I had some issues in the message flow between Exchange Server 2007 and Exchange 2000 that I will be explaining in a next post.
Exchange Server 2007 has a lot of new exciting features, one of them is a new cmdlet called Test-ReplicationHealth that will validate all aspects of replication. We can see an example of the cmdlet in action in the figure below: