• "It is not science that is arrogant: science can be defined as 'humility before the facts' - it is those who refuse to submit to testing and make unsubstantiated claims that are arrogant. Arrogant and unjust." - Stephen Fry, concerning the libel suite against Simon Singh

• Archives

  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • April 2009

• Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org
• Search for:

• Blogroll

  • Alex’s Blogthing
  • Glen’s Exchange Dev Blog (no relation)
  • Inside Entourage by Amir
  • Just Another ITS Systems Guy
  • My “other” blog - Spyglass’ Ramblings
  • The Entourage Help Blog
  • The Microsoft Exchange Team Blog

• Spyglass' Ramblings (RSS Feed)

  • 3D Mandelbrot Sets (Sort Of) November 19, 2009
  • I Can't Believe I Totally Missed RH Day! November 19, 2009
  • Stupidity on Parade VIII November 5, 2009
  • The Latest Song Stuck in My Head November 5, 2009
  • Making Lilypond work with TeXShop November 1, 2009
  • Pirates, keep an eye on your parrots! October 29, 2009
  • Converting iPhone Voicemails to Custom Ringtones October 29, 2009
  • DSCOVR May Fly After All October 23, 2009
  • This is why Alton Brown rocks October 9, 2009
  • Denial of Reality October 1, 2009

Every once in a while, we get a ticket complaining about meeting invites generating an NDR claiming that a mailbox (not belonging to any of the invitees) does not exist. Invariably, this turns out to be due to one of the invitees having a delegate whose mailbox has been deleted, and this can be a pesky problem to resolve.

Here is a summary of how the delegation process works under the hood, and how to deal with “dangling” delegations when mailboxes are deleted.

Suppose you have a mailbox for user A who wishes to make user B a delegate.  When the delegation is made the following takes place:

1. Appropriate sharing permissions are placed on the relevant folders in user A’s mailbox, depending upon the permissions set with the delegation tool.
2. If the checkbox for forwarding meeting requests is set, a special hidden forwarding rule is created in user A’s mailbox.
3. User B is added to user A’s publicDelegates attribute (the send-on-behalf-of field), and user A is added to the publicDelegatesBL attribute of user B. This does not always happen in recent versions of Outlook, especially when the person trying to set the delegation is not actually the owner of mailbox A. See this earlier posting for more information on this issue.

Unfortunately, if the mailbox for user B is deleted, their publicDelegatesBL entry in AD gets cleared out, so there is no direct way to track down who they might have been a delegate for. Even more problematic, when user B’s mailbox is deleted, the hidden forwarding rule in mailbox A does not get updated, which is why it is important to always remove someone as a delegate prior to their mailbox being deleted.

Assuming that we can narrow down whose mailbox has the orphaned delegation, we can manually fix this by using the MFCMAPI tool to delete the hidden forwarding rule (the instructions being contained in the README file accompanying MFCMAPI). Unfortunately, if there are other delegates to that mailbox, the forwarding for them would break as well, so all of those delegates would need to be removed and re-added, which requires logging directly into the mailbox in question.

If the owner of the problematic mailbox is okay with this, the Exchange administrators can go ahead and nuke that hidden rule from their mailboxe, but the mailbox owner will need to go in afterwards and redo their delegations, or the Exchange administrators could do that with their permission.

Wired.com has a nice tutorial on the topic.

Microsoft Forefront Protection 2010 for Exchange Server is now available. Capacity planning guidance for this product has also been published.

Also of note is that Forefront support for the AhnLab, CA, and Sophos engines is being retired on Dec. 1, 2009. The new set of available scan engines will be Authentium, Kasperky, Microsoft, Norman, and VirusBuster.

The only piece now missing is a 2010-friendly version of DPM for backing up Exchange.

Exchange 2010 RTM bits have been made available for download. Weee!

Also, the Exchange 2010 Mailbox Server Role Requirements Calculator is out and I’m reading through the documentation on it now. (Now for a comparable tool for scaling CAS and HUB deployments and we’ll be all set.)

But wait, there is more. The Exchange Server 2010 Deployment Assistant has also been released. This is basically a wizard which asks questions about your environment, and creates deployment checklists. Very helpful, far more so than trying to wade through the mountains of TechNet docs to create such checklists (which I remember vividly doing for our transition to Exchange 2007). On the downside, the current release is only for transitions from Exchange 2003 to 2010. A version which includes transitioning from 2007 is slated for release in early 2010.

Of more immediate interest to the UT community, after I (along with our storage guru, Alex Barth) had spent most of last week cobbling together a preliminary plan for transitioning AEMS to Exchange 2010, we met with a Dell consultant for a whiteboard session to go over options for such a transition. Although there was not much depth to the session, the consultant did bring to our attention some ideas we had not really considered, so now we have more food for thought and testing to perform. My plan may very well undergo significant rewrites, but that’s okay. Actual deployment is a long way off, which gives us ample time to refine our plan so that, hopefully, it will go off with a minimum of problems.

http://msexchangeteam.com/archive/2009/11/05/453052.aspx

While it isn’t related to Exchange (or anything else I do here at the University), I thought I would provide a link to an article on my personal blog where I describe how I finally cajoled Lilypond and TeXShop into working together…..

Interesting….

http://blogs.msdn.com/interoperability/archive/2009/10/26/roadmap-for-outlook-personal-folders-pst-documentation.aspx

With the introduction of Exchange 2007, Microsoft introduced a new model for making free/busy information available to clients. While older, down-level clients (Outlook 2003 and older) still access free/busy by pulling it from a system Public Folder, newer clients such as Outlook 2007 retrieve free/busy information by making use of the SOAP-based Availability Service. This works quite well for most situations, thus paving the way for the eventual deprecation on Public Folders, but their are certain situations where this model is somewhat…lacking. The most common scenario where the limitations of this approach are made manifest is the case where the Outlook 2007 client is running on a workstation which is not bound to the Active Directory domain where Exchange is hosted. Unfortunately, this is a common situation for many departments in our environment.

Read more

Lots of Exchange development goodies at http://channel9.msdn.com/posts/cmayo/Exchange-2010-and-Exchange-Web-Services-Whats-New-Webcasts/

(This posting is based upon a message I recently sent to a customer, and is essentially an expanded version of this posting.)

From time to time, it is necessary to grant certain users “Full Access” permissions to log into mailboxes that are not their own in order to allow those individuals the ability to set up delegates and/or sharing permissions, especially in the case of Exchange 2007 resource mailboxes, since the underlying AD accounts for such mailboxes are disabled by default.  However, over the years, there have been difficulties with this. Read more

• The views expressed here do not necessarily represent the views of my employer or anyone else, no matter how badly I may want them to.

  Quantum Mechanics: The Dreams of Which Stuff is Made!

•  

  November 2009

  S	M	T	W	T	F	S
  « Oct
  1	2	3	4	5	6	7
  8	9	10	11	12	13	14
  15	16	17	18	19	20	21
  22	23	24	25	26	27	28
  29	30

• Tags

  Active Directory AEMS EWS Exchange LaTeX Mac PowerShell

• FireStats

  • Pages displayed : 7123
  • Unique visitors : 3809
  • Pages displayed in last 24 hours : 46
  • Unique visitors in last 24 hours : 26
   Powered by FireStats