[Enhancement Request] Stop needing Admin$ access to use PowerShell Direct

[AlexHeylin]

Arising from microsoft-hyper-v-f25/powershell-direct ... 92185.html

There is a requirement for ongoing access to the admin$ share on the hypervisor / GIP for PowerShell Direct to work. This should not be needed once all components are deployed. Admin$ was firewalled off as part of hardening the hypervisor (which is also GIP) prior to production. Everything else in VBR has worked fine, but it broke PowerShell Direct.

IMO Nothing in Veeam should require ongoing access to admin$ shares or other attack vectors.

Thanks

[PetrM]

Hi Alex,

For some reason, I overlooked the topic you're referring to. I cannot remember why we have the requirement for admin$ on the hypervisor for PowerShell direct, please let me have some time to clarify this part of our logic and update this topic.

Thanks!

[AlexHeylin]

Thanks Petr