Exchange SE HTTP 500 error
Hi Everyone, Been having this weird thing with 2 new Exchange SE installs. Both of them when trying to sign into ECP get a HTTP500 error once I've entered credentials Not really sure where to go, looked in IIS, checked the bindings, checked event viewer, services I expect to be behind this look to be running. Anyone else come across or have any solves? Thank you
Exchange Migration Cross forest
Hello, I planning to do an exchange Migration from forest A to forest B and the email address will be changed. I don't want to set any trust between the two, i will simply create the active directory users from scratch with new passwords and will install and configure the exchange environment in the target forest and will create the mailboxes. i will use a third-party tool to migrate the mailboxes between the two forests and after cutover i will add the alias of the old email as additional proxy address to the mailboxes. i am assuming everything will work fine however i have seen lot of articles on the internet about we have to migrate the legacyexchangeDN from the source environment and to add it as X500 proxy address as well in the destination or we might face issues in the migrated recurrent meetings when someone wants to edit or when someone reply to a migrated email.... I can afford having some meeting corrupted after migration but i cant afford the headache of NDR when someone reply to the migrated emails it will be a disaster.... anyone had this experience before to share it with me especially regarding the reply to the migrated emails and i did not lot of documentation from Microsoft about such scenario? Thank You.
Exchange 2019 Mailbox Migration Error - Folder conflicts with Exchange Online folder
Hi Exchange Experts, I'm migrating a small Exchange 2019 environment to 365. Been pulling my hair out becuase of just one mailbox giving this error Error description --------------------------- Error: AggregateMailboxFolderConflictPermanentException: The folder 'Files' conflicts with Exchange Online folder 'Files', please move the messages to another folder and restart the job. Data migrated: 0 B (0 bytes) Migration rate: -------------------------------------- Migration user report: 5/14/2025 12:32:05 PM [MEUP300MB0105] Request processing continued, stage CreatingFolderHierarchy. 5/14/2025 12:32:05 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Fatal error AggregateMailboxFolderConflictPermanentException has occurred. ---------------------- It seems to be a system folder and I've tried to remove files from it (although there're no files in it) using MFCMAPI tool with no success. Renamed the folder and tried to re-run the migration with no luck. Has anyone experience this issue? any thoughts or tips are much appreciated ! Thank you.
Missing Teams Contacts after Migration
Hello, We are currently migrating mailboxes from exchange 2019 to exchange online. The migration works absolute flawless. Now we have some employees complaining about missing teams contacts that were previously created in Teams only. The MS support told me that this is a teams limitation and the local contacts are gone. I know about unified contacts, thats contacts are synced now between outlook and teams and newly created contacts are stored in exchange online mailbox. But whatabout the old contacts ?? cant believe that theres no workaround to keep this contacts. Do you know something about this ? Rene
I am receiving DMARC errors
Hello Please i need your help on this issue. Last night I started receiving DMARC and other errors when trying to send emails. I dont believe my business email is receiving messages either. Please help me 'fix' resolve these bounce back errors. I did try to find the solution on my own,, but its just out of my wheelhouse. Please help as my business is being affected by these errors and bounce backs.Exchange 2016 to SE and Exchange Online questions
Hi, We're currently in the process of migrating from Exchange 2016 to Exchange Subscription Edition (SE), along with moving a portion of our mailboxes to Exchange Online. We have approximately 3,000 mailboxes, and around 2,000 of those will eventually end up in Exchange Online—for various reasons (don’t ask why…). I have a few questions I'd like to clarify and hope you can assist: Exchange On-Premises Questions: If a user mailbox is moved to Exchange SE, can they still access shared or user mailboxes that remain on Exchange 2016? Do we need to migrate them in the same batch to preserve access/permissions? (should't be an issue in the same Exchange Org right?) If a shared mailbox is migrated to Exchange SE while the user mailbox remains on Exchange 2016, will access still work? Do we need to point the Hardware Load Balancer (HLB) to the new Exchange SE servers before mailbox moves to allow proper client connectivity and proxying back to Exchange 2016? Or is it okay to keep the HLB pointed to the Exchange 2016 servers until all migrations are complete and then switch it over? Proxy upwards from Exchange 2016 to Exchange SE? What’s the best practice here? Pros/cons? Exchange Online Questions: If we want all outbound mail to go through the on-prem Exchange environment—even for Exchange Online mailboxes—is this configured via the Hybrid Configuration Wizard (HCW)? Is the Litigation Hold status preserved when migrating a mailbox to Exchange Online? Can a mailbox hosted in Exchange Online access a shared mailbox still residing on-prem? (Should't be an issue right?) Can an on-prem mailbox access a shared mailbox that has been migrated to Exchange Online? For mailboxes with Full Access or Send As permissions (e.g. user mailboxes tied to shared mailboxes), do they need to be migrated together in the same batch to retain functionality? We’ll be using native Microsoft migration tools (no 3rd-party solutions). If I recall correctly, separate migrations will still allow Full Access?!?, but Send As may not work properly unless migrated together. Is that still accurate?
Exchange Server SE Hybrid License and Upgrades
Hi, I have a question about Exchange Server SE. Reading the FAQ I found this: As with previous versions, Exchange Server SE will continue to provide free licenses for qualified hybrid use via the Hybrid Configuration Wizard (HCW); however, unlike previous versions, you will need to either purchase SA for this license to get Exchange Server updates or have a cloud subscription license that satisfies the requirements. Does this mean I need to have SA to do the updates? Which cloud licenses do I need to buy to be able to update Exchange Server SE? Thanks Regards
Multiple objects with Sid S-1-5-10 were found.
When I tried to set exchange on-premise user mailbox permission, I'm getting the below error. I have used the below script. What we missed ? This works for some objects. $sid = "S-1-5-10"; Add-MailboxPermission -Identity "TestExchange213" -User $sid -AccessRights FullAccess -confirm:$false;
Problems after upgrade to CU14
Hi, I'm in the process of migrating from Exchange 2013 CU23 to Exchange 2019. I installed Exchange 2019 CU13 on Win2022 Server, in coexistence with our 2013 and everything was looking good. Before starting with the testing to route emails through 2019, I checked that CU14 was released recently, so I download/install the CU14 in upgrade mode (with the no EP flag) to have the last build, and now I'm having problems with virtual directories, mailboxes, and so ON. Already run the healtchecker powershell scripts and nothing out of the ordinary. Some of the problems I'm having: 1. When I clic on the 'authentication' tab in any Virtual Directory (ECP, OWA, EWS) I got this error: "The task wasn't able to connect to IIS on the server <FQDN>. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable." The other tabs don't throw me any errors, but almost all options are greyed-out. 2. In SERVERS > DATABASES, when entering the properties of any Database that are on the new EX2019, I got this error: 'Exchange can't connect to the Information Store service on server <FQDN>. Make sure that the service is running and that there is network connectivity to the server.' I cannot create a new Database neither and the status of the currents 2019 Mailbox databases says Uknown and BadCopyCount = 1. 3. SERVERS > CERTIFICATES: Cannot see any Cert here for the EX2019. The error I get: "Cannot connect to the remote procedure call service on the server named <servername>. Verify that a valid computer name was used and the Microsoft Exchange Service Host service is started." Already check: - Binding of the Certificate 'Microsoft Exchange 'on the BackEnd and our Public Certificate on the Frontend Server. - All Exchange Services are up and running. - Restart of IIS. It appears that is something with permissions and/or with IIS that breakdown after the installation, but still don't know what it is. Al things related to the 2013 environment appears to be normal and functioning. according. Something I noticed, on the Certificate error it says the name of the server, and in the other errors, it says the FQDN of the server. Please guide me here, what could be the problem and what to check/confirm. Thanks in advance.
