Rollup Update 2 for Exchange Server SP2 is available for download on Microsoft Download Center now.
This rollup update has 53 fixes for recently identified bugs in the application. The complete list of fixes is available at Description of Update Rollup 2 for Microsoft Exchange Server 2007 Service Pack 2
Read more about the Rollup Update – Released: Update Rollup 2 for Exchange Server 2007 Service Pack 2
Download the Rollup Update – Microsoft Download Center
Rapid transition guide from Exchange 2003 to Exchange 2010
I am glad to present this Rapid Transition Guide From Exchange 2003 to Exchange 2010.
This guide will walk you through the most important considerations and steps that you need to perform before, during, and after the deployment of Exchange 2010 server.
This guide is written for the IT administrators of an existing Exchange 2003 organization which contains small to medium scale deployments.
This guide mainly focuses on a typical transition of Exchange 2003 to Exchange 2010 environment which includes the transition of Exchange 2003 backend and front end servers to Exchange 2010 mailbox server role, client access server role and hub transport server role installed using the typical installation method.
You can download this transition guide from Here
I will appreciate your comments and feedback on this guide. Please feel free to drop me an email at geek @ msexchangegeek . com if you think this guide has some important content missing.
EDIT: There is a change in Exchange 2010 SP1 setup UI which allows you to install and configure Windows Server Features required for Exchange Server 2010 SP1 Server roles. Except those changes in the setup UI this guide remains same for the simplest transition scenario. In case you have further questions please feel free to write tome at geek @ msexchangegeek.com or use the blog contact form.
Thanks to everyone for their valuable feedback. 🙂
Today I was playing around with Exchange 2010 Certificates in my labs. My lab contains simple setup as below:
||Windows Server 2003 SP1
||Windows Server 2003 SP1
||Exchange 2003 SP2
||Windows Server 2008 R2
||Exchange 2010 RTM
In above setup the domain controller is also an Enterprise Root CA. I requested a new certificate from my internal CA and wanted to import it and then enable it for services on my Exchange server 2010 box. Something was going wrong and the certificate didn’t have a private key. After downloading the certificate the certificate had that “You have a private key that corresponds to this certificate.” missing from certificate. Just as shown below
Now the trouble was the pending request in EMC could yet import this certificate but didn’t let me assign it to the services. After spending good 2 hours at my own I found a solution at https://support.comodo.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1188
So here is the simplest way to overcome this problem.
- Download the certificate and store it at some place on the server.
- Click Start –> Run and then type MMC, press Enter.
- In the MMC Snap In click File Menu and then select Add/Remove Snap-in…
- Select Certificates.
- Click Add button.
- Select Computer account from the popped up dialog box.
- Click Finish and click OK
- Expand Certificates –> Personal –> Certificates
- Right click in the right hand side pane of the MMC Snap-in and select All Tasks –> Import…
- Specify the file path in the wizard that will pop up and Finish the wizard.
- You should see the certificate that has the little golden key icon missing. The other certificate you may see is the self-signed certificate generated during exchange installation.
- Now double click on the newly imported certificate and select the Details tab.
- Click Serial Number and write down this value or simply copy and paste it into a notepad file. Please note that you will not be allowed to copy using mouse. You can use Ctrl+C instead.
- Open command prompt and type certutil –repairstore my “serial number of certificate” and press enter.
- Now, refresh the Certificates MMC and you should see the private key paired with the certificate.
- In Certificates MMC right click on the same certificate and select All Tasks –> Export…
- Export this certificate into a .pfx file with below options selected during the export wizard.
Now open EMS and and run the following cmdlet.
- Yes, Export the private key on Export Private Key page.
- Include all certificates in certification path if possible on Export File Format page.
- Export all extended properties on Export File Format page.
- Enter the password.
- Select the path where the pfx file will be stored and complete the wizard.
[PS] C:>Import-ExchangeCertificate -FileData ([Byte]$(Get-Content -Path "C:UsersAdministrator.EXCHANGEDesktopexchangecert.pfx" -Encoding byte -ReadCount 0)) -Password:(Get-Credential).password
The credentials prompt will pop up. Enter the credentials as the currently logged on user and the password that was specified for the pfx file during export. If the credentials are correct the output should be as below:
Next, you can enable this certificate for the services you want to use it for. Again, simply open the EMS and run Enable-ExchangeCertificate -Server ‘EXCHANGE2010’ -Services ‘IMAP, POP, IIS, SMTP’ -Thumbprint ‘E7DD3356F1DC4359D9AAFD18BC7E36C06C7FC418’
While designing a new exchange organization it is really tough to do the proper capacity planning. Most of the times it is really hard to decide how to choose correct hardware configurations. HP has developed a tool for exchange 2010 sizing problems. I found this tool really cool to be used as a help for your capacity planning and related stuff.
You can download this tool from HP’s website directly. Here is the download location: HP Sizer for Microsoft Exchange Server 2010
To read the primary documentation and introduction of the tool you can also logon to http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/microsoft-exchange-server-2010.html