Forum Widgets
Latest Discussions
PublicFolder CN=Schema,CN=Microsoft Exchange System Objects,DC=contoso,DC=com
I'm in the preparation stage of migrating our Public Folders from an on-premises Exchange 2016 CU19 server to Exchange Online. Running the SourceSiceValidation.ps1 script outputs several orphaned MEPFs in our Active Directory, and I get a similar output from the ValidateMailEnabledPublicFolders.ps1. The recommendation is to delete the orphaned MEPFs, but I'm running into an oddity that I just don't feel comfortable deleting. There's a PublicFolder named "Schema" in our MESO OU, and it just feels wrong to delete anything named "Schema" in a database. Get-ADObject "CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=***" | fl DistinguishedName : CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=*** Name : Schema ObjectClass : publicFolder ObjectGUID : 9*******-8***-4***-8***-2*********** Any advice on how to determine if this object really is safe to remove? Thanks!
EXRCA autodiscover test failure
Preparing to configure Exchange Hybrid between the On-Prem Environment and O365 we ran the ExRCA connectivity test for outlook access. The test fails at the autodiscover testing for XML response Attempting to send an Autodiscover POST request to potential Autodiscover URLs. Autodiscover settings weren't obtained when the Autodiscover POST request was sent. The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.XXXXX.com:443/Autodiscover/Autodiscover.xml for user email address removed for privacy reasons. Additional Details Exception details: Message: The operation has timed out Type: System.Net.WebException The Exchange server is published by a simple DNAT The On prem environment is made of two Exchage 2016 CU23 Servers in DAG . thanks SC
Supported / recommended .Net versions Exchange SE on Windows Server 2019
I’m reading up on the Exchange SE upgrade, but there’s something I don’t understand. We are currently running Exchange 2019 CU15 on a Windows Server 2019 server (desktop experience). My initial plan is to perform an in-place upgrade from Exchange 2019 CU15 to Exchange SE, while remaining on Windows Server 2019 for the time being. From what I’ve read, this should be possible: https://techcommunity.microsoft.com/blog/exchange/why-%E2%80%9Cin-place-upgrade%E2%80%9D-from-exchange-2019-to-exchange-se-is-low-risk/4410173 https://learn.microsoft.com/en-us/answers/questions/2182463/upgrade-exchange-2019-to-exchange-se According to the supportability matrix, this should also be supported: https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix Exchange Server SE is supported on Windows Server 2019. What I don’t understand is the table for .NET Framework support. It seems like Windows Server 2019 is missing for Exchange Server SE in that table, just like Exchange Server 2019 CU15 on Windows Server 2019 with its corresponding .NET version. https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019#additional-requirements-and-information Does anyone have an explanation for this? I’d love to hear it!
Internal mails get sent to primary smtp instead of alias
Hey there, in our company we have a service mailbox (user mailbox) with several aliases for different top level domains. Before they were all separate mail boxes with different mail rules, but for simplicity and management we merged they all on the main (.com) domain and combined the mail/forwarding rules. Now we have the issue that internal mails sent/forwarded to the alias domains, automatically get resolved and sent to the primary SMTP address and therefore the mail rules don't get triggered. Alias also won't show in the mail header. We have already deleted all offline address books(OAB), enforced the use of the GAL (via client and registry) and cleared all caches. Also, not all internal mail accounts are affected, since this usually happens with accounts which are in the delegation of the service mailbox (via security group) yet not all of them are affected. Any suggestions?
Need expertise advise on an event of mass mail-send
Hi all, We have a consultation from one of the application team about a mass mail that they are planning to send the number of emails is 60k, the challenge here is we cannot ask them to create group and send out an email because each of the recipient will be sent with a distinctive attachment and distinctive mail body content, hence no solution will work for now. We have a hybrid exchange setup with an Open SMTP Relay that connects to around 32 Exchange onprem servers and these servers will route those mails to Office365 Exchange Online as all of our mailboxes are hosted in Exchange Online. ALthough i am suggesting them to break these down to smaller batches and send in different time-slots giving 30 minute gap after each gap. I just want to be thoughtful and give the best suggestion, so what are all the things i would need to look into from Exchange standpoint and end to end monitor the situation.Outlook Intermittently not Displaying Notifications
My department has a daily Standup meeting led by the CTO of our company. It includes all of our developers, the CEO and myself, the admin. For the last several weeks, we've had a very puzzling issue where Outlook notifications for these meetings do not display for random participants. The problem will affect a handful of users for a few days, and then move on to different participants for another few days, and so on. For the last couple days, it has been my turn not to get notifications. All my settings are correct, and I'm getting notifications for other meetings in my schedule, just not this one. The meeting is set to display a notification 15 minutes before start There are no restrictions on notifications in either my Outlook settings, or Windows settings My Teams status is set to Available Do Not Disturb is set to Off Focus Time is also set to Off My desktop computer is plugged in, with no option for Battery Saver We do not use any Add-Ins with our mail clients It's embarrassing for me that the devs and C-suite get to start every call asking who didn't get the notification. I don't like that this naturally progresses to a lot of criticism of Microsoft from our Mac-using developers. I'm unable to find any resources on the web to help me, so here I am. Can someone please tell me how permanently to remove this topic from the top of our daily meeting agenda? Thank you.Roomfinder x onprem rooms
Some users are starting to report that they can't see the room status in room finder that used to work. The roomlist where there are rooms whose accounts are on-prem, all rooms appear as unchanged, the list where there are rooms that have already been migrated, the status is fine. If the user opens the scheduling assistant and adds an on-prem room, the status is also fine. The status is the same in outlook desktop and online outlook, but mobile outlook works without a problem. Has anyone encountered this?Removing Public Folders in Exchange 2016 Hybrid
We have Public Folders, and Public Folder Mailboxes in Exchange 2016 Hybrid. All users' mailboxes have been migrated to Exchange Online. We want to discontinue, remove / Delete Public Folders in Exchange, don't want to migrate onto Exchange online. What is the best practice to delete Public Folders in Exchange 2016? Any guidelines to check Public Folders usage, backup, removing without business interruption much appreciated. Thanks in advanceLogin Probleme Apple Mail
Hallo Zusammen, bis Mitte Juli lief bei uns alles wie gewohnt: Wir haben Outlook im Office 365 Abo. Dieses wird auf Mac und Windows genutzt. Der Account vom Chef (Mac) wird auf den Macs der Assistentinnen ebenfalls abgerufen. Er ruft seinen Account zusätzlich Zuhause (Macbook) und iPhone ab. Wie gesagt bisher ohne Probleme. Seit Mitte Juli geht nichts mehr bei ihm. Nur wenn ich die moderne Authentifizierung abschalte klappt alles wie vorher. Dafür können sich dann diverse andere Kollegen nicht mehr in Outlook (Windows) anmelden und nur noch den OWA nutzen. Support ist überfragt und sagt, dass man nur noch auf drei Clients einrichten kann. Das ist aber ja keine Lösung. Habt ihr eine Idee? Vielen Dank vorab
