Hi,

We've recently migrated our Exchange 2007 users to a new 2013 infrastructure and everything seems to be working OK.

We noticed that the users that we've migrated are still accessing unwanted Public folders on the legacy system when they run outlook and we were wondering what steps we need to take to stop this from happening?

Is it just a matter of deleting the Public folders from the Legacy system or is there more to it than that?

We've disabled the Public Folder distribution of the OAB on the legacy system hoping that this might resolve the problem (even though the new databases are using the Exchange 2013 OAB).

Cheers for now

Russell

Not sure what at I'm supposed to be checking but the legacy systems are still up and running at the moment as we've only just migrated the last user to 2013?

There is no valid data in the Public Folders and I suspect that they were only used for OAB distribution in the past.

Cheers for now

Russell

Not sure what at I'm supposed to be checking but the legacy systems are still up and running at the moment as we've only just migrated the last user to 2013?

There is no valid data in the Public Folders and I suspect that they were only used for OAB distribution in the past.

Cheers for now

Russell

if you don;t want to migrate (or there truely is no data you care about) the public folders, then just remove them. 

Another thing you can do is Get-MailboxDatabase | fl name, PublicFolderDatabase

This should return the legacy public folder database.  Once you confirm that then you can do:

Get-MailboxDatabase | Set-MailboxDatabase -PublicfolderDatabase $null

And that remove the public folders from the Outlook the next time the user launches Outlook. 

Not sure what at I'm supposed to be checking but the legacy systems are still up and running at the moment as we've only just migrated the last user to 2013?

There is no valid data in the Public Folders and I suspect that they were only used for OAB distribution in the past.

Cheers for now

Russell

if you don;t want to migrate (or there truely is no data you care about) the public folders, then just remove them. 

Another thing you can do is Get-MailboxDatabase | fl name, PublicFolderDatabase

This should return the legacy public folder database.  Once you confirm that then you can do:

Get-MailboxDatabase | Set-MailboxDatabase -PublicfolderDatabase $null

And that remove the public folders from the Outlook the next time the user launches Outlook.

hmm.. the switch should still be valid, since Exchange 2010 and 2007 are supported migration paths, and can host public folder databases.  I've used it before, if you run the first get command again does it still show the legacy folders?

Yes, the original command does list the Public folders again.

I'll try manually removing the Public Folders from the legacy system out-of-hours and let you know if that removes them from the 2013 databases.

Cheers for now

Russell

Yes, the original command does list the Public folders again.

I'll try manually removing the Public Folders from the legacy system out-of-hours and let you know if that removes them from the 2013 databases.

Cheers for now

Russell

Hi Russell,

If the Public Folder in Exchange 2007 is not useful and would not be moved to Exchange 2013, please remove them. Then do the following steps to have a try:

1. Open ADSIEdit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.

2. Right-click the listed database > Properties.

3. Check whether the msExchHomePublicMDB value is set to the legacy public folder database. Please clear the value to <not set>.

4. Click OK.

Then check whether the issue persists.

Regards,