Starting from Exchange 2010 it is possible to import pst files using the New-MailboxImportRequest cmdlet. By default this cmdlet can’t be executed. This is caused by the fact that the New-MailboxImportRequest cmdlet is not a part of the default RBAC groups.
When you have worked with Exchange 2010 you might know that some things only can be configured by using the Exchange Management Shell (EMS). A few examples are:
During a migration you may encounter the issue that incorrect aliasses are used, for exampe spaces or incorrect characters in the alias. Microsoft has published a nice script fix-alias.ps1. There are some limitations when using this script. Because of this I modified the script a bit and added the following features:
Some times it can be very usefull to automate things by creating a script. Of course you will first have to think if it is usefull to automate it or just decide to do it manually. Which option you chose is really hard to say but let’s say if you have to modify more then 50 items becomes very interested to use a script.
Microsoft has released Rollup 4 for Exchange Server 2007 SP3. This rollup will fix the following issues:
In this article we will have a look at Trend Micro Scanmail (SMEX) 10. This is the latest version of Trend Micro’s antivirus/antispam solution for Microsoft Exchange Server.
Microsoft has released Rollup 4 for Exchange Server 2010 SP1. This rollup will fix the following issues:
During the removal of an Exchange 2003 cluster I had the issue that I couldn’t remove the Exchange Virtual Server from the Cluster Administrator.
During the removal of an Exchange 2003 cluster I found an issue after the removal of Trend Micro Scanmail (SMEX) 8.0. After the deinstallation was completed the Cluster Administrator started with an error. Once of the things I expected to cause the issue was the resource object from SMEX which was still there. This could be solved easily by removing the default procedure for removing cluster resources.
