Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 252
  • Last Modified:

Exchange 2007 Public Folders Rebuild Address List

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
steve352
Asked:
steve352
  • 3
1 Solution
 
EEhotlineCommented:
Hello,

Take a look at here, it will help you: http://exchangeserverpro.com/exchange-2010-fix-alias-script/
0
 
steve352Author Commented:
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
 
Simon Butler (Sembee)ConsultantCommented:
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
 
steve352Author Commented:
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
 
steve352Author Commented:
Took longer than expected to find this solution.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now