PowerShell Direct won't work on Win Svr 2022?

[AlexHeylin]

Following on from microsoft-hyper-v-f25/powershell-direct ... 86874.html

On case #07111205 I just got told v2.0 exactly is required. Please can the source of this info be hunted down and corrected.
Three days so far and still no PowerShell Direct on Win Svr 2022. I didn't need to lose another day to incorrect information from support team.

If anyone has time to take a look at this case I'd be grateful because so far it looks like either the non-persistent agent executables are corrupted (and didn't get replaced by a v12.0 -> v12.1.1.56 upgrade), or they don't work on Win Svr 2022 VMs as it keeps insisting it can't find the VeeamVssSupport service which is installed and running (or at least is left installed and running after PowerShell Direct "fails" according to VBR)

Code: Select all

01/02/2024 03:31:22   5564  INFO    ================================================================================================
01/02/2024 03:31:22   5564  INFO    User: WIN-NEJ8D3EUCL6\Administrator
01/02/2024 03:31:22   5564  INFO    VeeamVixProxy started.
01/02/2024 03:31:22   5564          Command line: ["C:\Users\administrator\AppData\Local\Temp\VeeamVixProxy_tmpDB3F.exe" -func UnregisterService -out C:\Users\administrator\AppData\Local\Temp\tmpEB42.tmp -svcname VeeamVssSupport -scmoptimeout 600000 ]
01/02/2024 03:31:22   5564          Unregistring service [VeeamVssSupport]
01/02/2024 03:31:22   5564  ERR     Error: 
01/02/2024 03:31:22   5564  ERR         Cannot open service. Machine: []. Service name: [VeeamVssSupport].
01/02/2024 03:31:22   5564  ERR         Cannot open service.
01/02/2024 03:31:22   5564  ERR         Win32 error:The specified service does not exist as an installed service.
01/02/2024 03:31:22   5564  ERR          Code: 1060
01/02/2024 03:31:22   5476  INFO    ================================================================================================

I find this very suspicious. Why is the machine field empty? Why not the name of the guest machine, or at least '.' to indicate "this machine"?

Code: Select all

Machine: []

Thanks

[AlexHeylin]

For clarity - PowerShell Direct itself works perfectly. VBR uses it to access the VMs, installs the VeeamVssSupport service (which it leaves there) then says PowerShell Direct is not working.

[AlexHeylin]

The multiple VMs we have in our own infrastructure which are being backed up using PowerShell Direct are all 2019 or earlier. The one 2022 VM we have being backed up appears to be injecting over the network but the log is not explicit (which is suboptimal).

[AlexHeylin]

Traced to firewalled access to Admin$ share on HV/GIP. Made much harder to find by incomplete documentation and logging which pointed in other directions. Enhancement Request raised microsoft-hyper-v-f25/stop-needing-admi ... 92340.html