Skip to content

Instantly share code, notes, and snippets.

@mstum

mstum/gist:2fb41dfe16a9fd195b126d9b1fe75fd2

Last active July 10, 2017 02:08
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mstum/2fb41dfe16a9fd195b126d9b1fe75fd2 to your computer and use it in GitHub Desktop.
Save mstum/2fb41dfe16a9fd195b126d9b1fe75fd2 to your computer and use it in GitHub Desktop.
Download ZIP
Remotely manage Hyper-V when not domain Joined
Raw
gistfile1.txt
Server:
* Enable-PSRemoting (use sconfig for that)
* Enable-WSManCredSSP -Role Server
Client:
* Run PowerShell as Admin
* Enable-PSRemoting
* Set-Item WSMan:\localhost\Client\TrustedHosts -Value "fqdn-of-hyper-v-host"
* -Concatenate can be used to add
* https://stackoverflow.com/questions/21548566/how-to-add-more-than-one-machine-to-the-trusted-hosts-list-using-winrm
* Enable-WSManCredSSP -Role client -DelegateComputer "fqdn-of-hyper-v-host"
* Not sure how to add/remove individual computers - need to test.
* gpedit.msc
* Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials with NTLM-only server authentication
* wsman\fqdn
* In Hyper-V Manager, use `~\Username` syntax to connect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment