How to clear the Discovery Holds folder
To find whether this discovery holds folder is completely full, use the below-mentioned command. Step 1: Connect-ExchangeOnline and then, Step 2: Get-MailboxFolderStatistics -Identity user | select name,foldersize Note: This DiscoveryHolds folder is having a limit of 100 GB. If it is full, we will get issues like "Unable to clear deleted items folder", "deleted items are getting auto-restored" etc., One of the reasons for this folder is full: If Organization Hold is turned on(All Exchange mailboxes are selected in Compliance Retention Policy) or the Individual ID is selected on Compliance Retention Policy. Solution: Please try the below-mentioned steps to overcome this issue. Step 1: Exclude the DiscoveryHolds full ID in the Compliance Retention policy or run the below-mentioned commands in PowerShell. Connect-IPPSSession and then, Set-RetentionCompliancePolicy -Identity "Compliance Retention Policy Name" -AddExchangeLocationException user for multiple users, Set-RetentionCompliancePolicy -Identity "Compliance Retention Policy Name" -AddExchangeLocationException user1, user2, user3 Now on PowerShell, Connect-ExchangeOnline and then, Set-Mailbox -Identity user -RetainDeletedItemsFor 0 and then run the below-mentioned command two times. Start-Managedfolderassistant -Identity user Start-Managedfolderassistant -Identity user After 2-3 minutes, run the below-mentioned commands. Get-Mailbox "user" | FL DelayHoldApplied,DelayReleaseHoldApplied If the output is received as true for any above-mentioned holds, then run the below-mentioned commands. Set-Mailbox user -RemoveDelayHoldApplied Set-Mailbox user -RemoveDelayReleaseHoldApplied and then run the below-mentioned command two times. Start-Managedfolderassistant -Identity user Start-Managedfolderassistant -Identity user After 2-3 minutes, this DiscoveryHolds folder will become zero as per the below-mentioned screenshot. This process helped me a lot. If you have any doubts/concerns/suggestions about this post, please comment below. Best Regards, Venkat Kiran Kona.EOL - DDG - EQ operator wildcard bug fix
EOL > MSFT recently announced (i/t Health - Message center - MC912176) a bug fix related to the -eq operator and use of wildcards ('*') to compile the member list for Dynamic Distribution Groups. When the update takes effect, the * character will be treated as a literal value and not a wildcard. Therefore, expressions using the -eq operator will only evaluate to true if the right-hand side value matches the property values exactly. For example, the expression (WindowsLiveID -eq '*@microsoft.com') will only return true if the recipient’s WindowsLiveID property is exactly "*@microsoft.com". The current behavior will no longer function after the fix, and this may impact any processes that rely on this behavior. To distinguish the DLs (for corporate communication) membership of internal employees only and external consultants/contractors, we've created several DDGs using PowerShell to define the Recipient filter options based on our internal naming conventions (FTEs get FN.LN@emaildomain whereas consultants/contractors get FN.LN.ext@emaildomain). The formula was based on -eq operator combined with '*' wildcard > formula extract > -RecipientFilter {(( RecipientType -eq 'UserMailbox') -and ((WindowsLiveID -eq '*.*.ext@emaildomain') ... When the bug fix is corrected the formulas will no longer return the expected members. We've tried already several alternatives w/t -like operator but were not able to retrieve the same list. Other operators as -contains and -match are not supported i/t context of EOL. Are there other operators or other parameters to compile a filtered list using wildcards?
Collect count of emails sent to ALL Distribution Groups in ExOL
Hey Team, I am looking for PowerShell assistance, such as exporting a list of all distribution groups and measuring how many messages were sent to each DG in the past 10 days. Basically, how can I combine "Get-DistributionGroup -ResultSize Unlimited | Select-Object Name, DisplayName,GroupType,PrimarySmtpAddress | Export-csv c:\temp\DistributionGroupReport.csv -NoTypeInformation" and "Get-MessageTrace -StartDate (get-date).AddDays(-10) -EndDate (Get-Date) -RecipientAddress email address removed for privacy reasons | measure-object | Select Count" to a single csv, if possible. Thanks.Exchange SMTP Auth Fails with: 451 4.7.0 Temporary server error. Please try again later. PRX5
Office 365 refuses SMTP authentication with error: 451 4.7.0 Temporary server error. Please try again later. PRX5 This is when accessing External Send SMTP AUTH through OAUTH2 authentication. Initial authentication is successful (and is logged as so in Entra ID) but when trying to send send messages through authenticated SMTP, you get the above error. Working with multiple support reps, we looked through login logs and could not find any trace of the error in Entra ID. Support reps all blame the third party application. The issue is connected to a special use case, where a user has both the GLOBAL ADMIN role, as well as certain other admin roles. When you have a certain combination of those roles, for a selected user, OAUTH2 will fail, even though OAUTH2 for (apparently) ALL OTHER SERVICES - work without error! - ONLY SMTP Auth is affected. RESOLUTION: Keeping Global Admin while simply removing excess roles will almost immediately resolve the issue. This bug has been publicly noted as far back as August 2022, perhaps earlier. This needs to be fixed.
Random Exchange Server to 365 migration batch fails with the error "SourceMailboxAlreadyBeingMoved"
I'm running a migration for a small customer (about 400 mailboxes). half of the mailboxes are migrated just a couple of random mailboxes failed with this error. Has anyone faced/worked around this issue? I've tried following with no success: -Tried after a server restart -Tried creating a new batch ---- Error ---------------------------------------------------------------- Data migrated: 46.29 MB (48,542,751 bytes) Migration rate: Error: SourceMailboxAlreadyBeingMovedPermanentException: Couldn't switch the mailbox into Sync Source mode. This could be because of one of the following reasons: Another administrator is currently moving the mailbox. The mailbox is locked. The Microsoft Exchange Mailbox Replication service (MRS) doesn't have the correct permissions. Network errors are preventing MRS from cleanly closing its session with the Mailbox server. If this is the case, MRS may continue to encounter this error for up to 2 hours - this duration is controlled by the TCP KeepAlive settings on the Mailbox server. Wait for the mailbox to be released before attempting to move this mailbox again. --> -->SMTP Issue - Exchange 2019
Hi All, I have an hybrid exchange environment (365 + 2019), and the onprem server is used for smtp relay only. An internal app uses this relay and send email as "email address removed for privacy reasons", and all works well except by an specific message-subject. This application can send all the emails with any subject, but if the subject is "Purchace Order to be approved" the relay fails. Checking logs, I could see that when the message has this mentioned subject then the field "sender-address" is always empty (return-path is ok). And, of course, SPF/DKIM fails and message is quarantined. All other message subjects contain the address in "sender-address". This could be an issue with my application or something related to smtp config? Source for fields analyzing: https://learn.microsoft.com/pt-br/exchange/mail-flow/transport-logs/message-tracking?view=exchserver-2019 Thanks and happy new year to all of you.
Decomm a single EX16 after migration to MS365
We have moved all users off on-prem EX16 8 weeks ago. 3rd party did full migration to MS365, new external Azure AD, no hybrid mode. EX16 has been in maintenance mode for 3 weeks. Have dismounted databases. I am finding lots of conflicting details about decommissioning this server. It was a single server, no DAG, 50 users. Most instructions are for migration to on-prem higher versions with users still tied to local AD and EXCH. I just want to remove it from the environment and retire hardware. Not finding un-install details specific to this scenario. Anyone have some direction?
Automatic redirection of Exchange ActiveSync On-Pre
I am migrating mailboxes between on-premises Exchange forests using ADMT automated calls in SC Orchestrator 2019. Prepare-MoveRequest Migrate-ADMTUser MoveMailbox Set-Resources Has anyone already done the automatic redirection of Exchange ActiveSync in the following scenario: Moving mailboxes between on-premises Exchange organizations. I know the link below says it is not possible, but I would like to know if anyone has overcome this limitation? https://learn.microsoft.com/pt-br/exchange/activesync-settings
