In this post I'll talk a bit about the legacy Recipient Update Service (RUS) and explain the changes made to it for Exchange Server 2007.
Recipient Update Service
The Recipient Update Servi...
Updated Jul 01, 2019
Version 2.0
Blog Post
Evan, thanks for the information which is really useful. I've been playing with Beta 2 and overall think it's awesome (without even firing Outlook 2007 up as yet).
I do think though that there was some elegance to creating a user with mailbox from AD Users & Computers, even with the associated problems and penalties. What springs to mind in particular is that within the same app, you created that user with mailbox, and then were easily able to add them to groups or set other attributes. Not to mention that you were fully in control of the OU in which the user was created.
Yes, I see that we can select an existing user, and that's cool. But it means two applications. I don't know about you, but I like to keep things as quick and easy as possible for my help desk staff.
On top of which I'm really not enthused about the need to manually associate Managed Folder Mailbox Policies and ActiveSync policies to each user. That plainly and simply sucks- you'll happily apply new email address policies to all users, but it seems nothing else.
I'm sorry - I'm very enthusiastic about Exchange 2007 and I think there's a lot there that's a huge step in the right direction. But please think about your customers and pay attention to the little things too. Simple things like (for example) new integration to AD Users & Computers to fix my first gripe (or alternatively, expand the capabilities of recipient configuration), and consistency in the application of policy to users. After all, you have filters there for things like Company - you could expand the filters a little incidentally - so why not use them to their best extent, an engine that automatically applies the policy to existing users and then by default to new ones. It couldn't cost much in development time, surely.
Perhaps if I were speaking from the perspective of someone with MIIS or other software, I'd be more relaxed about the first issue - sure, it sounds reasonable to me to schedule a periodic script (not too far different from RUS after all). But I'm not, and neither would a significant number of customers. And the policy stuff is just plain stupid; after all, what if I ever dare to think of changing it ...
Anyway, thanks for your time. Again, I'm enthusiastic about 2007, it really is fantastic - but take care of the fine detail!!!!
I do think though that there was some elegance to creating a user with mailbox from AD Users & Computers, even with the associated problems and penalties. What springs to mind in particular is that within the same app, you created that user with mailbox, and then were easily able to add them to groups or set other attributes. Not to mention that you were fully in control of the OU in which the user was created.
Yes, I see that we can select an existing user, and that's cool. But it means two applications. I don't know about you, but I like to keep things as quick and easy as possible for my help desk staff.
On top of which I'm really not enthused about the need to manually associate Managed Folder Mailbox Policies and ActiveSync policies to each user. That plainly and simply sucks- you'll happily apply new email address policies to all users, but it seems nothing else.
I'm sorry - I'm very enthusiastic about Exchange 2007 and I think there's a lot there that's a huge step in the right direction. But please think about your customers and pay attention to the little things too. Simple things like (for example) new integration to AD Users & Computers to fix my first gripe (or alternatively, expand the capabilities of recipient configuration), and consistency in the application of policy to users. After all, you have filters there for things like Company - you could expand the filters a little incidentally - so why not use them to their best extent, an engine that automatically applies the policy to existing users and then by default to new ones. It couldn't cost much in development time, surely.
Perhaps if I were speaking from the perspective of someone with MIIS or other software, I'd be more relaxed about the first issue - sure, it sounds reasonable to me to schedule a periodic script (not too far different from RUS after all). But I'm not, and neither would a significant number of customers. And the policy stuff is just plain stupid; after all, what if I ever dare to think of changing it ...
Anyway, thanks for your time. Again, I'm enthusiastic about 2007, it really is fantastic - but take care of the fine detail!!!!