I have searched for the past two days in the existing threads for a solution to the issue we are currently experiencing to no avail.
We are a SBS2011 Standard deployment. I consistently apply updates/patches/fixes to our environment through WSUS. I am our administrator, but color myself a 'high-end user' as it pertains to server environments. I have run EMC before - as I had to setup the initial mail connectors, etc.
I have attempted numerous times in the past couple of days to open the Exchange 2010 EMC. I get the main screen with the post installation tasks, but when clicking on the 'Microsoft Exchange On-Premises' link it begins the initialization process. As it's 'getting management role assignment for: <domain>/USER' it seems to take a long time, (I am the only client/user which is using the server) and ultimately fails.
"The following error occured when getting management role information for <domain>/USER" Processing data from remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.
In response to the suggestions in the error:
1. Server name is valid. We have one server. This is it.
2. Firewall exception: not sure specifically what sort of rule I'm looking for, but if it was part of the default installation parameters for when we installed SBS 2011 - it was working.
3. I cannot seem to locate the 'Remote_Troubleshooting' help topic indicated.
I'm pretty comfortable that we've not intentionally modified our server installation from when it was originally installed. We rely on it to essentially function like a toaster (no fuss). This system is not deployed full-time. We turn on the server and the client PCs for specific functions - and then shut them down and pack them away once our need for them is over.
Any detailed ideas/steps I can follow to ensure that this is corrected (hopefully short of rebuilding the environment totally new?)