MVP - Most Valuable Professional

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft technologies like Exchange Server, Microsoft 365, Microsoft Teams, and Cloud Security.

The community script Copy-ReceiveConnector has been updated. Receive Connectors that do exist on a specified target server can now be updated.

Besides the receive connector communication the assigned permissions of the source connector can be copied as well.



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:

Read More »


When you use Symantec NetBackup 7.x you might encounter Error 5, when you try to restore an Exchange Server 2013 DAG mailbox database backup to a Recovery database or to the original datrabase.

The error message in Backup, Archive, and Restore Tool looks similar to this

Screenshot NetBackup Error 5

Enabling NetBackup debug logging by using the mklogdir.bat file located in C:\Program Files\Veritas\NetBackup\logs does not necessarily provide additional input. The restore job fails before entering the job section for local restore activities. So no TAR log is being created.



When following the NetBackup Admin Guide and several Symantec HowTo’s you have already configured the following two services to run using a dedicated Service Account

  • NetBackup Client Service
  • NetBackup Legacy Client Service

Screenshot NetBackup Legacy Network Service running with LocalSystem

There are some circumstances (not clearly defined by Symantec) when an additional NetBackup Service performs Exchange PowerShell commands as part of a restore process. Therefore the following NetBackup service must be configured to run using the same Service Account as the other two NetBackup services.

  • NetBackup Legacy Network Service

Screenshot NetBackup Legacy Network Service running with Service Account

In addition be aware that the Service Account required Debug permission on the Exchange Server. It might be helpful to propagate the permissions for the Service Account using a GPO.

  • Computer Configuration\Windows Settings\Security Settings\LocalPolicies
    • User Rights Assignment
      • Debug programs
      • Log on as a service
    • Restricted Groups
      • Administrators


Read More »


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

  • CN=Microsoft Exchange System Objects, DC=MCSMEMAIL, DC=DE

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.

  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MsExchangeIS\ParametersSystem
  • DWORD (32 bit)
  • EnableDeletePFProxyAndStorePropTogether
  • Value = 1

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:

  • Old MESO object attributes
    • displayName=Public Folder Name
    • CN=Public Folder Name
  • New MESO object attributes
    • displayName=Public Folder Name
    • CN=Public Folder Name 38513598

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:

  1. Delete orphaned object in MESO container
  2. Mail enable public folder

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
Follow at



Read More »

Graphic Whitepaper: Improve Your Exchange Deployment by Learning from a Massive ScaleGiven 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:






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:

Read More »

A new community PowerShell script to simplify Exchange Server mailbox migrations has been published to TechNet Gallery and Github.



  • Validate CSV file for required column EmailAddress prior to creating migration batch in Exchange
  • Automatic batch naming based on CSV file name
  • Common notification email address settings
  • Variable AutoComplete of batches
  • Common logging of script activities

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.

Read More »