Just can't get enough of IT

Description

This script removes the proxy address(es) for a selected protocol from mail-enabled public folders.

Any proxy address with a given protocol is removed from the proxy addresses list.

The script can fix the alias of mail-enabled public folders as well. The code used is based upon a blog post by Shay Levy.

Examples

# EXAMPLE 1
# Check mail enabled public folders for proxy addresses having "MS:" as a protocol type.
# Do not remove and update addresses, but log found addresses to RemovedAddresses.txt

.\Clean-MailEnabledPublicFolders.ps1 -ProtocolToRemove "MS:*" 

# EXAMPLE 2
# Check mail enabled public folders for proxy addresses having "MS:" as a protocol type.
# Remove and update addresses and log found addresses to RemovedAddresses.txt

.\Clean-MailEnabledPublicFolders.ps1 -ProtocolToRemove "MS:*" -UpdateAddresses

Version History

• 1.0, Initial community release
• 1.1, FixAlias added, cleanup logic changed
• 1.2, Some minor PowerShell updates

Links

• Download and follow at Github: https://github.com/Apoc70/Clean-MailEnabledPublicFolders
• Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Script-to-remove-unwanted-9d119c6b

Follow

• Twitter @stensitzki
• LinkedIn
• Xing

Additional Note

This Powershell script has been optimized using the ISESteroids™ add-on. Learn more about ISESteroids™ here.

Description

This script removes/disables HealthMailboxes that show an inconsistent error when querying monitoring mailboxes using

Get-Mailbox -Monitoring

and receiving a warning like

"WARNING: The object DOMAINNAME/Microsoft Exchange System Objects/Monitoring Mailboxes/Health_Mailbox_GUID has been corrupted,

Examples

# Remove the HealthMailbox(es) having an empty database attribute

.\Fix-HealthMailboxes.ps1 -Remove   

Version History

• 1.0, Initial community release
• 1.1, Some PowerShell hygiene

Links

• Download and follow at Github: https://github.com/Apoc70/Fix-HealthMailboxes
• Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Find-and-remove-corrupt-42c8bfc2

Follow

• Twitter @stensitzki
• LinkedIn
• Xing

Problem

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.

Solution

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
  • mail=PublicFolderName@mcsmemail.de
• New MESO object attributes
  • displayName=Public Folder Name
  • CN=Public Folder Name 38513598
  • mail=PublicFolderName2@mcsmemail.de

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.

Note

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.

Links

• KB2647396: A public folder still appears in Exchange address lists after you mail-disable the folder in an Exchange Server 2010 environment
• Bill Long: Cleaning up Microsoft Exchange System Objects - part 2

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

Description

This script searches for OOF rules created by users using the Outlook rule-tab in the OOF assistant and deletes exisiting OOF rules.

In preparation to configure compliant Out-Of-Office (OFF) settings for users, any existing OOF rule needs to be deleted. The script will use either an exisiting Exchange Server EWS library or the Managed EWS library installed using the default file path.

This is the first of two scripts for the complete solution. Find the second script here.

The script access the mailbox rules using Exchange Web Services. Therefore the account executing the script either needs to have ApplicationImpersonation rights or full access to the user mailbox.

Requirements

• Exchange Management Shell (EMS) 2013+
• GlobalFunctions library as described here: http://scripts.granikos.eu
• Locally installed Exchange Web Services (EWS) Library, https://www.microsoft.com/en-us/download/details.aspx?id=42951

Examples

# EXAMPLE 1
# Find any existing OOF rule and write results to log file
Remove-OOFRule 

# EXAMPLE 2
# Find and delete any existing OOF rules in all user mailboxes and write delete actions to log file
Remove-OOFRule -Delete

# EXAMPLE 3
# Find and delete any existing OOF rules for user SomeUser@varunagroup.de and write delete actions to log file
Remove-OOFRule -Mailbox SomeUser@varunagroup.de -Delete

Version History

• 1.0, Initial community release

Links

• Download and follow at Github: https://github.com/Apoc70/Manage-OOF-Settings
• Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Remove-Out-Of-Office-rules-3f740964

Additional Credits

Rhoderick Milne (https://blogs.technet.microsoft.com/rmilne)

Follow

• Twitter @stensitzki
• LinkedIn
• Xing

When you move mailboxes using migration batches you might encounter a situation that your batch contains migration users that fail during batch execution. One of the possible reasons is an existing move request for the affected users. You must remove those requests to successfully move mailboxes.

The following PowerShell example gets all failed migration users from a migration batch and removes existing move requests. 

$r = Get-MigrationUser -BatchId MyMigrationBatch | ?{$_.status -eq 'Failed'}
$r | %{Remove-MoveRequest -Identity $_.MailboxIdentifier -Confirm:$false}

Enjoy Exchange Server!

Description

This script reads the Exchange schema version from the Active Directory schema partition.

The Exchange organization name is fetched from Active Directory automatically.
  
The script fetches at forest level:

• objectVersion of MESO Container
• rangeUpper of ms-Exch-Schema-Version-Pt 
• msExchProductId of Exchange Organization container
• objectVersion of Exchange Organization container

The script fetches at domain level:

• objectVersion of MESO Container

Examples

Code Samples

# Fetch all version information in the Active Directory forest
.\Get-ExchangeServerVersionInfo.ps1

Sample Output:

PS D:\Scripts> .\Get-ExchangeServerVersionInfo.ps1

Exchange Server Schema and Object Information for forest [VARUNA.ROOT]
Exchange Organization Name        : VARUNA-GROUP
Active Directory Schema rangeUpper: 15332

Working on VARUNA.ROOT
MESO Container objectVersion           : 13236
Exchange Configuration msExchProductId : 15.01.1466.003
Exchange Configuration objectVersion   : 16213

Working on VARUNAGROUP.DE
MESO Container objectVersion           : 13236

Version History

• 1.0, Initial community release

Links

• Download and follow at Github: https://github.com/Apoc70/Get-ExchangeServerVersionInfo
• Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Get-Exchange-Schema-73d3e629

Follow

• Twitter @stensitzki
• LinkedIn
• Xing

Enjoy Exchange Server!