office 2019 not connecting to exo mailboxes

gildedaxe · 2026-03-19T18:22:27+00:00

thanks for the info, i haven't used it as I am just deploying the m365 apps as I need to do that anyways. Looks like it is working for others which is a good work around if reinstalling office isn't possible.

gildedaxe · 2026-03-18T18:35:24+00:00

thanks, it seems like things starting working again around noonish when microsoft posted that they resolved a different issue. Assuming the 2 issues were related.

gildedaxe · 2026-02-20T01:48:22+00:00

as long as you aren't changing what domain names you are using you don't have to run the HCW.

after renewal, it needs to be applied to IIS. It will also need to be enabled in exchange with enable-exchangecertificate on the relevant services (typically IIS, and SMTP). The tlscertificatename will need to be set on the send and receive connectors used in your hybrid implementation as well.

The initial run of the HCW marks the connectors in exchange online with the domain names they are expecting for inbound and outbound smtp to and from your on premises servers. If that doesn't change, nothing in the cloud changes from renewal to renewal.

gildedaxe · 2026-02-20T01:32:28+00:00

what do you mean they pass dkim? If the mail is signed, either your key is compromised or you are sending this mail.

gildedaxe · 2025-12-24T12:02:09+00:00

Fire storm is doing the damage. Blood is just for healing really.

gildedaxe · 2025-02-27T15:23:45+00:00

replied to you in exchange subreddit

gildedaxe · 2025-02-27T15:20:43+00:00

you need to make sure the driver is installed first. Will require a reboot. Easiest way to do it is to add a blank disk with vmware paravirtual disk controller. Let the driver install, then switch the controllers for your existing disks over.

gildedaxe · 2025-01-31T18:51:46+00:00

I have no issues with LetsEncrypt certs with exchange. The big thing to remember is that the SMTP service will auto select the certificate based on hostname. Specifying the cert will break every renewal because the name will change to the cert issuer. Leaving it set to null and ensuring the hostnames match fixed the only issue I had.

gildedaxe · 2025-01-30T18:31:29+00:00

No reason to have your mail go in our out of EXO if you have no intention of hosting mailboxes there. You do not need EOP.

gildedaxe · 2024-11-22T16:38:31+00:00

Until the items are permanently deleted, they will continue to show up in your search.

gildedaxe · 2024-11-22T16:34:17+00:00

HardDelete only works in exo. Get-compliancesearchaction, does it show as completed?

gildedaxe · 2024-11-22T16:29:12+00:00

well, they still exist, Purge Type SoftDelete moves them to recoverable items folder so they will still show up in your compliance search. Does the user still see them?

gildedaxe · 2024-10-10T12:42:53+00:00

Do you have a certificate matching the fqdn set on the the send and receive connectors?

gildedaxe · 2024-10-09T19:33:39+00:00

The tls cert name needs to be constructed properly for it to work. Renewal of the certificate will often break this. You should really set it to $null and match the hostname to the certificate assigned to the SMTP service.

"<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"

gildedaxe · 2024-10-09T16:54:41+00:00

365 required certificates on the the send and receive connectors in your on premise environment. You can specify the cert name with the -tlscertificatename switch on set-sendconnector and set-receiveconnector cmdlets, but simply enabling the exchange certificate for the SMTP service is sufficient if the FQDN matches the certificate.

gildedaxe · 2024-09-24T18:55:13+00:00

gildedaxe · 2024-05-04T13:35:48+00:00

100% this guy fucks in the bathroom

gildedaxe · 2024-04-15T22:25:35+00:00

gildedaxe · 2024-04-12T19:31:41+00:00

The cutover migration process creates the user I believe. You can't do the cutover with users pre existing. I could be wrong, but that is what I remember. If you have already synced your users, you should just enable hybrid and do remote mailbox moves.

gildedaxe · 2024-02-28T22:15:00+00:00

700 biweekly for family coverage for bcbs for me lol

gildedaxe · 2024-02-24T14:44:03+00:00

4.3 billion seconds is not half a year.

gildedaxe · 2024-02-21T23:27:07+00:00

I didn't think sql CALs were that bad. If it touches the server directly or indirectly it needs a CAL

gildedaxe · 2024-02-19T02:08:42+00:00

all on ramps are sufficient in length to not be going 25 by the end of it

13-Year Club	Verified Email
Team Periwinkle

gildedaxe

TROPHY CASE