Clients with RPC over HTTPS non exchanged mode receive server unavailable message after server reboot
I have clients that I set up to use RPC over HTTPS in non Cached mode. This was working fine until I rebooted the server. Now I am getting all these calls about an erro stating the server is unavailable. I enabled cached mode on a few of them and they connect fine again. OWA works as well. What happened and how do I get this working again, and always, with non cached exchange mode?
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.