[Issue] Exchange Log Collector - One Server Fails within Invoke-Command of main execute

Describe the issue
By default Exchange Log Collector goes through and checks out if we can hit each server with Invoke-Command. If we can't it gets removed from the list. However, we can oddly run into issue within the main execute that causes the script to bail out and stop working. Sometimes this is right away, other times it is a soft error that allows the main remote execution to continue prior to the main execution thread then bails out. Need to improve the logic to better handle these scenarios.

Expected behavior
If we aren't able to run the main Invoke-Command and it is never executed on the main threads of the remote machines, then bail out. Otherwise, we should attempt to handle the servers that we can still talk to.