When you are using FIM (Forefront Identity Manage) to provision mailboxes to Exchange (in my case Exchange 2010) and would like FIM to generate the e-mail addressen and additional proxyAdresses (aliasses) you will run into an issue!
FIM 2010 is perfectly capable of generating unique e-mail addresses and filling up the multi-value attribute proxyAddresses with all additional aliases you might want. When you look at the contents of the property proxyAddresses in Active Directory you could see something like this:
SMTP: firstname.lastname@domain.com
smtp: <first letter of firstname>.lastname@domain.com
smtp: lastname@domain.com
The fact that the first line has SMTP spelled with capitals means that this is your default reply address.
As you might know, Exchange 2010 has a default E-mail address policy called “Default Policy”. That contains something like % m@domain.com. This policy cannot be removed nor disabled.
Question: What happens when we provision a mailbox to Exchange2010 using FIM2010 and flow attribute with the content provided earlier (the thee smtp addresses)?
Answer: The mailbox will be created, however because the default e-mail address policy runs, the primary e-mail address (SMTP) will be reset to % m@domain.com! In addition, FIM will return an error stating “exported-change-not-reimported”.
The solution would be to disable the “automatically update e-mail addresses based on e-mail address policy” option. You could do this of course i.e. by using PowerShell. However, you can only do this after the mailbox is created. Within FIM, this would mean customization to able set the option on the mailbox. In addition, you would have to perform the export again to set the correct ProxyAddresses.
There is a way to solve this within one single flow. The Active Directory attribute msExchPoliciesExcluded on the userobject is used to specify whether or not the “automatically update e-mail addresses based on e-mail address policy” option is selected on the mailbox. If the option is selected, this attribute empty and when it is not selected, it contains the value {26491cfc-9e50-4857-861b-0cb8df22b5d7}.
You might have guessed the solution by now, I simply flow the string “{26491cfc-9e50-4857-861b-0cb8df22b5d7}” to the attribute msExchPoliciesExcluded during the creation of the mailbox. By doing so the option is not selected, the Exchange Mailbox policy is not being executed for this user and the proxyAddresses I configured (within the same flow) are correctly set! This is done with code-less provisioning within the existing synchronization rule! See screenshot below.
Originally posted here: http://microsoftplatform.blogspot.com/2011/08/provisioning-mailboxes-to-exchange-2010_19.html
There have been numerous improvements regarding the way end-users experience RemoteApps in Windows Server 8. In this blog post, I’ll discuss some of the improvements that might at first seem very small but will definitely help end users to adopt Remote Apps even more.
I have done a series of blog posts, feature highlights, to show you some of the new features related Remote Desktop Services on Windows Server 8 (Beta). This blog post is the summary and contains links to all the separate highlight posts. If you have any questions related to the features below or would like to propose other new features as a highlight, feel free to contact me via my blog or @fberson. 
