New
#20
See if any of these steps help. Connecting Hyper-V Manager to another PC - Windows 10 Forums
Note I don't know if they are all still required - the method in the tutorial seems far simpler - but it wouldn't harm to try doing the host file, firewall, configuring winrm etc. Can always undo it if it doesn't help.
EDIT : You should persevere - it is really excellent being able to manage a PC remotely and this looks ideal.
Not just for Hyper-V management but remote firewall, event viewer and all the other stuff. I never could get remote firewall snap-in to open on remote PC so I'm for sure going to try this as soon as I'm allowed to use my other PC...
I'm quite exited about it really so thanks @Kari for this tutorial - it looks like the best new Windows stuff I've seen in years.
Last edited by lx07; 21 Sep 2018 at 13:08. Reason: Don't give up!
@Martin, one thought: do your local admin account have password? You cannot connect to your host or other computers in WAC without password. WAC will then show a Kerberos / authentication error as shown in your original post.
If you don't use passwords, try to set up one now, then restart and sign in with new password, and try WAC again.
Kari
I use an MS account with a password. I usually autologin with netplwiz boxed unchecked, but I also tried it with box checked.
Does the hidden administrator account need a password as well?
I also tried using a different account with the "manage as" etc.
I am not part of a domain or anything.
I went into GPE and tried different options - nada!
I am almost wondering if it is 1809 that is the issue but I cannot download any earlier version.
I have 1809, too, having no issues.
Yes, built-in admin needs to be enabled and have password, if used in WAC. That is worth testing: Enable it, sign in once and set password for it, sign out and back in once to "activate" new password. Sign out, sign back to your local admin account, start WAC and select the computer you want to manage, then Manage as:
Remember to enter account as PC_NAME\Username, enter password, click Continue:
Kari
You manage both your host and other computers added to WAC with one of your host admin accounts. You don't have to use built-in admin account. Any local admin account is OK. From Manage as link you can change the management account to any admin account, including built-in, subject to account being enabled and having password.
Kari
Decided I'd give WAC 1809 a try ... not sure it's the same issue cereberus is having or not ...
1. Got WAC installed and setup on my Desktop PC
2. Can see/manage the Desktop PC
3. Can see Laptop PC, but not manage (can't connect to it no matter what credentials I use) ???
a. Tried PC-NAME\Administrator and PC-NAME\Username
4. Both PC's are using local accounts (admin) with passwords
5. Both PC's have credentials for each other in Credentials Manager
6. All applicable Services are running on both PC's
7. Firewall Rule set on both PC's
Hi @Kari
I finally got it working by using Manage As, and entering my current admin account and password. I had done this several times but it just did not work. I think it was messing with GPE that did it - specifically after I did this - I enabled this and then set to not configured. Manage As then accepted my credentials and it is now working.
Only minor detail, is I seem to have to do it after each restart but it at least allows me to pick the credential rather than type it in.
Now to try and look at unbuntu how we first stated!
So here it is- Yippee!
The management account is and should be one of the admin accounts on your host, in your case the desktop PC.
WAC is a remote client on local host, the Manage as account is the account used to connect to your admin panel (remote host). There's no need to use credentials from any other managed computer.
That being said, did you do the registry trick:
In elevated PowerShell or Command Prompt, enter this command:
REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1
Kari