I came across and issue where we needed to have an auto response sent every time users sent an email to a specific distribution list. In our case since the distribution list already existed a shared mailbox was created. This shared mailbox was then added to the DL. From there a rule was created where the shared mailbox would send an auto reply.
Only problem, when an email was sent to the DL the sender would not receive an auto reply. Emailing the shared mailbox directly did produce the desired result which verified that the rule which was created did in fact work.
Turns out by default distribution lists do not pass auto responses – in order to configure this you need to enable the following parameter: SendOofMessageToOriginatorEnabled
By default this parameter is set to false – once set to true auto responses were received when emailing the distribution list.
Example: Set-DistributionGroup -Identity <identity info> -Name <Group Name> -SendOofMessageToOriginatorEnabled $true
At a client site yesterday, the help desk were provisioning new users with phone extension and for one they came across the error below.
The user was already assigned this extension in Lync and AD had the correct information. Normally when an extension is in use they would not have been able to add the extension in link.
In order to resolve this issue – I ran the Get-UMMailbox command. I piped the output to a text file and found that the extension above was still in use on a disabled user. Once removed we were able to assign the extension to the new user.
Recently had an issue where a user who was a carried over from Exchange Server 2003 way back when had multiple corrupt items. When he was originally migrated to Exchange Server 2010 there were a number of items which so how got corrupt. This inhibited his search abilities. With the New-MailboxRepairRequest command in Exchange 2016 I was able to resolve this issue.
I ran the repair against all options:
Once complete we recreated the user’s .OST file since he works in cached mode.
You can find more info on this at Technet:
If you are sending emails to a Journaling connector and do not wish to journal voicemail messages for legal or business purposes you can disable this feature with the following command.
Set-TransportConfig -VoicemailJournalingEnabled $false
A client recently asked to have a retention for mail items but to leave calendar and tasks untouched. When in the ECP the option to create a specific retention tag for calendar items or tasks is missing. You must do this through Powershell.
Below is the command I used for both Calendar items and Tasks
New-RetentionPolicyTag “Name of Retention Policy Tag” -Type Calendar -RetentionEnabled $false -RetentionAction DeleteAllowRecovery
Do the same for Tasks replacing Calendar for Tasks in the Type field. Once run you can then add these Retention Policy Tags to your Retention Policy.
I have noticed on occasion that after suspending a database copy for a prolonged period of time the ContentIndex State may be stuck in a Suspended state.
You can resolve this situation by reseeding the ContentIndex only from the Active copy.
Update-MailboxDatabaseCopy “DatabaseName\ExchangeServer” -CatalogOnly
The other day while updating Exchange 2016 to the latest CU, I ran across the following error message:
An Active Manager operation failed. Error: The database action failed. Error: Move for database ‘DatabaseName’ was suppressed because too many moves have happened recently. 3 moves have happened within 01:00:00
Before updating, I had applied the latest security patches plus needed to update .NET Framework so I was moving datastores back and forth.
To get around this error you can use the SkipMoveSuppressionChecks parameter.
Move-ActiveMailboxDatabase -Identity ‘DatabaseName’ -ActivateOnServer ‘ExchangeServer’ -SkipMoveSuppressionChecks