Is this just a blog entry to justify the use of managed code on exchange? this has caused problems for many large IT depts and if this had been thought through from an end user perspective it wouldn't have been implemented.
It is also abit irresponsible putting an outdated blog link when a valid and updated KB exists for this issue: http://support.microsoft.com/kb/944752
blogs are what you may call "do so at your own risk" given that they are not official microsoft support / premier documentation.
one item from the KB that was a modification from the original v1 is that crl.microsoft.com in the host file pointing to local host no longer seems to work with SP2 + installation and to install you need to modify IE adv security setting "check for publishers certificate revocation". also do this to speed up exch shell loading and scripts.
So given this, i would expect that your next step will be to update the "Offical" KB with the information within this "non supported" blog.
mike