When you mail enable an Exchange legacy public folder, a system object is created in Active Directory which is stored in the so-called MESO object container
The object created contains all required attributes for Exchange address lists and other Exchange attributes.
When you mail disable a public folder Exchange Server is supposed to delete the MESO object as well. For some reason that might not happen. In this case, the public folder will show in Public Folder Management Console as mail disabled, is still capable of receiving emails sent to its email address.
From an Exchange perspective, the email address can still be resolved, because a system object containing the email address still exists.
At first, it looked like a permission issue on the MESO object container, but it wasn’t.
A Microsoft KB article described the issue for a single forest, multi-domain environment, and a similar issue with Exchange Server 2010.
Configure the following registry on each Exchange Server hosting a public folder database and restart the MSExchangeIS service.
In addition, you should name the public folder and domain controller in the Exchange cmdlet
Enable-MailPublicFolder “\Public Folder Name” –Server PUBLICFOLDERSERVER –DomainController DC01
When you mail enable an existing public folder which looks like being mail disabled but still having an (old) MESO object, a new MESO object will be created. The situation will be as follows:
The result is not necessarily as expected, as the old MESO object is orphaned and never reconfigured again.
Orphaned objects need to be cleaned up manually and being recreated again, if necessary. In an Exchange environment that has been migrated from ancient versions to 2010, you might already have a lot of MESO objects having digits added to their common names.
You can clean up the MESO objects as follows:
This results in a correctly named and configured MESO object. You can use Bill Long’s PowerShell script to identify orphaned public folder objects in the MESO container.
This information is related to legacy Exchange public folders being hosted on Exchange Server 2007 and/or Exchange Server 2010.
The solution has been validated for Exchange Server 2007 as well, even though the KB article has been published for Exchange Server 2010 only.
This post had originally been posted at my former blog SF-Tools.
Do you need assistance with your Exchange Server setup? You have questions about your Exchange Server infrastructure and going hybrid? You are interested in what Exchange Server 2019 has to offer for your environment?
Contact me at thomas@mcsmemail.de Follow at https://twitter.com/stensitzki
Given Microsoft’s success in building Exchange Online running on its Office 365 cloud platform, it has undoubtedly learned a few valuable lessons that can be applied to on-premises deployments.
In this whitepaper, ENow board member and Microsoft Exchange MVP Tony Redmond reveals how standardization, automation and monitoring played into Microsoft’s success with scaling its platform.
Download the Whitepaper here: http://enowsoftware.com/whitepaper/Improve-Your-Exchange-Deployment-by-Learning-from-Massive-Scale.pdf
Are you unsure, if you should migrate to Office 365? You want to know more about security of cloud applications and services? Your Exchange Server infrastructure requires an upgrade? Contact me via email: thomas@mcsmemail.de
A new community PowerShell script to simplify Exchange Server mailbox migrations has been published to TechNet Gallery and Github.
See script help for examples.
Check out the professional services provided by Granikos for planning and migrating your existing Exchange Server infrastructure to the cloud.
PowerShell module providing centralizied logging and other helpful functions.
Import-Module GlobalFunctions $ScriptDir = Split-Path $script:MyInvocation.MyCommand.Path $ScriptName = $MyInvocation.MyCommand.Name # Create a new logger object, keeping the last 14 days of log files $logger = New-Logger -ScriptRoot $ScriptDir -ScriptName $ScriptName -LogFileRetention 14 # Write a new informational message to the log file $logger.Write('My Log Message') # Write an error message to the log file $logger.Write('My custom error message') # Write a warning message to the log file $logger.Write('My custom warning') # Send a log file by email at the end of your script $logger.SendLogFile('sender@mcsmemail.de', 'recipient@mcsmemail.de', 'smtpserver.mcsmemail.de')
You can "install" a PowerShell module by copying the module to a sub folder of the same name as the module in either of the two following locations:
PS C:\> $env:PSModulePath C:\Users\admin\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\sys tem32\WindowsPowerShell\v1.0\Modules
Create a new folder named GlobalFunctions in C:\Program Files\WindowsPowerShell\Modules
Copy the GlobalFunctions.psm1 file to C:\Program Files\WindowsPowerShell\Modules\GlobalFunctions
That's it.
These steps assume that you use a dedicated PowerShell scripts folder, e.g. D:\MyScripts
.\Set-PersistentPSModulePath.ps1 -Add
Close the current PowerShell window and open a new PowerShell window. That's it.
When using PowerShell 5, you can simply use the following PowerShell command from within an administrative PowerShell window.
Install-Module GlobalFunctions
When a new version of the GlobalFunctions module has been released, use the following PowerShell command to update the module.
Update-Module GlobalFunctions