The wonderful colleague who has succeeded me as the main ActiveRoles Server admin here at Awesome German Auto Parts Manufacturer (awesome.com) ran into trouble last week while trying to find out which user had a proxy address that she was trying to assign.
email@example.com is not quite as unique as one might think, even in a country with loads of rather long family names, and when a holder of a
firstname.lastname@example.org leaves, there’s possibly another who would like to have it, and who outsiders are trying to reach at that address.
So my successor cleverly noticed that
Get-QADUser has a
-ProxyAddress parameter, so tried this on the stubborn address:
Get-QADUser -ProxyAddress "email@example.com"
She tried it on her own address, as she was quite sure that one was in there.
Resourceful lady that she is, she started Googling.
Nothing beyond this old Dmitry Sotnikov post: http://dmitrysotnikov.wordpress.com/2010/08/13/manage-email-addresses-without-exchange-cmdlets/
His example shows the address type (in this case, x400) prefix on the searched-for address, but doesn’t state that this is necessary for this parameter to work properly.
Because I’d hit my own wall on Lync emergency calling configuration, I experimentally tried:
Get-QADUser -ProxAddress "smtp:firstname.lastname@example.org"
Just to check, I tried it without whispering “