Outlook mail forwarding rule to external address not working
You might notice that, your Microsoft Exchange environment, if your users setup outlook rules to automatically forward their emails to an external email address, these rules will not work and the forwarded email will never leave your organization.
This is because Exchange blocks, by default,automatic forwarding message. To solve this problem you will need to follow the below steps
Exchange 2010 SP1 fails with: Setup previously failed while performing the action “Uninstall”.
While installing Microsoft Exchange 2010 SP1, the setup might fail with the following error
Setup previously failed while performing the action "Uninstall". You can't resume setup by performing the action "BuildToBuildUpgrade".
The error will look like the below depending if you are using the GUI or CLI
To solve this problem you will need to edit the registry using regedit tool
Disclaimer: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. ZeroHourSleep cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
Outlook Web Access did not initialize error on Exchange 2007 SP1 after installation of Rollup 5
Installing the rollup update 5 on a machine running Microsoft Exchange 2007 SP1 might cause your Outlook Web Access, OWA, to fail with error Outlook Web Access did not initialize
I have already experienced this error at 2 of my customers on fresh installations and I am surprised I didn't find this error documented at Microsoft (Maybe I didn't look hard enough)
The problem is that, for some weird reason, the installation of the rollup update 5 is removing the Exchange server from the Exchange Domain Servers group !
So if you are facing this issue simply find that group, add your exchange server account to it and restart your server. That should do it!
A fatal error occurred when attempting to access the SSL server credential private key.
I have faced the following error at a client when trying to setup a Forefront TMG 2010 array in a work group environment, however this error is not related to TMG itself so you might encounter it in any setup when your server is using Certificates for server authentication.
When building my Forefront TMG 2010 Array the server designated as configuration storage started logging in the the event log the below error every other minute, I did try to issue another certificate for it and even uninstalled and installed TMG again but nothing did the trick.
Error
A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030d. The internal error state is 10001.
The solution to my problem was granting the Network Service Read permission on the certificate and this is how I did it
Export and Import mailboxes in Exchange 2010 SP1
Ever since Exchange 5.5 I have been longing for an easy way to import/export mailboxes to and from PST. I have to admit that Exmerge was a pretty decent tool back then, however, although it did work, I was very disappointed by the requirements of import-mailbox export-mailbox on Exchange 2007, and I prefer to forget the frustration of using these commands with Exchange 2010 RTM.
I can happily say that all my problems are now quickly forgotten after the release of Exchange 2010 SP1 and the new commands New-MailboxImportRequest and New-MailboxExportRequest.
Prerequisites and permissions considerations
I am happy to say that installing Outlook on the server is no longer a requirement to export/import mailboxes and this, for me, was great news!
If you rush things and directly try to run New-MailboxImportRequest cmdlet it will fail with the following error, this is because, by default, no one is assigned the permission to Import and Export mailboxes.
“The term 'New-MailboxImportRequest' is not recognized as the name of a cmdlet”
Disable & Enable Organizations in Exchange 2010 SP1 multi-tenant
One thing I have noticed while working with Exchange 2010 SP1 installed in hosting (or multi-tenant) mode is the lack of the possibility to disable/enable a tenant organization.
There is a lot of scenarios when disabling a tenant organization can be very handy and useful. For example if a client didn't pay, you might want to suspend his account without deleting the whole organization and making him lose data.
I have recently developed my own scripts to disable and enable, or suspend and resume, a specific organization for a client of mine and never thought of sharing them until yesterday when this same question popped up on the technet forum and I thought that they might be helpful for some of you so here they are.
Disclaimer
I need to start with a disclaimer, I have built these script for my own use so they are not polished and might be lacking a lot of features and surely have some bugs. Although I am ready to work on them and enhance them if they find interest and feedback I am not to be held responsible for any damage they might cause to your environment. So, in short,
THE SCRIPTS ARE PROVIDED FREE OF CHARGE AND "AS IS" WITHOUT WARRANTY OF ANY KIND, AND MAY NOT BE ERROR FREE. ANTOINE KHATER, THE AUTHOR OF THESE SCRIPTS, DISCLAIM ALL WARRANTIES AND LIABILITY FOR ANY KIND OF DAMAGES AND/OR LOSS.
