In this post I’m going to show you how to troubleshoot connectivity issues, specifically RPC Client Access.
Do you think this is only a topic for Exchange 2010? That’s not true as Exchange 2013 has still the service Microsoft Exchange RPC Client Access. And there are still logs written for.
What do you need in order to parse those logs?
- a server from where you will run the script. this server needs SMB access to all Exchange server as we will access the RCA logs via UNC path
- adjust the execution policy. Here is an example, which bypass the policy only for the running process:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
- the script itself