Deleted delegate still exists in AD, generates NDR when sending meeting request

Posted on 2009-04-18
Medium Priority
Last Modified: 2015-01-05
Our MD had a secretary we'll call userX, userX was set up as a delegate on the MD's Outlook client so she would also receive meeting requests sent to the MD.

userX left the company a while back so her account was deleted from Active Directory.

Now when anybody sends the MD a meeting request they get a non delivery report saying userX could not be found in the organization.

I've checked the MD's delegate tab on Outlook and all tabs of the MD's AD Account but can see no reference to userX.

I'm thinking when userX was deleted the attribute where she was set up as a delegate is still in place.

How can I remove her from AD completely?  We're using Small Business server 2003

Any help much appreciated.
Question by:kestrel05

Expert Comment

ID: 24175392
1) Check MD's calendar properties and see if userX is not added there with any permission. If so, remove UserX.

LVL 15

Expert Comment

ID: 24175409
have you tried running the cleanup agent so the server will go thru and clean out old mailboxes that have been marked for deletion but have not been removed yet?

Exchange System Manager > Administrative Groups > %your system name% > Servers > %servername% > First Storage Group > Mailbox Store

then right click Mailboxes and run Cleanup Agent

Author Comment

ID: 24175507
Tried both of these options, none of them work unfortunately.  Any other ideas?
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.


Expert Comment

ID: 24175524
1. Close Outlook
2. Create a Outlook profile in online mode for the affected user.
3. Run MFCMAPI and click OK on the first Windows.  download link for MFCMAPI - http://www.microsoft.com/downloads/details.aspx?FamilyID=55FDFFD7-1878-4637-9808-1E21ABB3AE37&displaylang=en

4. Go to Session->Logon and Display Store Table.
5. Select the users profile
6. Double on the Mailbox.
7. Expand the 'Root Container' item.
8. Double-click "FREEBUSY DATA"
9. On the right you will see two items, one named 'sniffer' and the other named
10. Select 'LocalFreeBusy' and in the lower pane double click on a property
named 0x6844101E and you will see all Delegates user names in the Property Editor
11. Identify the entry/entries for orphan Delegate/delegates , Delete them and
click Ok.
12. Close the 'FREEBUSY DATA' window.
13. Expand "Root Container"
14. Expand "Top of Information Store"
15. Right click on Inbox and select "Display Rules Table"
16. Under "PR_Rule_Provider" column, delete the entry with display name
"Schedule+EMS Interface"
17. Close MFCMAPI.
18. Check for the problem.

Expert Comment

ID: 24175544
Additionally you may refer - http://support.microsoft.com/kb/909638

Author Comment

ID: 24175729
When I get as far as:

11. Identify the entry/entries for orphan Delegate/delegates , Delete them and
click Ok.

The orphan entry does not show up.

Any thoughts?
LVL 40

Accepted Solution

coolsport00 earned 750 total points
ID: 24176094
"kestrel"...I've assisted with 2 or 3 of these over the past year (and even had 1 myself) and have yet to have it be anything other than an Outlook Delegate issue. That 'user', though deleted in AD is in someone's Outlook Delegate tab somewhere. (see my EE post: http://www.experts-exchange.com/Software/Office_Productivity/Groupware/Outlook/Q_23531517.html). Do some more browsing in Outlook and let me know your findings.


Author Closing Comment

ID: 31571788
You're right - Thanks

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

569 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question