I have a virtual testing environment for developing scripts. As .NET isn't capable of all the possibilities PowerShell offers I use Remote PowerShell Runspaces.
My problem is now, that I can't reach the WinRM-Service on the FileShare-Memberserver, although the service is running.
winrm quickconfigtells me that the service is running and configured on all parties.
- If I run the command
Test-wsmanon the FileShare itself it isn't a problem either.
- I obviously restarted the service a couple of times
- With my remote script, I can reach the Exchange Shell on the FileShare, but not the MS PowerShell
- I can connect to the server manually with the "Remote Desktop Connection"-Application
- At one point I deactivated all firewalls, because I wanted to merge out the possibility that the request gets stopped there.
I made a quick drawing of the Server structure within my virtual testing Environment. (Red Arrows mean that the
Test-WSMan command didn't work)
I'm have no clue how to continue on with this problem. I've read so many things on the Internet which didn't help. I went through all the steps of the TechNet Blog "about_Remote_Troubleshooting". Most of all that that my script can reach the Exchange PS on the same server blows my mind. I asked a question on this topic on SO a couple of months ago, because I thought the ShellUri of my script was wrong, although it worked for the PS on the DC.
So if anybody has a hint for me what I could try next, I'd be very thankful.