exchange server
2601 TopicsExchange 2010 to Microsoft 365 Migration – Recommended Approach and Tools
I’m looking for guidance on migrating Exchange 2010 (on-premises) to Microsoft 365 / Office 365. Is a direct migration from Exchange 2010 supported, or is an intermediate hop (such as upgrading Exchange or setting up a hybrid configuration) required? Additionally, could you please recommend any reliable tools that can help with this migration? I also have a few PST files that need to be migrated as part of the process. I’d appreciate insights on best practices, common challenges, and lessons learned from real-world migrations. Thanks in advance for your help.119Views0likes3CommentsTeams delegation permission issue with Onpremise Exchange Server
we have migrated the exchange server from 2019 to SE Environment and configure the OAuth 2.0 which is working perfectly but there is one issue that one of the user is using Shared calendar but while he create the meeting invite along with Teams meeting option then everytime it shows an error "please login into the meeting" If anyone works on this case please guide or help us. Thanks78Views0likes2CommentsDMARC rejection after Exchange upgrade
I'm having problems with inbound emails getting bounced as Undeliverable due to DMARC rejection. For many years I've had my email come through Fasthosts / Livemail to my own domain (qts.org.uk) with catch-all forwarding set to forward everything to my GMail account. Just recently Fasthosts have upgraded their servers to Exchange and I've started getting DMARC rejections from GMail which start Diagnostic information for administrators: Generating server: exchange2019.livemail.co.uk Total retry attempts: 1 (my gmail email address) t1-hex-xprelay.gem.livemail.co.uk Remote Server returned '550 5.7.26 Message rejected by DMARC policy by gmail.com. Please use your own email address as the sender, instead of (sender's email address). [MSG0009]' Which bounce from Fasthosts / Livemail back to my GMail address. My own domain has SPF, DMARC, and DKIM configured I've done a little digging and it appears to only affect senders from originating domains with DMARC set to reject. So either GMail has coincidentally become much more strict (possible) or Fasthosts are somehow failing to forward emails fully transparently. I have spoken to Fasthosts and logged the issue with them and was not impressed so I hope the experts here can offer a solution I can forward to them.131Views0likes1CommentExchange 2019 Certificate Error
Hello guys, I plan to migrate my users on Exchange 2019, currently, i have 2 Exchange 2013 servers. As soon as i installed the exchange Server 2019, I changed all the virtual directories and i also runned the command to make sure the users doesn't connect on the new server. But now every users who uses Microsoft Outlook from the environment have a pop up that says that the certificate is not valid, and its normal because I can't apply the services SMTP and IIS on my wildcard certificate. Indeed, when i enable the services SMTP and IIS on my new certificate, it doesn't apply. I tried to enable from the ECP, it says "Are you sure you want to replace the existing certificate", when i say yes, it doesn't change anything, the smtp service is still unchecked. I also tried to stop IIS and restart IIS, restart the server but it doesn't changed anything, and I also tried to enable the services directly with the powershell command with the correct thumbprint of the wildcard certificate as it is said on the event viewer : "Enable-ExchangeCertificate -Server "EX01-2019" -Thumbprint A6BC992FDD... -Services SMTP,IMAP,IIS -Force" But it still don't work, when i check the certificate, only the service IIS is active. I had to uninstall completely the exchange server, because users were complaining about the pop up. Have anyone faced this problem before? Thank you very much for your advices guys105Views0likes3CommentsKeep user account but provision new empty mailbox
i did ask in another forum but thought i would ask here as it seems impossible... we are hybrid exchange. We have litigation hold and purview retention policies in place. We have a scenario where an existing user is moving to a new role and her existing mailbox needs to be dissociated from her AD account and a new clean mailbox provisioned. The original mailbox needs to stay as inactive and searchable via ediscovery. Is it possible? I have asked AI and its said: Make sure all the holds and retention policies are in place Move the AD account to a non-syncing OU and run a delta sync The mailbox should show as inactive in exchange online Then it tells me to run Set-User <UserUPN> -PermanentlyClearPreviousMailboxInfo but ONLY if the recipient type shows as MailUser or User This is where i am stuck as it is still UserMailbox. It told me to restore the cloud only object which i did. But it still shows as RecipientType = UserMailbox when i check. Its now just a cloud only account, it has no license. The mailbox is inactive but its still a UserMailbox Is what i am trying to do possible? Would now just changing the cloud only account to have a new email address be the only way to retain it and then sync back the on-prem account?105Views0likes2CommentsOWA “Manage Add-ins” Stuck Loading After Clicking Settings (Exchange 2019 CU15 / Exchange SE RTM)
I have an Exchange Server environment with three versions: Exchange Server 2019 CU14 Dec25SU, Exchange Server 2019 CU15 Sept25H, Exchange Server SE RTM, and Exchange Server SE RTM Dec25SU. Issue: When users click the Settings icon/button in OWA/Outlook on the web and then click Manage add-ins, the page does not redirect and remains stuck on an external loading screen. Tested environments: Exchange Server 2019 CU14 Dec25SU: Works without issues Exchange Server 2019 CU15 Sept25H, Exchange Server SE RTM, and Exchange Server SE RTM Dec25SU: Does not work on any of them Troubleshooting performed: Moved all arbitral mailboxes to a database on Exchange Server SE RTM Dec25SU (the most recent version in the forest). (No success) Migrated all servers to Exchange Server SE RTM Dec25SU. (No success) Isolated testing using the hosts file (DNS) pointing to each host individually, and all hosts have the issue. All SE RTM Dec25SU servers were installed in admin mode via Command Prompt. I also ran the two .ps1 scripts below on a test host after installing the SU: #learn.microsoft.com/en-us/troubleshoot/exchange/client-connectivity/owa-stops-working-after-update cd "C:\Program Files\Microsoft\Exchange Server\V15\Bin" .\UpdateCas.ps1 .\UpdateConfigFiles.ps1 iisreset /restart Workaround: With the user already authenticated, if I manually open the URL below in the same authenticated session, it loads normally: webapp.mydomain.com/owa/#path=/options/manageapps Does anyone know how to fix this, or if this is a bug that started with CU15 (or a later SU)?209Views0likes4CommentsUpgrading to Exchange SE
Hi, I currently have Exchange 2019 and need to upgrade to SE. When attempting an upgrade the process didn't appear as expected. Articles I've read basically said the process should be the same as a regular CU upgrade. When I run setup from the ExchangeServerSE-x64 iso, I get an Add Server Role window, instead of the expected upgrade method. The window presents 3 Roles, 2 are ticked, and they're all greyed out. The Next button has no function. I have Standard Edition 15.2 2562.17 (CU15). When checking my build number online, it is listed as the SE version, released July 1st, 2025. When I run Get-ExchangeServer, the Edition = Standard. Should it not say Subscription, or maybe SE? How do I verify my installation is actually SE? ThanksSolved358Views2likes4CommentsTeams calendar for exchange on prem users not working
Hello I am having issues to make Exchange On prem users use Calendar on teams. Initially Client autodiscover was blocked externally but they added a cname and open flows but I am still having issues to makecalendar on teams work HCW as passed and new hybrid dedicated app was used any help is welcome255Views0likes2CommentsMicrosoft Exchange refers to an older certificate that no longer exists, ID 12023.
We have one Microsoft Exchange 2013 server. The Windows Application log periodically displays the ID 12023 entry, which states that Microsoft Exchange could not load the certificate with the thumbprint 3E8XXXXXXXXXXXXXXXXXXXXXXXXXXXX from the local computer's personal certificate store. This certificate was deleted because it expired, and a new self-signed Auth certificate was created. Now, when running the Get-AuthConfig | Format-List CurrentCertificateThumbprint, PreviousCertificateThumbprint, NextCertificateThumbprint command, only the current certificate is displayed. The Microsoft Exchange 2013 server is running. The question is, what should I do to remove the ID 12023 entry from the Windows Application log?260Views0likes4Comments