Hi,I recently have come across a Exchange 2003 SP2 mixed mode server where the local admin team had been complaining that for the last 6 months every so often they would get a warning from their Exchange monitor regarding queues.Whilst I was there it happened again, and a quick dart onto the queue viewer showed an email sat in the local delivery queue. I extracted the to address and searched AD for it, anyways it turns out to be attached to an AD Public Folder object in the Microsoft Exchange System Objects container. The local admins recognized the name but thought that the public folder to which it belonged did not actually exist anymore, hence the jam...Anyways I ran a search on AD and Exchange using PFDAVAdmin and now have a list of 8 objects which appear to be mail enabled public folder objects in Active Directory in the above container, but do not have corresponding actual Exchange folders. How does this happen, (Reason I ask is because I created a test folder which created a PF object in AD, then deleted it via ESM and it removed the AD object automatically). And how can I safely sort this out, because if I go to remove the email address from the object in AD it says I should be managing the object using ESM, but of course it is not there!

You should be able to remove them using adsieditVinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

So, these public folders can’t see via ESM or PFDavAdmin, right? The problematic public folders may not be deleted completed, so left the objects in the ADUC But since their folders don’t exist anymore, please update the GAL so others won’t mail to these addresses again. You can remove the object as Vinod said from Adsi or ADUC Also, please run a integrity check for the public store (KB 182081)James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com