Part 2 – Hyper-V Remote Management: You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer ‘COMPUTERNAME’


Update 14th Nov 2008. I’ve just released a script which does all this configuration in one or two command lines: HVRemote 

Quick links to the all parts in the series: 1, 2, 3, 4 and 5 

The second part of the extra-long blog post contains the steps necessary on the client machine. Part one concentrated on the server side configuration.

Step 5 (On the client)

Step 5 mirrors step 2 in the first part of this blog post, but on the client. Note also (again for convenience more than anything else), my Vista SP1 machine is actually itself a virtual machine running on the same physical machine as the server. You’ve got to love it when you can have a somewhat recursive technology 😉
 
Enable the firewall rules on the client for WMI (Windows Management Instrumentation). From an elevated command prompt, enter the following:

netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes

Make sure the command it successful and responds: Updated 8 rules(s). Ok.

wg27

If you now open “Windows Firewall with Advanced Security” from Control Panel/Administrative Tools on the start menu, you will notice eight rules, six inbound and two outbound have been enabled. (It helps to sort by Group)

wg28

wg29 

Step 6 (On the client)

This step creates a firewall exception for the Microsoft Management Console application (mmc.exe). From an elevated command prompt, enter the following:

Netsh firewall add allowedprogram program=%windir%\system32\mmc.exe name="Microsoft Management Console"

Make sure the command is successful and responds “Ok.”

wg30

You can verify that you succeeded in the above step by looking in the “other” Windows Firewall application. (No, I have no idea why there are two either….). Open "Network and Sharing Center" on the control panel, and click Windows firewall in the bottom left corner, then click "Allow a program through Windows Firewall" where you’ll see a new entry with the name “Microsoft Management Console”

wg31

wg32

wg33

Step 7 (On the client)

IMPORTANT!!!! You need to do this step in the following scenarios:

  • Client and server are both in a workgroup
  • Client is a workgroup and server is in a domain
  • Client is in a domain and server is in a workgroup
  • Both client and server are in domains, but there is NO TRUST between them.  

You DO NOT NEED TO DO THIS STEP if the client and server are in either the same or trusted domains. Go to step 8.

WMI makes calls back from the server to the client. This is entirely expected (and is not Hyper-V specific). When a server is in a workgroup, the DCOM connection from the server back to the client is "anonymous". This step therefore grants the appropriate permission.

On the start menu box (yes, well spotted, I need to apply updates), type dcomcnfg and hit enter to open Component Services. If UAC is enabled, click allow when prompted or enter appropriate administrative credentials.

wg34 

Expand the tree down through Component Services\Computers\My Computer, select My Computer, right-click, choose properties and select the COM Security tab.

wg36

Click Edit Limits in the Access Permissions area (do not confuse with Edit Limits in the Launch and Activation Permissions area). Select “ANONYMOUS LOGON” from the list of users, and make sure Remote Access/Allow is checked in the permissions area. Your screen should look like below.

wg37
Click OK and OK again, and close Component Services.

Step 8 (Away from the keyboard)

Take a deep breath and pat yourself on the back. Now do that again. A third time if you like. Then double-check to make sure you followed the above steps and those in part one  to the letter.  You did remember the step about restarting the server, didn’t you?

Step 9 (On the client)

Logon as the account you have granted permissions to (“john” in my walkthrough) on the client.

Start Hyper-V Manager from Administrative Tools on the Control Panel. Enter appropriate administrative credentials if UAC is enabled and the account is not an administrator on the client.

Click Connect to Server and enter the name of the remote machine.

Watch in awe as you get a screen like below. You can also see, it took me 2 hours, 24 minutes and 19 seconds to do this walk-through documenting it step-by-step. It should take you much less time!

wg39

Cheers,
John.

Update 14th Nov 2008. I’ve just released a script which does all this configuration in one or two command lines: HVRemote

