Automation

 View Only
  • 1.  Get-PatchBaseline network port?

    Posted Jun 16, 2020 09:10 PM

    Does Get-PatchBaseline and New-PatchBaseline use a different port to communicate to vCenter and VUM compared to other PowerCLI cmdlets?

    I'm trying to use a script I have used multiple times in our internal environment against a vCenter in a much more locked down environment.  We have port 80 and 443 open from the management server to vCenter and I can run most PowerCLI commands, but these are giving me an error about not being able to connect.  I expect I'll need another firewall rule, but couldn't find any documentation about it using a different port.



  • 2.  RE: Get-PatchBaseline network port?
    Best Answer

    Posted Jun 16, 2020 09:16 PM

    Afaik, the VUM SOAP port is TCP 8084.

    So I assume the PowerCLI VUM cmdlets require that port be open (next to TCP 443)



  • 3.  RE: Get-PatchBaseline network port?

    Posted Jul 17, 2020 01:10 PM

    Port 8084 did it.  Had the firewall opened on that port and I can now manage baselines.