Forum Widgets
Latest Discussions
Allowing normal users to delegation mailbox
Hi, We have a request to allow normal users to delegate their own mailboxes to other users. Following a call with Microsoft normal users can delegate folder and not the mailbox therefore requiring any administrator to make the change. Has anyone come up with a process which allows a normal user delegate via a PowerApp or Power Automate? Regards Mike
Address List additions/removal are not showing in Outlook or OWA
I am trying to clean up our Address lists. I've used powershell to remove several old obsolete address lists and I've used the Exchange Admin Center to create some new lists. In Exchange Admin Center, I can see the changes I've made in Exchange Management Shell and in the Shell, I can use the get-addressList get-recipient commands to list members in the new lists I created. What I don't see is the new lists in Outlook or in OWA. These new lists were created 4 days ago. I am seeing new users in the old address lists in Outlook so those are being updated. On a separate note, I can see new dynamic distribution groups I created in Office 365 in Outlook and OWA. Why can I see new users but not new address Lists? Why do I still see the Address List Names for address lists I have deleted? (None of the Address lists I deleted had any remaining members.) We have a Hybrid Exchange/Office 365 Environment. We are using Exchange Server 2016. Here is some addressbook info: Get-OfflineAddressBook | fl *VirtualDirectories*, *GlobalWeb* VirtualDirectories : {<servername>\OAB (Default Web Site), <servername>\OAB (Exchange Back End)} GlobalWebDistributionEnabled : False get-oabvirtualdirectory Server Name Internal Url External Url ------ ---- ------------ ------------ <servername> OAB (Default Web Site) https://<servername>.<domain>/OAB That web site though has an invalid certificate as the certificate is for a different domain. Would that be the problem? That URL is not our OWA site either. (Please note, I didn't set up the Exchange Server, I'm just trying to clean up our AD and do some reorganizing.)
Fully Migrating Exchange Server 2019 to O365
We currently have a Hybrid Exchange environment with Exchange Server 2019 on-premises and Office 365 (Exchange Online). All user mailboxes have already been migrated to Exchange Online, but we are still using the on-prem Exchange 2019 server for SMTP relay services. We are now planning to fully transition to Office 365 and decommission the on-prem Exchange server. Could someone please provide a detailed list of steps, considerations, and any dependencies we should be aware of to complete this migration successfully?
Exchange Hybrid sending external email from on-premises
I have an Exchange 2019 server setup as our hybrid server. Mail flow works fine to any mailboxes moved to Exchange Online, inbound from the Internet is delivered successfully to on-premises mailboxes. Where we're having trouble is trying to send email to the Internet from an on-premises mailbox. My preference is to route all email through Exchange Online, so in addition to the Send connector the Hybrid wizard created, I created a second connector using the * SMTP space and sending to our smarthost, aka the record in the MX value from Exchange Online. I also gave this connector a cost of 2 so it still uses the default send for email going to our tenant. Any email that isn't going to our tenant, so domain.mail.onmicrosoft.com, is immediately rejected with the error "Remote Server returned '550 5.7.64 TenantAttribution; Relay Access Denied [ValidationStatus of 'CN=SERVER' is UntrustedRoot]" The Exchange Online connector from our Org to O365 is set to use subject name of certificate, .ourdomain.com. I even tried setting it to the external IP the emails would come from and that failed as well. One thing I noticed in the send log, the subject name of the cert is mail.ourdomain.com, not *.ourdomain.com as shown in the example from this URL. So, I even tried updating the EXO connector to look for the subject name mail.ourdomain.com and still no luck. 550 5.7.64 TenantAttribution when users send mails externally - Exchange | Microsoft Learn I also tried the steps here. NDR error 550 5.7.64 TenantAttribution when sending emails through EOP - Exchange | Microsoft Learn What could I be missing?How does Purview/data lifecycle management on Mailboxes work for deleted mailboxes?
I have an inkling that it more or less keeps the Mailbox in the Recoverable Items set//folder/dimension, but I don't want to guess. We do not have a license for Purview, I just have discovered that we have policies in here setup and forgotten about (or migrated Compliance and Security, and forgotten about). I say this because I don't fully understand Purview (because I don't want to use it, and we don't have it), yet I have a 'keep forever' policy set on ALL Exchange Mailboxes, but it doesn't actually prevent me from Deleting them. Reading this and this doc, the word 'mailbox' appears 54 times. I have responsibilities and a life, but I did manage to find out when MAIL is deleted from Deleted Items, it goes to 'recoverable items' - a folder that exists in (somewhere). What I don't know is what happens if the entire Mailbox is deleted. I have archiving turned off. I notice that there is a separate 'inactive mailbox' article. I genuinely do not have the time or patience to read these massive docs, or the 100 other docs they link to, for a platform way outside my scale, that I don't intend on using. Anyone know? I need to understand how this works before I get approval on removing it.
HCW fails to download
Erst einmal Entschuldige mich mich falls ich diese Frage im falschen Kanal stelle Hallo versuche gerade mit dem "Programm" Microsoft.Online.CSE.Hybrid.Client.application die HYbrid Stellung zu realisieren komme aber nicht weiter . Das Programm startet einwandfrei. Die Datei Microsoft.Online.CSE.Hybrid.Client.exe.manifest wird aber nicht heruntergeladen In der Firewall kann ich keinen Blockierten traffic sehen. Meldung die Anwendung konnte nicht dedownloaded werden. Erforderliche Dateien fehlen in der Anwendung. Wenden Sie sich an den Hersteller der Anwendung OS Server 2012R2 Software Firewall ist aus Kein Antivirenprogramm aktiv Falls jemand ähnliche Probleme hatte und die lösen konnte wäre ich sehr dankbar über Hinweise wie das geschafft wurde. Der Support von Microsoft war nicht sehr hilfreich Ticket ist aber noch offen. Die Aktivierung von C:\HCW\Microsoft.Online.CSE.Hybrid.Client.application führte zu einer Ausnahme. Folgende Fehlermeldungen wurden entdeckt: + 'file:///C:/HCW/Application Files/Microsoft.Online.CSE.Hybrid.Client_17_1_2714_0/Microsoft.Online.CSE.Hybrid.Client.exe.manifest' konnte nicht gedownloadet werden. + Ein Teil des Pfades "C:\HCW\Application Files\Microsoft.Online.CSE.Hybrid.Client_17_1_2714_0\Microsoft.Online.CSE.Hybrid.Client.exe.manifest" konnte nicht gefunden werden.
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.Exchange 2016 CU23 breaks Outlook 2010 connection
Hello, I have an environment with an Exchange 2016 CU22, that connects to a public folders in legacy, which resides on an Exchange 2010. We have many users still using Outlook 2010 and all is working fine. Yesterday we decided, to my great regrets, to install CU23 and a nightmare began, Outlook 2010, on the first start since CU23, connects no issue, but if we close Outlook then reopen it, no more connections, it just shows disconnected and if I look deeper, I see it just keeps retrying but Exchange refuses it to connect. I looked everywhere in the CU23 documentation for changes and nowhere there is mention about Outlook versions and legacy connections being affected by it! Anything I can do to get Outlook 2010 going again? What happened on the first connection, what did Exchange tell Outlook to reconfigure? Newer Outlook works fine. All Outlooks connect with RPC because of the legacy public folders.
exchange 2013 to 2019 migration
Looking at the exchange 2013 migration path, for coexistence I found what it seems an error in the online documentation at the following links Exchange Server 2019 system requirements, Exchange 2019 Requirements, Exchange 2019 Memory Requirements, Exchange 2019 Client Compatibility | Microsoft Learn it says for 2016 that no previou exchange relesase are supported for coexistence. That's clearly wrong. Where can we find correct information for upgrade planning
Issue with Queue Viewer after Exchange 2019 CU15 Upgrade (Hybrid Mode Environment)
Hi everyone, I recently upgraded Exchange 2019 from CU12 SU5 to CU15 in a hybrid environment, and I'm now seeing an issue with Queue Viewer on the upgraded server. When I try to open Queue Viewer from the Exchange Toolbox, I get this error: "Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints." Columns listed in the error: NextHopDomain, DeliveryType, Status, MessageCount, NextRetryTime, LastRetryTime, LastError, Identity, CanSuspend, CanResume, CanRemove, CanForceRetry Environment: .NET Framework version: 528049 OS: Windows 10.0.17763.6414 Exchange 2019 Hybrid (on-prem + Exchange Online) Additional Info: The issue only appears on the CU15-upgraded node Queue Viewer still works fine on a CU12 node From that CU12 node, I can connect to the CU15 node and use Queue Viewer without errors Has anyone seen this before or have any ideas for a fix? Thanks in advance!
