November 2009 - Posts
Update Rollup 1 for Exchange Server 2007 Service Pack 2 (SP2) resolves issues that were found in Exchange Server 2007 SP2 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP2 customers.
For a list of changes that are included in this update rollup, see KB971534.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.
Get it here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=de91f994-6263-47ef-89d7-6d344997459d
The best way to understand a product is to study its architecture. If you want to learn a little bit more about Hub Transport, then this download is for you.
Many components are involved in the transport of messages through the Exchange Server 2010 mail flow pipeline. The Hub Transport server role diagram can help you understand the role each component plays in the processing of messages that enter the Exchange 2010 mail flow pipeline. Exchange administrators can use this information to help diagnose mail flow problems. The Hub Transport extensibility diagram can help you understand how the agents process a message that is in the Exchange 2010 mail flow pipeline. Developers can use this information to help create third-party agents and applications to work with Exchange 2010.
Get it here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6eb8c09a-6ea4-442a-9faa-de33265ceb84&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29#tm
Bhargav Shukla (http://www.bhargavs.com) added the Filter Pack installation on the current script and now the script can download and install the Filter Pack.
Great job Bhargav and thanks for sharing this with the community. His blog entry with the script can be seen at his blog http://www.bhargavs.com/index.php/powershell/2009/11/script-to-install-exchange-2010-pre-requisites-for-windows-server-2008-r2/ and also saved his script on this location: http://cid-a9fab8a859bc28e5.skydrive.live.com/self.aspx/.Public/Ex2010-PreRequisites-v2.ps1?ccr=6123
If you have ever tried to use ServerManagerCMD on Windows Server 2008 R2 probably you will remember this message:
"Servermanagercmd.exe is deprecated, and is not guaranteed to be supported in future releases of Windows. We recommend that you use the Windows PowerShell cmdlets that are available for Server Manager"
So.. which means that we can use the XML files to install the pre-requisites but we should start using the new method which is PowerShell. In order to use PowerShell to add Windows Features we need to know three cmdlets: Get-WindowsFeature, Add-WindowsFeature and Remove-WindowsFeature. If you open a PowerShell prompt on your Windows Server 2008 R2 and you try it won't work because you must enable the modules first, you can accomplish that task using Import-Module ServerManager cmdlet.
Using Exchange Server 2010 documentation has all the code to install all features using PowerShell capabilities, you can find this information at this page: http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2
I'm a kind of lazy guy and I always trt to create scripts to automate regular process like the Exchange Server 2010 pre-requisites. So, using Microsoft documentation I created a script that asks you what you want to install for each role, also configures the NetTCPPortSharing service and gives you the TinyURL to download the Office 2007 Converter. The script is really simple and it can be seen in the figure below:
Get it here: http://msmvps.com/media/p/1739558.aspx] and make sure to rename it to .ps1 before using it.
Get it here: http://cid-a9fab8a859bc28e5.skydrive.live.com/self.aspx/.Public/Ex2010-PreRequisites.rename?sa=717015916 and make sure to rename it to .ps1 before using it.
Thanks to Phil Grainger and Robbie for telling me that MSMVPs.org required password to download. Thank you guys!
MSExchange Team released a great tool to help mail administrators to move from their current environment to Exchange Server 2010. The name of this web interface tool is Exchange Deployment Assistant and it can be found at http://technet.microsoft.com/en-ca/exdeploy2010/default.aspx#Home.
At this point the only option available is Upgrade from Exchange Server 2003 and the other transition scenarios will be covered soon.
You will be asked a couple of questions about your environment and based on your answers you will have a list of steps to be performed and those tasks are explained step-by-step which makes really easy a migration procedure.
You can also send a lind of the current step by e-mail clicking on Send or download the checklist (Download Checklist link).
Microsoft Forefront Protection 2010 for Exchange Server (FPE) provides fast and effective protection against malware and spam by including multiple scanning engines from industry-leading security partners. It also integrates with Forefront Online Protection for Exchange to provide the defense-in-depth benefits of hosted and on-premise filtering in a single solution.
Get it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=b8a7d36f-cc8d-4335-ae60-8f27c48f3a37&displaylang=en&hash=cAyQs16hHEBYVnB%2bP3agzqA51Mb0PGLnQg%2b%2bugdWiPe0six3xFieUb5SYqPaSRR9Nfw34kg6oUKYiufP%2fPqX0Q%3d%3d#filelist
MSExchangeTeam released the Storage Calculator for the new version just one day after the release of the RTM version.
The Exchange Mailbox Server role is arguably one of the most important roles within an Exchange deployment for it stores the data that users will ultimately access on a daily basis. Therefore, ensuring that you design the mailbox server role correctly is critical to your design.
With Exchange 2010 you can deploy a solution that leverages mailbox resiliency and has multiple database copies deployed across datacenters, implements single item recovery for data recovery, and has the flexibility in storage design to allow you to deploy on storage area networks utilizing fibre-channel or SATA class disks or on direct attached storage utilizing SAS or SATA class disks with or without RAID protection. But, in order to design your solution, you need to understand the following criteria:
- User profile - the message profile, the mailbox size, and the number of users
- High availability architecture - the number of database copies you plant to deploy, whether the solution will be site resilient, the desired number of mailbox servers
- Server's CPU platform
- Storage architecture - the disk capacity / type and storage solution
- Backup architecture - whether to use hardware or software VSS and the frequency of the backups, or leverage the Exchange native data protection features
- Network architecture - the utilization, throughput, and latency aspects
Read more at source: http://msexchangeteam.com/archive/2009/11/09/453117.aspx
Exchange Server 2010 RTM has just been released for download at Microsoft download site.
Microsoft Exchange Server 2010 helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.
- Flexible and reliable - Exchange Server 2010 gives you the flexibility to tailor your deployment based on your company's unique needs and a simplified way to keep e-mail continuously available for your users.
- Anywhere access - Exchange Server 2010 helps your users get more done by giving them the freedom to securely access all their communications - e-mail, voice mail, instant messaging, and more - from virtually any platform, Web browser, or device.
- Protection and compliance - Exchange Server 2010 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company's communications and meeting regulatory requirements.
This software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use the software. There is no product support for this trial software. You are welcome to participate in the forums to share your trial experiences with others and to ask for advice.
Get it here: http://www.microsoft.com/downloads/details.aspx?familyid=05741f65-2a7b-4070-879f-d74208d6171d&displaylang=en&Hash=p7EU0gyhY4DEbH1Kipa3uP2uqNEJBU6x8oXNokye62E1aoNzVuAdGKn5z%2bpQxA0UMZ9tlXMiGQL%2bhmwYy1%2btbA%3d%3d
If you are planning to upgrade your entire infrastructure to Windows Server 2008 R2, then Exchange Server 2007 (in case you still have it :)) won't be an issue. Today, it was posted a note about that in the MSExchangeTeam, as follows:
We always talk about listening to customers and sometimes this is written off by many as 'marketing speak'. In fact, we do take feedback seriously and no input is more important to our engineering processes than your voice.
Earlier this year we made a decision in one direction, and due to the feedback we have received on this blog and elsewhere, we have reconsidered. In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2. We heard from many customers that this was important for streamlining their operations and reducing administrative challenges, so we have changed course and will add R2 support. We are still working through the specifics and will let you know once we have more to share on the timing of this update.
Talking about Windows Server 2008 R2 and UC products, at this point OCS 2007 R2 is not supported on Windows Server 2008 R2, so keep your OCS infrastructure running on Windows Server 2008 for now. :)
Read more at source: http://msexchangeteam.com/archive/2009/11/04/453026.aspx
MSExchangeTeam posted about Remote PowerShell and some examples of scripts using remote access (exchange 2010) instead of local one (exchange 2007).
The management experience given by Exchange 2010 through PowerShell has been moved all the way from Local to Remote. This will mean that enterprise Admins will have to adjust their regular scripts to connect to Remote PowerShell instead of creating a local session.
Read more at source: http://msexchangeteam.com/archive/2009/11/02/453016.aspx