The problem still remains: What's the best way to set Delegates AFTER a migration? You could use this as a learning opportunity for your users: let THEM set their own darn delegates, thank you very much.
But sometimes your user community is more demanding and wants (nay, NEEDS) this all done for them.
We have an account in Connecticut (thank you, Vince) who wrote up this account of how to set Delegates for calendars in Exchange 2007 (do not attempt on E2K3). This assumes your Exchange Admin account with adequate permissions to execute (and you know that is its own separate issue) is called "sumatra"
- Logon to Windows box as yourself.
- Delete the "sumatra" account if it is in C:\documents and setting. If it is not there then it will be after this first account adjustment. You are good for the 1st run.
- Locate the Outlook app and "Run as..." and run as the Domain Administrator
- Setup the user you want to add Delegates to
- Once done you will be asked to logon, again. This time logon as "sumatra"
- The account will then be setup in the app.
- Set your Delegates.
- When done close Outlook
- Delete the sumatra account (as mentioned in step 2) and the administrator account.
- Repeat steps 3-9 until you are done with your account setup.
All bets are off once sp1 hits the street -- we can almost guarantee this process will change.
2 comments:
So, did the process change for SP1? Any follow-up advice? This is an annoying hole in Exchange administration, don't you think? Sure, it would be nice if users could/would do this themselves, but it doesn't always happen that way. And then you have users on Macs...
Actually SP1 includes some new capability for setting Delegates programmatically. We haven't had time to dig into it yet, but we'll post it when we do.
Post a Comment