I'm stumped... We have a bunch of Exchange servers that I've slowly been adding to SAM for monitoring. The first 2 Exchange servers are hybrid 2013 servers so we can do mixed Office 365, and on-prem setup. These boxes went mostly without a hitch. The only glitch was a missing perf counter.
The next box added was a 2010 Mailbox server, it went smoothly, no issues, even pointed out that one of our Exchange services wasn't running (this is what the monitoring is for after all).
The next 2 boxes both failed. They both complained that the user I was using wasn't a local admin, so couldn't do the automatic configuration. I checked, and checked again. The group the user is a member of is in the local admins group, but for kicks, I even added the user directly to the group, no luck there. So I dutifully followed the manual instructions. Courtesy of the fairly well written docs, this was actually pretty easy. The configuration went well, and both boxes reported that the connection was now successful when pressing "Test Connection". This is where I think I'm done, and SAM would be happy... Not so much:
"PowerShell FullLanguageMode is not configured on Remote Host" and directs me to the information on configuring Exchange. Nowhere do I find details on setting up "FullLanguageMode". I did a quick compare between the web.config files on the 2010 server that worked, and the ones that didn't, and found that it looks like the automated process modifies the web.config for the /PowerShell web application. In that file, I do see that the broken hosts had <add key="PSLanguageMode" value="RestrictedLanguage"/>, while the working host had <add key="PSLanguageMode" value="FullLanguage" />. So I backed up the config on the broken hosts, copied the working config, and reset the app pools. I'm still seeing the same error, even after about an hour.
Just for kicks as well, I verified the output of $ExecutionContext.SessionState did show FullLanguage on both boxes for LanguageMode. I'm not entirely sure where else to turn, any hints?