Forum Widgets
Latest Discussions
Dynamic Distribution Group with no Disabled Accounts
Hi I'm trying to build a few Dynamic Distribution Lists in Exchange Online and want to only include Active Users (i.e., users that are marked "Active" in Azure AD). I've tried using the UserAccountControl attribute (-eq 514 or -ne 514 - both are returning the same results, which is strange), but it still includes user accounts that are disabled. This is how my recipient filter looks like: RecipientType -eq 'UserMailbox' -and UserAccountControl -ne 514 What's the best way to achieve this in Exchange Online? Thanks Taranjeet Singh1.9KViews0likes4CommentsTwo Exchange servers in one domain
Hello everybody, I want ask you, because I can’t find how “Exchange magic” works. I have two seperate Exchange DAG clusters in one domain, with different DNS records and different Virtual Directories URLs. Servers are on two physically diferent locations, but we create a direct connection between two locations for migration mailboxes in near future. We notice sometimes clients from old enviroment can connect through new enviroment and access to mailboxes on old servers. How is it possible? What communication ongoing between old and new Exchange enviroments? Can somebody explain me specifically? Thank you very much for answer to this mystery.sie65Feb 18, 2025Copper Contributor114Views0likes8CommentsAccess to Exchange Admin Centre blocked using most (but not all) URL links
Suddenly, when I try to use most of the published links to the Exchange Admin Centre, including the links on the Microsoft 365 Admin Centre, my access to the Admin Centre for Exchange is blocked. The messages vary but the most common one is "admin.exchange.microsoft.com closed the connection". All of the links for the other admin centres work just fine for me (Teams, InTune, SharePoint etc.) - it's just the Exchange Admin Centre link that are mostly problematic. Two examples of links that don't work for me: https://admin.exchange.microsoft.com/?landingpage=homepage&form=mac_sidebar https://admin.exchange.microsoft.com/#/homepage The only link I can find that still does work for me: https://admin.cloud.microsoft/exchange#/SolvedInaurukunFeb 17, 2025Brass Contributor322Views1like3CommentsHow to repair a corrupted Public Folder (on-prem)
Hello guys, Hope all is well. In our Exchange 2019 environment we use Public Folders extensively. Everything seems ok except one of folders that looks corrupted. I can execute commands Get-PublicFolder / Set-PublicFolder against it, I can get its items statistics (Get-PublicFolderItemStatistics) and have access to items through Outlook. But commands Get-PublicFolderStatistics, Get-PublicFolderClientPermission return the same error: The security principal specified is already on the permission set. + CategoryInfo : NotSpecified: (:) [Get-PublicFolderStatistics], CorruptDataException + FullyQualifiedErrorId : [Server=E7,RequestId=b2f89187-878f-4cab-b05f-fcdaa7d82c0d,TimeStamp=2/17/2025 3:19:42 PM] [FailureCategory=Cmdlet-CorruptDataException] B960021F,Microsoft.Exchange.Manag ement.MapiTasks.GetPublicFolderStatistics I tried to repair the corresponding public folder mailbox (New-MailboxRepairRequest) but none of my requests found errors. I moved the public folder content to a different public folder mailbox, no success. Any ideas how to fix the issue? My guess is that ACL list of the public folder is corrupted. Regards, Dmitry Horushindgk62Feb 17, 2025Copper Contributor10Views0likes0CommentsOutlook Android App error occurred during authentication. Please try again later.
Hi, I am migrating mailboxes between on-premises Exchange forests using ADMT automated calls in SC Orchestrator 2019. 1-Prepare-MoveRequest; 2-Migrate-ADMTUser; 3-MoveMailbox; 4-Set-Resources; Problem: Outlook mobile app using ActiveSync does not configure the same account after the mailbox is migrated from the source forest to the target forest with the email address in the "Username" field. Only using DOMAIN\Login or NETBIOS\SamAccountName. This happens with some accounts, but there are cases where it does not happen, even though the migration method is the same for all cases. Error message in the app: Outlook Android App error occurred during authentication. Please try again later. Workaround to configure post-migrated accounts: Email address: login@domain Password: User's forest password Server: FQDN of the NEW on-premises Exchange server Domain: Empty User Name: DOMAIN\SamAccountName PS: I can connect normally with 'Email - Fast & Secure Mail' and 'Gmail App ActiveSync'. This problem doesn't occur, and I can use the email address in the Username field." Troubleshooting performed: Enabled ActiveSync Logging: Set-CASMailbox -Identity "login@domain" -ActiveSyncDebugLogging:$true Get-Mailbox login@domain | Set-User -LinkedMasterAccount $Null Set-CASMailbox login@domain -ActiveSyncBlockedDeviceIDs $null Compared all attributes in Active Directory of an account with issues with another that does not have this problem; Compared all attributes in Exchange Server of an account with issues with another that does not have this problem; Both Exchange Server 2019 in the source and target forest with the latest CU14 and SUv2 from November. The Outlook Android App Support is very very complicated. It practically doesn't exist because no one ever responds.evandromalmsteenFeb 17, 2025Copper Contributor173Views1like3CommentsOn premise 2016 to exchange online
Hi all, i have a hosted exchange 2016 with 22 tenanats that I need to migrate. I don't want to install AAD connect or hybrid. Is there a way to do it manually by importing a CSV file? Or do a cutover with selective mailboxes?input04Feb 15, 2025Copper Contributor87Views0likes9CommentsProblem Search in mailboxes exchange 2019
Hi, i have problem with search in mailboxes. services search not working when users find email only result to day xxxx, after not work. I find only event after by date stop searching MSExchangeFasteSearch FAST endpoint exprienced an exception. exchange last updates, etc. Service ExchangeSearch and Exchangehost restart not work. Clients outlook 2019 and higher thanks for replydaweagleFeb 15, 2025Brass Contributor73Views0likes4CommentsUsing the Outlook Booking with Me Feature
Outlook’s new Booking with Me feature is rolling out worldwide. Any user with an Exchange Online license can create a personal bookings page to allow other internal and external people to book meetings with them. It’s a nice idea and a good example of how Microsoft can use its software toolkit to create new solutions. https://office365itpros.com/2022/07/25/booking-with-me/99KViews0likes5CommentsSlow performance when executing cmdlets through Powershell from a management server
We are trying to execute some management cmdlets to manage our distribution groups. We have a server having the Exchange Management Tools installed, not hosting any other Exchange Server roles. The command works well from an exchange server. When executing for example set-distributiongroup it takes some minutes to execute the command. It succeeds eventually . When running the command within a few minutes after the first try, it works fast. But when waiting for 5 or 6 minutes, it is slow again. I ran the command with the verbose option, below you will find the output. The bold part is taking so long. This part is skipped when executing the command for the second time within some minutes: Set-DistributionGroup <group-emailaddress> -AcceptMessagesOnlyFrom @{add=“<user-emailaddress>”} -verbose VERBOSE: [13:03:12.395 GMT] Set-DistributionGroup : Runspace context: Executing user: <executinguser>, Executing user organization: , Current organization: , RBAC-enabled: Disabled. VERBOSE: [13:03:12.399 GMT] Set-DistributionGroup : Active Directory session settings for 'Set-DistributionGroup' are: View Entire Forest: 'True', VERBOSE: [13:03:12.399 GMT] Set-DistributionGroup : Beginning processing Set-DistributionGroup VERBOSE: [13:03:12.406 GMT] Set-DistributionGroup : Instantiating handler with index 0 for cmdlet extension agent "Rus Agent". VERBOSE: [13:03:12.406 GMT] Set-DistributionGroup : Instantiating handler with index 1 for cmdlet extension agent "Admin Audit Log Agent". VERBOSE: [13:03:12.423 GMT] Set-DistributionGroup : Current ScopeSet is: { Recipient Read Scope:{{, }}, Recipient Write Scopes:{{, }}, Configuration Read Scope:{{, }}, Configuration Write Scope(s):{{, }, }, Exclusive Recipient Scope(s):{}, Exclusive Configuration Scope(s):{} } VERBOSE: [13:03:12.431 GMT] Set-DistributionGroup : Searching objects "<group-emailaddress>" of type "ADGroup" under the root "$null". VERBOSE: [13:03:12.437 GMT] Set-DistributionGroup : Previous operation run on global catalog server ‘<GCserver>’. VERBOSE: [13:03:12.437 GMT] Set-DistributionGroup : Rereading object “<groupadobject>” of type "ADGroup" under the root “<cngroupadobject>“. VERBOSE: [13:03:12.437 GMT] Set-DistributionGroup : Previous operation run on domain controller ‘<DC>’. VERBOSE: [13:03:12.437 GMT] Set-DistributionGroup : Searching objects “<useremailaddress>“ of type "ADRecipient" under the root "$null". VERBOSE: [13:03:12.453 GMT] Set-DistributionGroup : Previous operation run on global catalog server '<GCserver>'. VERBOSE: [13:03:12.453 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Update Recipient object “<recipientadobject>“ with ConfigurationDomainController "<null>", DomainController "<DC>”, GlobalCatalog "<null>". VERBOSE: [13:03:12.453 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Read Address List for organization "" from domain controller <DC>. VERBOSE: [13:03:12.462 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\". VERBOSE: [13:03:12.462 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\". VERBOSE: [13:03:12.462 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\Default Global Address List". VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\All Rooms". VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List “\xxxx”. VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List “\xxxx”. VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\All Contacts". VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\Public Folders". VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\All Distribution Lists". VERBOSE: [13:03:12.469 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\External". VERBOSE: [13:03:12.485 GMT] Set-DistributionGroup : [Microsoft Cmdlet Extension Agent] Found Address List "\All Users". VERBOSE: [13:03:12.485 GMT] Set-DistributionGroup : Processing object "<groupadobject>". VERBOSE: [13:03:12.485 GMT] Set-DistributionGroup : Admin Audit Log: Entered Handler:Validate. VERBOSE: [13:03:12.493 GMT] Set-DistributionGroup : Admin Audit Log: Entered ClassFactory:InitializeConfig. VERBOSE: [13:07:03.950 GMT] Set-DistributionGroup : Admin Audit Log: Exited ClassFactory:InitializeConfig. VERBOSE: [13:07:03.966 GMT] Set-DistributionGroup : Admin Audit Log: Exited Handler:Validate. VERBOSE: Setting distribution group "<group-emailaddress>". VERBOSE: [13:07:03.966 GMT] Set-DistributionGroup : Resolved current organization: . VERBOSE: [13:07:03.966 GMT] Set-DistributionGroup : PreInternalProcessRecord on cmdlet extension agent index '0' returned object changed flag as 'False'. VERBOSE: [13:07:03.966 GMT] Set-DistributionGroup : PreInternalProcessRecord on cmdlet extension agent index '1' returned object changed flag as 'False'. VERBOSE: [13:07:03.966 GMT] Set-DistributionGroup : No properties changed for the object "<groupadobject>". WARNING: The command completed successfully but no settings of '<groupadobject>' have been modified. VERBOSE: [13:07:03.966 GMT] Set-DistributionGroup : Saving object "<groupadobject>" of type "ADGroup" and state "Unchanged". VERBOSE: [13:07:03.982 GMT] Set-DistributionGroup : Previous operation run on domain controller '<DC>'. VERBOSE: [13:07:03.982 GMT] Set-DistributionGroup : Admin Audit Log: Entered Handler:OnComplete. VERBOSE: [13:07:03.982 GMT] Set-DistributionGroup : Admin Audit Log: Exited Handler:OnComplete. VERBOSE: [13:07:03.982 GMT] Set-DistributionGroup : Ending processing Set-DistributionGroup Some got an idea what could be causing this delay? Using the lastest Exchange 2019 versions with updates.kevinmoonenFeb 14, 2025Copper Contributor293Views0likes2CommentsRandom 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. --> -->257Views0likes2Comments
Resources
Tags
- exchange online2,436 Topics
- Exchange Server2,224 Topics
- office 3651,194 Topics
- hybrid831 Topics
- 2016728 Topics
- outlook722 Topics
- admin648 Topics
- 2013275 Topics
- 2010159 Topics
- 201973 Topics