Seeking for advices here, I don't know what's happening.
This started with a vulnerability report, saying that some servers in this environment has self-signed cert signed with weak hashing algorithm. That include both Exchange servers.
Took me some time to determine that the self signed cert that the vulnerability was talking about are Microsft Exchange and Microsoft Exchange Server Auth Certificate. Both were signed with SHA1.
So, I took the liberty to renew both in Exchange Admin Center (On-prem). Another scan show Exchanger servers does not have that vulnerability anymore.
But, problem start occuring. Users started receving prompts on their computer Outlook and mobile phone (using Airwatch), saying that the certi is invalid or the cert does not match the URL.
The way this Exchange was set up is:
Internal DNS has a zone, for [m.com... keep reading on reddit ➡
Some REALLY exciting Exchange Server news was announced for on-premises customers at the Microsoft Ignite virtual conference today!
Microsoft will be releasing the next versions of Exchange Server, SharePoint Server, and Skype for Business Server the second half of 2021. These new on premises server versions will only be available with the purchase of a subscription license, using a similar subscription model to Microsoft 365.
Does anyone know if it's safe to delete the files in here? I assume they are using in OAB generation but not 100% sure if they are safe to delete or should be being cleaned up automatically.
We are seeing this directory grow to 50+ GB and 6.5 million+ files on some servers. The files stretch back to 2017 (which is probably when the server was built).
We are running Exchange 2016 CU16.
Cheers for any assistance!
I have an office that experiences this message. When I use psping and ping outlook.office365.com:443 when they report the message happens, I can see a lot of packet loss.
This is a small business, total of 7 users with a Spectrum business class cable connection. 200/10 is the speed they pay for.
When the message happens, Outlook freezes up. It happens at random. It happens sometimes changing folders, doing a search.
I have tried every single fix including:
- Disable antivirus, no antivirus, clean install
- Power cycling the cable modem (they use Spectrum) will usually clear the problem up - sometimes for a week, sometimes for 24 hours
- Prefer IPv4 over IPv6, disabled IPv6
- Re-create profile
- Safe mode, make sure no add-ons are enabled
- Disabled hardware acceleration
- Clean install
- Brand new computer, i9 9900K, 32GB Memory, Intel Gigabit NIC, 500 GB NVMe PCIe SSD class 40
- Certified the data run to patch panel
- This ha... keep reading on reddit ➡
Sent 250 workers to WFH, although half the company is already on a WFH plan. Sure enough one of my 2016 Exchange servers just got hammered and broke it's CAS connections for users to get into Outlook. Load Balancers were fine.. Storage was good (not great, but no drive over 80%). CPU and Ram were near 100% at time though, being taken up by several Microsoft.Exchange.Store.Worker.exes. the other box, the pimrary box that is, was fine.
A reboot fixed it, but this doesn't seem to be a coincidence. My boxes have been fine for months and the first day everyone connects remotely, one barfs on itself.
Any ideas? What sort of underlying things are changed when workers go from connecting to Outlook internally to externally? I feel like that's what caused this.