WinRM issues when using VCSA

[seasider72]

I'm really hoping someone can give me some steer with this one, bear in mind I'm not a developer - I'm infrastructure.

We have a lot of automation scripts which run against our Windows based vCentre 6.0 servers.   We are looking at migfrating to VCSA 6.5, but during testing we have experienced the following error when pointing the scripts to the new vCentre appliance.

"WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet."

Our automation team have mentioned a couple of things to me

1. Powershell remoting needs to be made available on the VCSA

2. need to run the invoke-command

I believe the reason why we aren't facing problems on our Windows vCentre server is because we have powershell installed on the server, and WinRM and the invoke-command are using the powershell software and the windows RM service.    On the VCSA we have neither, clearly due to this being non-windows.

What options/workaround are available?

[daphnissov]

Ok, I guess first of all is the question:  Why do you need to have remote access to the vCSA directly? What are your scripts doing that require access to the underlying operating system?

vCSA is a Linux-based appliance, and you cannot install other software or agents inside. This most certainly includes PowerShell Core.

If you can say what these scripts do, it's possible to find an alternate method, because there shouldn't be any valid reason for needing regular, remote access to the vCSA's OS to interact with vCenter.