Outlook 365 keeps asking for password with Exchange 2019
Hi guys, I would like to ask if you didn't face the similar problem last few weeks when using Outlook 365 connecting to on-premise Exchange 2019. Office 365 does not have exchange online setup and there is not authorized domain, so there couldn't be any colision with on-premise exchange autodiscovery. Few users using Outlook 365 started reporting that their Outlook keeps asking for password and when I was remotely connected to those users, they used correct username and password in the prompt (so there is not any problem with DOMAIN\ or @domain.com username format). Their login to OWA works correctly so password is correct too. The worst is I cannot find any reason why it's still asking for password and in very random intervals. It’s also good to say that Outlook 2019 does not have such issue and all users with Outlook 2019 works correctly and problem is observed only on Outlook 365. Couldn't be there some incomaptible update in Outlook 365 inside, as our team didn't do any update to Exchange 2019 for more than 3 months including update, configuration change (except new users) and I'm 100% sure that exchange is not changed anyhow. Thanks
hello darkness my old friend worrying emails in draft
hi everyone, we run on premise exchange 2019 and outlook clients keep showing a email message in Draft folder with content - "hello darkness my old friend" server is fully patch with latest cu but message keeps coming back. Any idea how to prevent this? Thanks
Exchange Hybrid - On-Prem mailboxes can't send to Online mailboxes
We're now running Exchange Hybrid OnPrem: Exchange 2019 latest patch. On-Prem mailboxes are not able to communicate with mailboxes in Exchange Online in any way. The other way around is working fie though. Mailboxes on-prem: The communication to Exchange Online mailboxes isn't working > Can't send emails to Exchange Online mailboxes, or see free busy of Exchange online mailboxes and can't send calendar invites. Mailboxes in Exchange Online: Receive emails from external sent to: email address removed for privacy reasons - working. Receive emails from external sent to: email address removed for privacy reasons - working. Receive emails form external setn to: email address removed for privacy reasons - NOT working. Receive emails from internal on-prem mailbox - NOT working. No matter to which domain it is sent. Calendars: Users can fully see on-prem calendars and can also send invites. Send emails to external and internal - working. The Exchange on-prem queue shows: DeliveryType: DnsConnectorDeliver Status: Retry NextHopDomain: cadomain.mail.onmicrosoft.com The bounce back emails the on-prem mailbox receives when trying to send to a mailbx that is online: Server at cadomain.mail.onmicrosoft.com (104.47.75.164) returned '400 4.4.7 Message delayed' 3/24/2023 3:38:01 AM - Server at cadomain.mail.onmicrosoft.com (104.47.75.164) returned '450 4.4.316 Connection refused [Message=Socket error code 10061] [LastAttemptedServerName=cadomain.mail.onmicrosoft.com] [LastAttemptedIP=104.47.75.164:25](Socket error code 10061)' This is the on-prem Exchange delivery report: Delivery Report for usernametest2 (usernametest2(at)domain.ca) Submitted3/24/2023 9:25 AM EXCHANGE2019 The message was submitted to on-premExchange.domain.local. Pending 3/24/2023 9:25 AM on-premExchange.domain.local Message was received by on-premExchange.domain.local from on-premExchange.domain.local. 3/24/2023 9:25 AM on-premExchange.domain.local The e-mail address for recipient "usernametest2(at)domain.ca" was updated to the e-mail address "usernametest2(at)cadomain.mail.onmicrosoft.com". The message is in the process of being delivered. Submitted 3/24/2023 9:27 AM on-premExchange.domain.local The message was submitted to on-premExchange.domain.local. Pending 3/24/2023 9:28 AM on-premExchange.domain.local The e-mail address for recipient "usernametest2(at)cadomain.mail.onmicrosoft.com" was updated to the e-mail address "usernametest2(at)domain.ca". The message is in the process of being delivered. 3/24/2023 10:40 AM on-premExchange.domain.local Message delivery is taking longer than expected. There may be system delays. For more information, contact your email admin.Exchange 2019 CU14 PowerShell and ADDriver log history issues
We have two Exchange 2019 Standard servers in a DAG and after updating from CU12 to CU14 one of those servers no longer logs PowerShell or ADDriver history. For example in the Application Log we see: Event ID 6003 Source MSExchange Common - RpsCmdletLogs: Failed to create the log directory: C:\Program Files\Microsoft\Exchange Server\V15\Logging\CmdletInfra\LocalPowerShell\Cmdlet because of the error: Access to the path 'C:\Program Files\Microsoft\Exchange Server\V15\Logging\CmdletInfra' is denied.. Logs will not be generated until the problem is corrected. Event ID 6003 Source MSExchange Common - ADDriver: Failed to create the log directory: C:\Program Files\Microsoft\Exchange Server\V15\Logging\ADDriver because of the error: Access to the path 'C:\Program Files\Microsoft\Exchange Server\V15\Logging\ADDriver' is denied.. Logs will not be generated until the problem is corrected. These events do not appear on our second Exchange server. The issue is with the first server to be updated and they were both updated from the command line as per this article without any errors: http://www.alitajran.com/install-exchange-cumulative-update I have checked security permissions are the same for both servers for the paths mentioned. Has anyone seen this or have any ideas how to troubleshoot ? Thanks DM
Issues after Exchange 2019 CU15 install
Hello, We have some issues with our Exchange server. After CU15 install we have high(er) CPU usage at the server and slow(er) Outlook (online no cache mode enabled) connection at the client. MAPI over HTTP and Exchange Extended Protection is enabled. Have anybody else who have the same issues?Shrink Exchange Database Volume
Hi team, An unusual scenario here may be. However, we have migrated users to cloud and the disk volumes that were provisioned through the SAN is barely being used. So we would like to shrink it from lets say for ex: 1.5TB to 900GB for volumes which holds DBs and Logs. I want to know if this is supported? PS: Env is Exchange 2019 Thank you.Exchange 2019 Hybrid Configuration Wizard Licence
We were planning to run Exchnage 2019 for hybrid management. This link https://docs.microsoft.com/en-us/exchange/hybrid-configuration-wizard-faqs?source=docs suggests running the HCW with Exchange 2019 wouldn't allow us to get a free hybrid licence key as it's not supported. However, I have seen articles online where people have run the latest HCW and got a free key for Exchange 2019. They suggest that the Microsoft literature is just behind the times since the latest HCW was released. Has anyone done this or seen that it's possible please? We are currently running Exchange 2016 with the free hybrid licence, but Exchange 2016 doesn't support Server 2022 AD servers or functional domain level. Thanks
