Today I had a nice issue with Exchange. For some kind of strange reason Exchange 2003 kept sending the same mails. Even when deleting the mails from the queue in the Exchange System Manager. A result of this was that the bandwidth was almost used 100% so I adjusted the simultaneous connections etc, without any effect.
Last week I have been working on an Exchange 2007 migration. After preparing the server for installation I installed the CAS/hub role. Everything went fine till we wanted to modify the settings of the virusscanner. For some strange reason it was not possible to add some exclusions and it was not possible to remove the virusscanner.
In a lot of cases Exchange 2007 wil be installed in the current Exchange 2003 environment. During the setup you will have to choose the Exchange 2003 bridgehead server to use for sending mail to the other organization and the internet. After this a routing group connector will be created which will be used to transport mail.
Why do it the hard way instead of the easy way, imagine you’ve got several mailboxes which you would like to disable and you’ve got them listed in a CSV file. Why shouldn’t you use Powershell to do this.
I think you may have needed it in the passed, you want to prevent that users can access a website on port 80 but also want to prevent they got an error displayed. The script below is the solution for this issue, it will redirect the user to the https version of the website.
Just as like Windows 2003 you need to add some components to Windows 2008 before you can install Exchange 2007. In this tutorial I will explain which need to be installed on which server and made some scripts for it, that’s far more easier then typing the commands one by one ;-).
Microsoft has release Rollup 6 for Exchange 2007 SP1 today. This rollup contains several fixes among which: