Solved

Exchange 2007 Public Folders Rebuild Address List

Posted on 2014-02-05
5
243 Views
Last Modified: 2014-04-15
Running Get-PublicFolder on our Exchange server (2007) produced a bunch of errors related to invalid characters (spaces) in the aliases of a number of mail enabled PFs. A bunch of the PFs were Default PFs and should never have been mail enabled to begin with so I disabled them for mail from the EMC. Unfortunately, even though the PFs are no longer mail enabled it appears as if the aliases don't get deleted and Get-PublicFolder still produces errors about the same bad characters in the same PFs. What is the easiest way to clean out all those aliases? I'm thinking there must be some way to issue an EMS cmdlet that updates the PF address list and removes all the old aliases. Is that possible or should I just delete the entire PF address list, rebuild it with New-AddressList, then use EMC to apply it? Weird bit is that some of the these PFs that have bad aliases are System PFs that probably came over from Exchange 2003. Is it safe to mail disable these System PFs as well? More generally, are there any System PFs that must remain mail enabled?
0
Comment
Question by:steve352
  • 3
5 Comments
 
LVL 8

Expert Comment

by:EEhotline
ID: 39836656
Hello,

Take a look at here, it will help you: http://exchangeserverpro.com/exchange-2010-fix-alias-script/
0
 

Author Comment

by:steve352
ID: 39836737
Unfortunately it appears that the script appears to be used for mailboxes, contacts, and distribution groups and not for public folders. If I run Get-Mailbox -resultsize unlimited | findstr "Warning" I don't get any warnings because the aliases for all the mailboxes are good.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39838641
Do you have any Outlook 2003 clients? If not then you could probably look at eliminating public folders completely. Mail disabling system folders is a tricky thing to call as it can cause some problems.

If you have made the changes to the aliases then the change should replicate out on its own, rather than trying to do anything with the address book.

Simon.
0
 

Accepted Solution

by:
steve352 earned 0 total points
ID: 39992403
Turns out that the problem was caused by a bunch of leftover MESO's in AD which most likely where there as a result of a Exchange 2K3 -> 2K7 migration. Removal from AD sorted things out.
0
 

Author Closing Comment

by:steve352
ID: 40001104
Took longer than expected to find this solution.
0

Featured Post

Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
how to add IIS SMTP to handle application/Scanner relays into office 365.

707 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now