Comments (103)

  1. Anonymous says:

    Hola Una herramienta imprescindible para configurar los servidores con Hyper-V para que se puedan administra

  2. Anonymous says:

    Hyper-V Management Console on Vista x64

  3. Evandros – can you post up the output of hvremote /show, plus a ping by name in each direction.

    Thanks,

    John.

  4. Anonymous says:

    Announcing "HVRemote"…., a tool to "automagically" configure Hyper-V Remote Management

  5. Dave. Yes. See the documentation for more info.

    Thanks,

    John.

  6. Anonymous says:

    Soon, I promise, I will be publishing part 3 which is the workgroup server-core version of “ Hyper-V

  7. Anonymous says:

    With the RTM release of Hyper-V just around the corner, I thought it would be a good idea to re-visit

  8. Anonymous says:

    日本語だと↓なエラーが出る件です。 「このタスクを完了するために必要なアクセス許可がありません。このコンピュータ ‘xxxxxxx’ の承認ポリシーの管理者に問い合わせてください。」

  9. Anonymous says:

    Although I thought I’d finished at part two, after even more emails and comments on part one and two

  10. Anonymous says:

    In my last post on installing Hyper-V for my home setup I said I had a number of issues.  One was

  11. Anonymous says:

    In my last post on installing Hyper-V for my home setup I said I had a number of issues.  One was

  12. Anonymous says:

    More for my own reference, as I keep having to search the Internet for this document and never bookmark

  13. Anonymous says:

    Aujourd’hui deux outils pour Hyper-V. Pas tout neufs, mais extrêmement utiles. Le premier vous servira

  14. Joel – first off, try and resolve the ping issue. Pings by default are disabled on Server, so try temporarily disabling the firewall and trying again. That should work by IP address at least. If name does not work, then it’s a DNS issue. You can verify that by temporarily putting an entry in windowssystem32driversetc on the client machine for the name and IP address of the server.

    I have a stack of subsequent troubleshooting steps, but let’s get the ping and DNS issue sorted out first – it’s often a common cause.

    Thanks,

    John.

  15. Darin – untrusted domains or part of the same forest? If the latter, then part 4 should work. Untrusted domains has seperate challenges which I’m still working through for a future part.

    Cheers,

    John.

  16. Zoltan – I answered your other comment on the HVRemote article. Please follow up on that one.

    Thanks,

    John.

  17. Greg – glad you resolved it 🙂

    Cheers,

    John.

  18. Anonymous says:

    So after even more feedback and questions, part 4 of this series provides the walkthrough steps necessary

  19. Anonymous says:

    It has been a little quiet on the blog front, but sometimes, at least in this case, I hope I’ve come

  20. Rob – there’s a couple of things here. Make sure you cover the steps in part 5 which covers a domain joined client to a workgroup server. Similar to this, but a couple of nuances.

    However, what’s most likely blocking this working is the external firewall you are describing. WMI/DCOM are not particularly "external firewall friendly" due to the number of ports you need to open, so I would not recommend the scenario you are trying to achieve. I’m not sure the exact list of ports you need for this – haven’t tried it myself, but as I understand it the default ports are

    135

    49152-65535  

    2179

    There’s a couple of articles about this you may want to read: http://msdn2.microsoft.com/en-us/library/ms809327.aspx

    http://support.microsoft.com/kb/217351

    If you’re also behind a NAT router, I don’t believe remote DCOM calls would work.

    I’m not sure of your exact topology, but I would look towards a TSGateway which you can remote Hyper-V manager through and use mouse (once the integration services are installed – I have an entry a short while ago describing how to use the keyboard to drive the installation of that without mouse), or use TS directly to the server and run Hyper-V Mnaager on the server (unless it is Server Core).

    Hope that helps.

    Thanks,

    John.

  21. Robr – I was thinking about this some more. With the caveat that I have never tried this, it may be possible to tunnel DCOM over HTTP using the RPC over HTTP proxy mechanism. When I get a chance, I’ll build up a lab environment to see whether it’s possible. There’s some interesting information here: http://msdn2.microsoft.com/en-us/library/ms809302.aspx

    You will still need port 2179 for the VMConnect video RDP connection though.

    Thanks,

    John.

  22. Josh – without the output from both sides, it’s impossible to diagnose anything here.

    Thanks,

    John.

  23. Dave – in which case, you should get the same result as creating a new user by simply runing "hvremote /add:yourusername" on the server. You still need to verify the client settings though (mmc and anondcom) as this is a workgroup. It *should* work then 🙂 I hope, anyway!

    Cheers,

    John.

  24. Hi Jonathan – Yes, I’ve seen reports of OneCare which (as I understand it – never have used it) has it’s own firewall which blocks part of remote management. Let me see if I can get hold of a copy to install and see what the problem is to find the solution. Stay tuned…

    Thanks,

    John.

  25. Dave – actually not quite true. You can /show the settings as an administrator from an unelevated command prompt on a Vista client, but not change the /mmc or /anondcom settings – you will hit permission denied.

    Similarly on the server, you cannot read the security permission for a WMI namespace unless you are elevated. I’m pretty sure this is related (for WMI) to UAC token filtering as described http://msdn.microsoft.com/en-us/library/aa826699(VS.85).aspx. However, in both client and server cases, this is really a question for those who developed the security model rather than for myself who’s trying to manipulate it 🙂

    So nutshell…. you still need to be elevated on both client and server to do anything useful.

    Thanks,

    John.

  26. Dave – I’m not sure is the simple answer – I’ll need to verify in my "test lab" which is all setup in my office at work (quicker than trying to set it up on my home servers) and run some network traces to work that out. Let me check tomorrow. If that is the case, as you seem to be saying, then I’ll add that to HVRemote to report on in the /show and to have the ability to change in the next version….

    That having been said, now you mention it, this does ring some distant bells. I’ll have to have a dig through my archives in the office. Out of interest, did you deliberately change any of the firewall rules on the server before running the tool. When I was doing my testing, I used a vanilla install and only ran the tool for the configuration, so I never tried it with other combinations.

    Thanks,

    John.

  27. Dave – I should have made it a bit clearer in the post (and I can make a check in the code if I can work out how). You must run the script as an administrator from an elevated command prompt. Without elevation, or running it as a standard user will give exactly that error. It should work when elevated by any account that is a local administrator.

    Thanks,

    John.

  28. Tore –  I got your email and have just replied.

    Thanks,

    John.

  29. Andrew – were you copying and pasting by any chance from above? I had exactly this error when copying and pasting when setting up another box. Have you tried typing it manually? (And no, I really can’t explain why)!

    Thanks,

    John.

  30. Jacques – what do you mean by terminal sessions. Do you mean you are using mstsc to logon to the hyper-v server and then running the Hyper-V management client locally on the server that is being targetted?

    Who is connecting? Standard users, administrators, both?

    What happens if you log on to the console of the Hyper-V machine and start Hyper-V Manager. Does it connect and work correctly? In the out of box configuration, as a local administrator, this should work with no configuration needed. For users to access, you need to update authorization manager as the access denied is an expected valid denial – you haven’t granted them access.

    Thanks,

    John.

  31. I’m not sure I understand your configuration: Are you saying that Windows Server 2008 is in the virtual machine under VMWare workstation? Have you enabled the Hyper-V role (which I don’t believe will succeed when the OS instance is running in a VM – never actually tried)?

    Thanks,

    John.

  32. Dave – regardling your ealier question about file and printer sharing, I can’t repro this. I have a Hyper-V Server (rather than 2008) and ran "netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=no", even restarted the server and connected from a vista box successfully. Is it possible you have other firewall software running on the server?

    Thanks,

    John.

  33. Dave – That’s really odd if disabling the firewall on the *SERVER* makes connections start working. Can you try turning it back on again and creating a seperate user account – I’m assuming you’re using "Administrator" here: On server net user <username> /add *, type the password. Do same on client and make sure the passwords are the same. Then run hvremote /add:username on server. If the client is workgroup, please also run hvremote /anondcom:grant. Also remember to run hvremote /mmc:enable on the client. Try that, when logged on as the new user. If that still fails, and also fails after a reboot, please can you re-post the hvremote /show on both the client AND the server.

    Thanks,

    John.

  34. Anonymous says:

    I am feeling lazy today – but thankfully my colleagues have been working hard 🙂 Mike Kolitz has done

  35. Anonymous says:

    So far, I’ve covered the following Hyper-V Remote Management scenarios: Workgroup: Vista client to remote

  36. Dave – I thought I *HAD* put this check into v0.3 for both client *AND* server. Are you sure you are running 0.3 on the server as well? If you are, please can you drop me an email using the option at the top of the blog.

    Thanks,

    John.

  37. re "I have Windows 2008 DataCenter Edition with the Hyper-V role installed. Do you have the standalone Hyper-V Server version that does not include additional roles (other than the Hyper…" question. Not sure I understand the question, but I’ve tried this on full and Hyper-V Server with no repro.

    Microsoft Hyper-V Server is not based on WinPE – it should have a black background with a default install, so not sure where green comes into this.

    Realistically, if you’re still having problems here, please run hvremote /show /debug:verbose on the server and the client and let’s see if there some other clue in there. Email link is at the top.

    Thanks,

    John.

  38. Roshan – if this is a workgroup environment, you still need to enable anonymous DCOM callbacks to the client machine (ie the Windows Server 2008 full machine in your configuration).

    Thanks,

    John.

  39. Jonh,

    thanks a lot for this post, it is very useful.

    But, in scenarios with Windows Live OneCare this solution doesn’t work due to OneCare firewall restrictions 🙁

    Only one solution turn off firewall at all… 🙁

  40. Scott – correct. I was being over cautious in saying reboot. Restarting the Hyper-V services which are dependent on winmgmt is sufficient – it was just easier to say "reboot".

    Obviously allowing anonymous callbacks has a security implication, but I don’t know the specifics. The closest information I could find published was at http://technet2.microsoft.com/windowsserver/en/library/4c9a2873-2010-4dbb-b9dd-6a7d1e275f0f1033.mspx?mfr=true.

    However, please note that you do not need to enable anonymous callbacks if both machines are in trusted domains. This is something I keep meaning to add to the walkthrough, but haven’t got  round to quite yet…..

    Thanks,

    John.

  41. Fabrice – it depends entirely on whether you are using "The Administrator" account, and whether you are are in a workgroup or domain. Generally, as "The administrator", you don’t need any configuration on the server. See part 5 of the series for a scenario where you do need to use cmdkey for Hyper-V remote management.

    Thanks,

    John.

  42. Kyle – there really shouldn’t be any need to turn off the firewall or UAC, so there’s probably something really simple making this not work in your case.

    Can you run hvremote /show on both the server and the vista box and send it to me using the email option at the top of my blog, or post it back as another comment.

    It would be helpful also if you can verify you have the RTM management tools installed on the Vista box, rather than pre-release. RTM is KB952627.

    If you can also include the output of ipconfig on both machines, and an attempt to ping by name the server from the client and the client from the server (just to verify there isn’t a DNS issue as well).

    Thanks,

    John.

  43. Mike P says:

    I use Windows One Care on my Vista PC. The settings above do not work as the Windows FW is turned off.

    Can you post the specific programs, ports etc… to accomplish the same thing as listed above.

    If I turn off the firewall on the Vista PC all works as advertised.

    Thanks is advance

  44. Hi John, thank you. I took me around 15 minutes to configure this remote management Hyper-V MMC console in a workgroup scenario. It works fine for me, but I had couple of problems with copy and paste of the netsh scripts in your post and enabled the rules manually using control panel. Kind regards, Ivan Versluis

  45. Tore4 says:

    I have a wierd problem.

    I got 2 computers (main and laptop) both running vista ultimate in workgroup mode.

    I have the same userpassword on both but only the main one can access the hyper-v server.

    The only difference i’ve found is that the main one uses x64 while the laptop uses Vista x86.

    Any idea why one should fail when the other works perfectly?

  46. Andrew Somervell says:

    Brand new Vista x64 install, i’m getting a "Group cannot be specified along with other identification conditions" error when I enter the "netsh advfirewall firewall set rule group=”Windows Management Instrumentation (WMI)” new enable=yes" command. Any clues?

    Regards,

    andrew (at) somervell dot com

  47. robr says:

    I was pointed here after trying to connect and getting the error "Cannot connect to the RPC service, make sure your RPC service is running".

    I followed all the instructions, with the exception of the firewalls steps as Windows Firewall is disabled on both computers.

    My client PC is here at the office behind a firewall.  I log into a domain here at work from the PC, so it’s not a workgroup config on the client side.

    The server is located remotely at a data center, no firewall in front of it, windows firewall disabled, and is a standalone server.  Because of this setup, I need to get this working so I can have mouse control of the remote VMs.

    Could my error be a firewall issue here at work related to RPC?  Thanks for all the work and well documented instructions.

  48. robr says:

    Thanks very much John, I’ll take a look at some of your other suggestions.  I’m running some Linux VMs, so I’m not certain integration services (in the case of SLES 10 which does have integration services installed, but I also have a Fedora VM) will solve all my mouse related issues.  I’ve installed them remotely without a mouse and just ssh in, but it would be nice to have access to the GNOME desktop.  

    So far, Hyper-V has been absolutely brilliant, but this ONE issue just makes everything they’ve done so right seem tarnished.  I have to imagine a great majority of people will be running production Hyper-V servers remotely.

  49. robr says:

    I’d absolutely love to see if you can get this working in your copious free time :).   I have previously played around with RPC over HTTP trying to get Outlook clients on the outside of our network to connect to the Exchange server behind our NATted firewall and failed miserably :).

  50. Michael Sainz says:

    John- I’m experiencing the same problem as Robr, but my topology is different. Instead of going through firewalls, mine is being routed by firewalls. I use ISA 2004 at two points to create a site to site VPN tunnel. Other MMC consoles seem to work, but this Hyper-V one does not. Again, it’s not going through NAT, but in a routed environment.

    I would like to be kept up to date also if you could.

    -Michael

    michaelsainz@(takemeout)sunsetpres.org

  51. Andrew Somervell says:

    Hahaha, you wouldnt believe how much I danced around when it worked John, you were right i had to type it in. Thank you.

    So when’s this all become less of a pain in the…. ? 😛

    A

  52. Rhynier says:

    Thank you very much! I would never have thought it would be so difficult to get Hyper-V Manager running with a remote connection. Two comments below.

    1) I installed the RC0 for Hyper-V and found both on the server and my Vista SP1 client that some new firewall rules had been added which looked very much like the WMI rules (same ports, etc.), but starting with "Hyper-V". I disabled the WMI firewall rules from your steps and everything still worked.

    2) The reason you can’t copy and paste the firewall rules from the blog post is that the open and closing quotes are not the same ASCII character as the one on the keyboard :). I’ve seen this many times using Word as it replaces the quote character with fancy open and close quotes that the command prompt does not recognize.

  53. mmcaulay says:

    I couldn’t get this to work until I explicitly added my user name to the appropriate steps in the server portion of this guide.  Even though that user was a member of the Administrators group on the server.  This was not enough to allow the connection. The user had to be added separately. At least on my setup. Running Server 2008 Full x64 with a client running Vista Business x86 SP1.

  54. greg says:

    The reason the shell commands don’t work if you cut and paste them is because the inverted commas – ie " " don’t come across right – they must be some kind of unicode character I imagine – if you paste the command into a command prompt box, then just go back and re-type the " over the existing ones, they’ll work.

  55. Darinfp says:

    What about if Hyper-V server and Client Vista are in different domains? Do I need to create the two indentical users in both domains?

  56. evan says:

    robr, I ran into this error message.  Not sure if my issue is the same but it ended up being that the user account I was connecting with through Hyper-v remote management tools had an expired password.  Odd error message but that is what it ended up being for me.

  57. Tom Ace says:

    I’m in!  Thanks so much.  There’s no way I would’ve figured any of that out.

  58. Thomas Goddard says:

    Hey it works!!!  I  hope this issue is somehow resolved in the next release.  Would be great if the setup did this for us!

  59. Christian says:

    YOU ROCK!!!

    thanks john, great walkthrough!!!

    /Chris

  60. uddhav regmi says:

    I did all the way as mentioned in this article.

    I have windows 2008 in vmware workstation installed as bare metal

    Vista Ultimate is also in same box, as virtual.

    I did all the way in vista as well as in 2008

    Now, while loading Hyper V manager and connecting, I get this error exactly

    Hyper-V Manager

    An error occured while attempting to connect to server 10.10.10.100, check that the virtual machine management service is running and that you are authorized to connect to server

  61. Oliver Schroeder says:

    Thank you, thank you, thank you!

    Regards from Germany.

    Oliver

  62. Gottfried Auer says:

    Thank you – from Austria

    Gottfried

  63. Roshan says:

    Thank you John for such a detailed post.

    After connecting to the core server from my W2k8 full server i see the following message under Virtual Machines "You might not have permission to perform this task".

    I have a windows 2008 full installation server and a core server. I did the following on the core server

    assign Hostname, IP, DNS, WINS.

    Enabled remote management and remote desktop

    applied patched and enabled hyper-V role

    Just to make things simpler I used the administrator username and gave the same password to both the machines.

    Then on W2k8 full and core servers I

    enabled firewall rules for WMI

    since I used the administrator account i didnot have to do any changes for DCOM etc.

    I rebooted the server and from the full installation server opened Hyper-V manager. I was able to connect to the core server and it displayed correctly under hyper-V manager.

    But on the middle pane under Virtual Machines i got the following messages in this order

    "Connecting to virtual machine management service" foilowed by

    "You might not have permission to perform this task"

    Please help

    Thanks

  64. NguyenIvan says:

    I also get "Cannot connect to RPC service on ‘servername’ Make sure RPC Service is running" error when trying to bring up Hyper-V manager.

    THe issue definitely has some thing to do with DNS server (If you point the client and Hyper-V server dns to dns server on active directory, the problem goes away). Will figure out a way to resolve NetBIOS and DNS right.

  65. ScottW says:

    Brilliant walkthrough, and quite dissapaointing that it actually needs to be this complicated!

    One observation and one question:

    Observation: You don’t need to restart the server after making the changes for it to work. Just restart the "Windows Management Instrumentation" service, which will in turn restart Hyper-V for you. Much easier than a whole reboot!

    Question: What security issues are there now that you have enabled anonymous logon remote wmi to the admin workstations?

  66. Jonathan Gray says:

    Great read and I can see this one is commented all over the web now..

    But I followed it and it did progress me further but I now get

    “Cannot connect to RPC service on ‘servername’

    I get this on my Vista SP1 Desktop and I have been through all stages. This is on domain (server/client).. I have all the firewall entries in but still if I disable firewall on the vista desktop  it works first time.. as soon as I enable firewall it kills it off with that message.

    I am using Onecare on Vista which is the only difference I can see.

  67. Jonathan Gray says:

    Hi John, For those with Onecare I cracked it for me, rather than cover it here I covered it with screenshots below

    http://itreallyisfun.spaces.live.com/

    This is NOT replacing Johns info but dealing specifically with Onecare..

  68. Jonathan Gray says:

    Hi again John,

    To update the previous blog link I sent which goes direct

    http://itreallyisfun.spaces.live.com/blog/cns!34EB0BCD9D9A2686!1355.entry

    That was they just get the article and not the blog entries totally unrelated.

  69. kim says:

    Brilliant! Thanks a lot! You saved my day!!!!!!!!!!! You’re the hero of the month!!

  70. JohnFF says:

    With ESXi, you just download and install the VI Client and it works. Why is this so HARD???

  71. paul says:

    JohnFF,  you are so correct.  The problem is that ESXi crashes when I try to install Windows Server 2008 and it’s doesn’t read my SATA card on my other computer.

  72. Robin says:

    Thanks great walk through worked perfectly.

  73. Tomohawk says:

    John, thank you very much, the steps are crystal and worked like a charm

  74. Joel says:

    Hello John:

    I’m on my 2nd try with your directions, no joy.  Workgroup setting, Hyper-V standalone (downloaded fresh today!) with a Vista client.

    All goes well until I go to use Hyper-V manager to connect. I get this error:

    >>>

    [Window Title]

    Hyper-V Manager

    [Main Instruction]

    An error occurred while attempting to connect to server "VIRTUALSERVER". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.

    [Content]

    The computer ‘VIRTUALSERVER’ could not be resolved. Make sure you typed the machine name correctly and that you have network access.

    [Close]

    >>>>

    I can RDP into the server fine.

    I can ping from the SERVER to the CLIENT

    I can NOT ping from the CLIENT to the SERVER (via name or IP).

    Any suggestions?

    Thanks in advance.

    joel*

  75. Dave says:

    John,

    I am receiving the same "exact" error as what "Joel" has stated (above).

    Error:

    "An error occurred while attempting to connect to server "VIRTUALSERVER". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server"

    If I disable the firewall on the Hyper-V server, then my Vista client connects remotely just fine (via Hyper-V Manager).

    BTW: The new "HVRemote" you uploaded last night is pretty slick!

    Here is a piped text file from HVRemote of my configuration on my Hyper-V server:

    Microsoft (R) Windows Script Host Version 5.7

    Copyright (C) Microsoft Corporation. All rights reserved.

    Hyper-V Remote Management Configuration & Checkup Utility

    John Howard, Microsoft Corporation. http://blogs.technet.com/jhoward

    Version 0.2 14th Nov 2008

    INFO: Computername is SVSS2K8PM1

    INFO: Computer is in workgroup WORKGROUP

    INFO: Assuming /mode:server as the role is installed

    INFO: This machine has the Hyper-V (v1) QFE installed (KB950050)

    ——————————————————————————-

    Discretionary Access for WMI Namespace rootcimv2

    ——————————————————————————-

    Required for Hyper-V remote mangement: Allow, EnabAct, RemEnab, InheritAce

    HVRemote also sets NoPropInheritAce and ValidInheritFlags

    BUILTINAdministrators    (S-1-5-32-544)

        Allow: Exec FullWrt PartWrt ProvWrt EnabAct RemEnab RdSec EdSec (393279)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYNETWORK SERVICE    (S-1-5-20)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYLOCAL SERVICE    (S-1-5-19)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYAuthenticated Users    (S-1-5-11)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    ——————————————————————————-

    Discretionary Access for WMI Namespace rootvirtualization

    ——————————————————————————-

    Required for Hyper-V remote mangement: Allow, EnabAct, RemEnab, InheritAce

    HVRemote also sets NoPropInheritAce and ValidInheritFlags

    BUILTINAdministrators    (S-1-5-32-544)

        Allow: Exec FullWrt PartWrt ProvWrt EnabAct RemEnab RdSec EdSec (393279)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYNETWORK SERVICE    (S-1-5-20)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYLOCAL SERVICE    (S-1-5-19)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYAuthenticated Users    (S-1-5-11)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    ——————————————————————————-

    Contents of Authorization Store Policy

    ——————————————————————————-

    Hyper-V Registry configuration:

    – Store: msxml://C:ProgramDataMicrosoftWindowsHyper-VInitialStore.xml

    – Service Application: Hyper-V services

    Application Name: Hyper-V services

    Operation Count: 33

       100 – Read Service Configuration

       105 – Reconfigure Service

       200 – Create Virtual Switch

       205 – Delete Virtual Switch

       210 – Create Virtual Switch Port

       215 – Delete Virtual Switch Port

       220 – Connect Virtual Switch Port

       225 – Disconnect Virtual Switch Port

       230 – Create Internal Ethernet Port

       235 – Delete Internal Ethernet Port

       240 – Bind External Ethernet Port

       245 – Unbind External Ethernet Port

       250 – Change VLAN Configuration on Port

       255 – Modify Switch Settings

       260 – Modify Switch Port Settings

       265 – View Switches

       270 – View Switch Ports

       275 – View External Ethernet Ports

       280 – View Internal Ethernet Ports

       285 – View VLAN Settings

       290 – View LAN Endpoints

       295 – View Virtual Switch Management Service

       300 – Create Virtual Machine

       305 – Delete Virtual Machine

       310 – Change Virtual Machine Authorization Scope

       315 – Start Virtual Machine

       320 – Stop Virtual Machine

       325 – Pause and Restart Virtual Machine

       330 – Reconfigure Virtual Machine

       335 – View Virtual Machine Configuration

       340 – Allow Input to Virtual Machine

       345 – Allow Output from Virtual Machine

       350 – Modify Internal Ethernet Port

    1 role assignment(s) were located

    Role Assignment ‘Administrator’ (Targetted Role Assignment)

      – All Hyper-V operations are selected

      – There are 1 member(s) for this role assignment

      – BUILTINAdministrators (S-1-5-32-544)

    ——————————————————————————-

    Contents of Group Distributed COM Users

    ——————————————————————————-

    There are no members in Distributed COM Users

    ——————————————————————————-

    Firewall Settings for Hyper-V

    ——————————————————————————-

    Public Firewall Profile is active

      Enabled:  Hyper-V (SPL-TCP-In)

      Enabled:  Hyper-V (RPC)

      Enabled:  Hyper-V (RPC-EPMAP)

      Enabled:  Hyper-V – WMI (Async-In)

      Enabled:  Hyper-V – WMI (TCP-Out)

      Enabled:  Hyper-V – WMI (TCP-In)

      Enabled:  Hyper-V – WMI (DCOM-In)

    ——————————————————————————-

    Firewall Settings for Windows Management Instrumentation (WMI)

    ——————————————————————————-

    Public Firewall Profile is active

      Enabled:  Windows Management Instrumentation (ASync-In)

      Enabled:  Windows Management Instrumentation (WMI-Out)

      Enabled:  Windows Management Instrumentation (WMI-In)

      Enabled:  Windows Management Instrumentation (DCOM-In)

    Note: Above firewall settings are not required for Hyper-V Remote Management

    Thanks, Dave

  76. Dave says:

    John,

    Before I setup a new user and try it, I wanted to confirm that ‘yes" I am using the Administreator account on both the client and server and am using the same password on both platforms.

    Also, (to be more accurate in my setup), I’m actually using the Administrator group, instead of the built-in Administrator account.

    Also, both platforms are in a workgroup called "WORKGROUP".

    Thanks, Dave

  77. Dave says:

    John,

    Disable "File and Printer Sharing" on your Hyper-V server (via Windows Firewall – Exceptions) and then try using your Vista client to connect to your Hyper-V server.

    Do you get the following error after doing this?

    Error:

    "An error occurred while attempting to connect to server "VIRTUALSERVER". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server"

    If you do receive this error, then I have a question that you may be able to answer:

    Why does Hyper-V Manager (on the Vista client) require the enabling of "File and Printer Sharing" on the Hyper-V server?

    Thanks, Dave

  78. Dave says:

    John,

    I also noticed the folowing:

    HVRemote commands do not work on the Hyper-V server unless you are the "Built-in" Administrator. If you use another "Administrator" account or "User" account, you will receive a "Failed to call GetSecurity Descriptor" and will stop at the "Cimv2 Namespace".

    All HVRemote commands work fine on the Vista client.

    Thanks, Dave

  79. Dave says:

    Hi John,

    I have Windows 2008 DataCenter Edition with the Hyper-V role installed. Do you have the standalone Hyper-V Server version that does not include additional roles (other than the Hyper-V role)? Does it boot up to a blue configuration box? on top of a WinPE (green background)?

    BTW: I haven’t changed any of the Windows Firewall settings.

    Thanks, Dave

  80. Dave says:

    How come HVRemote operates in Windows Vista without having to elevate the command prompt? HVRemote runs as a standard "User" or "Administrator" without have to run in an elevated command prompt.

    Does the settings (ex: "Cimv2 Namespace, etc") that HVRemote needs to configure require elevated privileges to set them up properly?

    Thanks, Dave

  81. zoltan says:

    Hello

    we tested it brutally.)Turned off the fireall also on the vista and also on the server.Nothing, the same rpc error.As I plug back the vista to the locla network, everything works fine.So?Any idea?

    I can ping the server by name from client and back.

    But I can not nslookup it, but I really dont understand, whí does it needed?

  82. Kyle says:

    I’m completely stumped… I have three systems, one Hyper-V server 2k8 (server core install w/ hyper-v role), a windows server 2008 standard edition install and the last being my Vista SP1 workstation.

    I am trying to connect to the Hyper-V role on the server-core install via remote management on my Vista box and I am getting the authorization policy error that has been posted a million times. I have ran hvremote on both my client machine and the remote server-core instance.

    It is important to note that I can connect to the hyper-v role on the server-core instance from my win2k8 standard edition box that also has the hyper-v role installed and configured. So I can remotely manage the hyper-v role on the server-core system from the 2k8 server but not my vista box.

    I do not have the firewall enabled on the server-core or my vista box. All systems are in the same domain and are in the same subnet with no ACL’s between them. The fact that I can remotely manage it from another server instance but I can’t from my vista box tells me that it is a problem with my workstation’s security. Also important to note that I cannot remotely connect to the hyper-v role on the windows server 2008 standard box either.

    I have done everything multiple times and followed instructions to the letter. I have also gone out and turned off UAC on my vista box. Still nothing works…

    Any ideas?

  83. The_Prisoner says:

    When copying and pasting

    netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes

    from the web page it uses the "wrong sort" of double-quotes. If you copy into Notepad, change the quotes and then copy/paste from Notepad it will work.

  84. Dave says:

    Hi John,

    I run the following command on my Hyper-V server:

    cscript hvremote.wsf /mode:server /show

    …and receive the following error:

    ***** Failed to call GetSecurityDescriptor

    ***** Giving up as not able to get the security descriptor for the cimv2 namespace

    This error is happening because I am not running the hvremote.wsf script in elevated mode.

    Could you put some error checking in the code when a user is not running a elevated command prompt (like you did with the client side).

    The client-side message that you created in v0.3 was something like this:

    “All client operations which change the configuration must be run from an elevated command prompt.”

    Thanks, Dave

  85. Dave says:

    Hi John,

    I’m tired tonight.

    I had v0.2 on this server. I thought I had copied v0.3 on each of my Hyper-V hosts. Forgot one…I guess :+)

    Thanks, Dave

  86. Dave says:

    What’s this message at the bottom of the /show results:

    INFO: Are running the latest version

    Is the script checking it’s version?

    Thanks, Dave

  87. brett says:

    I think it’s pathetic it’s this difficult to admin a Hyperv box.  Wasn’t there ever a "Man, we can’t release this to the public" statement made at MS head quarters?  I kicking myself for deciding to go this route–should have went with VMWare.

  88. jacques says:

    hi wonder if everyone can help me, i have this same error message but only it is on Server 2008 standard edition with the hyper-v role installed, but we use terminal sessions to connect to this server! please if anyone can help me!!

    thank you very much!

  89. rloureiro says:

    John,

    Excellent guide, it worked perfectly for me.

    Thanks!

    Rafael

  90. Fabrice says:

    Maybe one step is missing in the post (which is handled by the script), at least for Microsoft Hyper-V Server 2008.

    For this release, no configuration seems needed on server side, all setup has to be done on Vista.

    The missing step could be the cmdkey command is case of a workgroup scenario. On Vista : cmdkey /add:<server-name> /user:<admin-user-on-server> /pass:<admin-user-password>

  91. Evandro Reis says:

    John, first of all congratulations for the great HVRemote tool. It rocks. Also, your articles are of great value. Thank your for putting them together. I have a weird situation here. I have two machines running on the same WORKGROUP and inside the same network segment (same IP class/net mask for both – 192.168.1.25 server e 192.168.1.7 client). I am able to connect to the server and change its configurations via Remote Management running on Vista SP1. But in the Virtual Machines group I get the message "RPC Server unavailable". And when I try to create new vms, HVRM creates de VHD file but crashes in the middle with the error above. In summary, I can change Hyper-V Server configuration (like default folders and virtual networks), but when I try to manage VMs (create, for instance) I get the RPC error.

    Any thoughts?

    Thanks again.

  92. Evandro Reis says:

    One additional comment: after getting the "RPC unavailable" error and clicking on "Refresh" Hyper-V Manager sits idle with the message: "Loading virtual machines…" and nothing happens. I am running Hyper-V as a role of a Windows 2008 Server Core.

  93. Eric says:

    Thanks John for taking the time to put this together!  I didn’t use your HVRemote because I wanted to see what was involved to configure Hyper-V Manager.

    You did an excellent job!  Thanks Again!

  94. dbinfl says:

    Wow!  I just followed these instructions, and indeed got this working.  So, hats off to you for taking the time to document and post this; I sure appreciate it.

    Now, as to MS, maybe they could make this a little harder, but why bother since they’ve pretty much aced this in the PITA department (including a reboot — wouldn’t be complete without a reboot).

    Thanks for this and all the other helpful posts I’ve found here.

    cheers

  95. Larry says:

    John, you are definately a legend!!  We need guys like you around. 🙂

    Cheers

  96. Greg L says:

    Thanks for such detailed work. I’ve followed the examples to a "T" but this problem persists for me: Once I’ve connected to the Hyper-V server from the client (Vista Ent 64, SP2), I get an  RPC error. After refreshing the detail pane simply says "loading virtual machines" but nothing ever comes up. I can manage the server settings, and have even created a VM, but I cannot see them. I disabled the firewall on both server and client and the same thing happens. Any ideas? Thanks!

  97. Greg L says:

    Ok, at the last moment, I found the source of my problem. My the network adapter in my Vista client, running as a VM in Sun VirtualBox, was configured with NAT. Once I switched it to bridged, all worked fine. Thanks, sorry for the false alarm.

  98. jpavly says:

    Thanks a lot, that totally worked!

  99. Josh Franklin says:

    so strange, in my office, with the system set up behing a smoothwall firewall, I am able to get my laptop talking with my hpyer-v server.

    I bring the system home, hook it up identically, and it gives me an

    Cannot connect ot the RPC Services on computer ‘VVS1’ please make sure your RPC serve is running.

    I use hosts files as there is not yet a DNS set up on the network and can NSlookup from server to client without a problem. From client to server it was erroring out, but once I added the domain suffix to the TCP connection it started working without an issue.

    INFO: Computername is VVS1

    INFO: Computer is in workgroup VECTOR

    INFO: Current user is VVS1joshf

    INFO: Assuming /mode:server as the role is installed

    INFO: Build 7600.16385.amd64fre.win7_rtm.090713-1255

    INFO: Detected Windows 7/Windows Server 2008 R2 OS

    ——————————————————————————-

    DACL for WMI Namespace rootcimv2

    Required for Hyper-V remote mangement: Allow, EnabAct, RemEnab, InheritAce

    HVRemote also sets NoPropInheritAce and ValidInheritFlags

    ——————————————————————————-

       (S-1-5-21-1762662943-3239234248-1774531117-1001)

        Allow: EnabAct RemEnab (33)

        Flags: InheritAce NoPropInheritAce ValidInheritFlags  (6)

       (S-1-5-21-1762662943-3239234248-1774531117-1002)

        Allow: EnabAct RemEnab (33)

        Flags: InheritAce NoPropInheritAce ValidInheritFlags  (6)

    VVS1joshf    (S-1-5-21-1762662943-3239234248-1774531117-1003)

        Allow: EnabAct RemEnab (33)

        Flags: InheritAce NoPropInheritAce ValidInheritFlags  (6)

    BUILTINAdministrators    (S-1-5-32-544)

        Allow: Exec FullWrt PartWrt ProvWrt EnabAct RemEnab RdSec EdSec (393279)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYNETWORK SERVICE    (S-1-5-20)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYLOCAL SERVICE    (S-1-5-19)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYAuthenticated Users    (S-1-5-11)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    ——————————————————————————-

    DACL for WMI Namespace rootvirtualization

    Required for Hyper-V remote mangement: Allow, EnabAct, RemEnab, InheritAce

    HVRemote also sets NoPropInheritAce and ValidInheritFlags

    ——————————————————————————-

       (S-1-5-21-1762662943-3239234248-1774531117-1001)

        Allow: EnabAct RemEnab (33)

        Flags: InheritAce NoPropInheritAce ValidInheritFlags  (6)

       (S-1-5-21-1762662943-3239234248-1774531117-1002)

        Allow: EnabAct RemEnab (33)

        Flags: InheritAce NoPropInheritAce ValidInheritFlags  (6)

    VVS1joshf    (S-1-5-21-1762662943-3239234248-1774531117-1003)

        Allow: EnabAct RemEnab (33)

        Flags: InheritAce NoPropInheritAce ValidInheritFlags  (6)

    BUILTINAdministrators    (S-1-5-32-544)

        Allow: Exec FullWrt PartWrt ProvWrt EnabAct RemEnab RdSec EdSec (393279)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYNETWORK SERVICE    (S-1-5-20)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYLOCAL SERVICE    (S-1-5-19)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    NT AUTHORITYAuthenticated Users    (S-1-5-11)

        Allow: Exec ProvWrt EnabAct (19)

        Flags: InheritAce InheritedAce ValidInheritFlags  (18)

    ——————————————————————————-

    Contents of Authorization Store Policy

    ——————————————————————————-

    Hyper-V Registry configuration:

    – Store: msxml://C:ProgramDataMicrosoftWindowsHyper-VInitialStore.xml

    – Service Application: Hyper-V services

    Application Name: Hyper-V services

    Operation Count: 34

       100 – Read Service Configuration

       105 – Reconfigure Service

       200 – Create Virtual Switch

       205 – Delete Virtual Switch

       210 – Create Virtual Switch Port

       215 – Delete Virtual Switch Port

       220 – Connect Virtual Switch Port

       225 – Disconnect Virtual Switch Port

       230 – Create Internal Ethernet Port

       235 – Delete Internal Ethernet Port

       240 – Bind External Ethernet Port

       245 – Unbind External Ethernet Port

       250 – Change VLAN Configuration on Port

       255 – Modify Switch Settings

       260 – Modify Switch Port Settings

       265 – View Switches

       270 – View Switch Ports

       275 – View External Ethernet Ports

       280 – View Internal Ethernet Ports

       285 – View VLAN Settings

       290 – View LAN Endpoints

       295 – View Virtual Switch Management Service

       300 – Create Virtual Machine

       305 – Delete Virtual Machine

       310 – Change Virtual Machine Authorization Scope

       315 – Start Virtual Machine

       320 – Stop Virtual Machine

       325 – Pause and Restart Virtual Machine

       330 – Reconfigure Virtual Machine

       335 – View Virtual Machine Configuration

       340 – Allow Input to Virtual Machine

       345 – Allow Output from Virtual Machine

       350 – Modify Internal Ethernet Port

       355 – Allow Virtual Machine Snapshot

    1 role assignment(s) were located

    Role Assignment ‘Administrator’ (Targetted Role Assignment)

      – All Hyper-V operations are selected

      – There are 4 member(s) for this role assignment

      – BUILTINAdministrators (S-1-5-32-544)

      – S-1-5-21-1762662943-3239234248-1774531117-1001 (S-1-5-21-1762662943-3239234

    248-1774531117-1001)

      – S-1-5-21-1762662943-3239234248-1774531117-1002 (S-1-5-21-1762662943-3239234

    248-1774531117-1002)

      – VVS1joshf (S-1-5-21-1762662943-3239234248-1774531117-1003)

    ——————————————————————————-

    Contents of Group Distributed COM Users

    ——————————————————————————-

    1 member(s) are in Distributed COM Users

      – VVS1joshf

    ——————————————————————————-

    DACL for COM Security Launch and Activation Permissions

    ——————————————————————————-

    BUILTINAdministrators    (S-1-5-32-544)

        Allow: LocalLaunch RemoteLaunch LocalActivation RemoteActivation (31)

    Everyone    (S-1-1-0)

        Allow: LocalLaunch LocalActivation (11)

    BUILTINDistributed COM Users    (S-1-5-32-562)

        Allow: LocalLaunch RemoteLaunch LocalActivation RemoteActivation (31)

    BUILTINPerformance Log Users    (S-1-5-32-559)

        Allow: LocalLaunch RemoteLaunch LocalActivation RemoteActivation (31)

    ——————————————————————————-

    Firewall Settings for Hyper-V

    ——————————————————————————-

    Public Firewall Profile is active

      Enabled:  Hyper-V (REMOTE_DESKTOP_TCP_IN)

      Enabled:  Hyper-V (MIG-TCP-In)

      Enabled:  Hyper-V (RPC)

      Enabled:  Hyper-V (RPC-EPMAP)

      Enabled:  Hyper-V – WMI (Async-In)

      Enabled:  Hyper-V – WMI (TCP-Out)

      Enabled:  Hyper-V – WMI (TCP-In)

      Enabled:  Hyper-V – WMI (DCOM-In)

    ——————————————————————————-

    Firewall Settings for Windows Management Instrumentation (WMI)

    ——————————————————————————-

    Public Firewall Profile is active

      Enabled:  Windows Management Instrumentation (ASync-In)

      Enabled:  Windows Management Instrumentation (WMI-Out)

      Enabled:  Windows Management Instrumentation (WMI-In)

      Enabled:  Windows Management Instrumentation (DCOM-In)

    Note: Above firewall settings are not required for Hyper-V Remote Management

    ——————————————————————————-

    IP Configuration

    ——————————————————————————-

    Windows IP Configuration

      Host Name . . . . . . . . . . . . : VVS1

      Primary Dns Suffix  . . . . . . . :

      Node Type . . . . . . . . . . . . : Hybrid

      IP Routing Enabled. . . . . . . . : No

      WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 3:

      Connection-specific DNS Suffix  . :

      Description . . . . . . . . . . . : Vector.int

      Physical Address. . . . . . . . . : 90-E6-BA-4E-3D-A7

      DHCP Enabled. . . . . . . . . . . : Yes

      Autoconfiguration Enabled . . . . : Yes

      Link-local IPv6 Address . . . . . : fe80::f104:d946:5537:b26e%211(Preferred)

      IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)

      Subnet Mask . . . . . . . . . . . : 255.255.0.0

      Lease Obtained. . . . . . . . . . : Friday, November 13, 2009 8:31:12 PM

      Lease Expires . . . . . . . . . . : Friday, November 13, 2009 10:31:12 PM

      Default Gateway . . . . . . . . . : 192.168.0.254

      DHCP Server . . . . . . . . . . . : 192.168.0.254

      DHCPv6 IAID . . . . . . . . . . . : -745478470

      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-8D-F2-CC-90-E6-BA-4E-3D-A7

      DNS Servers . . . . . . . . . . . : 192.168.0.254

                                          192.168.0.1

      NetBIOS over Tcpip. . . . . . . . : Enabled

    ——————————————————————————-

    Testing connectivity to client: n120053 (2 tests in total)

    ——————————————————————————-

    Test 1

    ——

       This test verifies your DNS infrastructure. For Hyper-V remote management,

       VVS1 must be able to resolve the IP address of n120053.

       If you do not have a DNS infrastructure, test 1 may legitimately fail.

       However, you will have to edit windowssystem32driversetchosts on this

       computer to add an entry for n120053.

       If you have a DNS infrastructure and test 1 fails, this is a strong

       indication that Hyper-V remote management will not work.

           a) Verify that n120053 is the correct client name

           b) On VVS1, run ipconfig /flushdns

           c) On n120053, run ipconfig /registerDNS

       If you have a DNS infrastructure and test 1 succeeds, verify the IPv4

       address returned matches the IPv4 address of n120053. This can be

       found by running ipconfig /all on n120053.

       If you find the incorrect IP address is returned, follow steps a) to c)

       described above, plus step d) below.

           d) Check the hosts file on VVS1 for incorrect entries.

    ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

    Server:  HADRIANS

    Address:  192.168.0.254

    Name:    n120053

    Address:  192.168.0.200

    ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

    Test 2

    ——

       This test attempts to ping n120053. Like test 1, the aim is to

       verify name resolution. Examine the output to ensure the IP address is

       that of n120053.

       If an incorrect IP address is shown, follow resolution steps a)

       through d) listed above.

       A ping timeout is OK. It is likely the firewall on the client machine

       is blocking inbound pings. No action need be taken.

       If the ping cannot locate n120053, you may need to add an entry

       in windowssystem32driversetc (described above). If you have a DNS

       infrastructure, follow steps a) through c).

       This test may take a second or two…

    ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

    Pinging n120053 [192.168.0.200] with 32 bytes of data:

    Reply from 192.168.0.200: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.0.200:

       Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

       Minimum = 0ms, Maximum = 0ms, Average = 0ms

    ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

    INFO: Are running the latest version

    I’m now scratching my head. . .

  100. Albecool says:

    Thank you, Thank you, Thank you. Works like a charm.

  101. vsecgod says:

    omg this was a lifesaver, could not figure out what was causing this error!

  102. Ronnie says:

    Thanks