Quantcast
Channel: Hyper-V Remote Management Configuration Utility
Viewing all 37 articles
Browse latest View live
↧

NEW POST: RPC Server Unavailable

August 20, 2012, 4:18 pm
$
0
0
I have a windows 7 client, and several windows 2008 R2 hosts running Hyper-v. I used to be able to remote manage those hosts from the windows 7 Client, however, some servers suddenly lost the connection. At the beginning, I saw the RPC server unavailable error on one host, after a few days, there's another one. Now, I have 5 servers having the same error. I use the same configuration for all those servers, there's nothing changed recently. I am not sure why this happens.

I had tried disable firewall on both client and hosts, restarted winmgmt and vmms

I tried to use hvremote.swf script to check the connectives between client and hosts, I got the following error when I test from client to host:

*7: - Async notification query to root\virtualization WMI namespace
FAIL - Notification query failed The RPC server is unavailable.*


Windows 7 Client IP: 192.168.10.244
One Windows 2008 r2 host IP : 192.168.10.4


From windows 7 client to windows 2008 r2 host
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\hyperv>cscript hvremote.wsf /show /target:windows2008r2host
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.


Hyper-V Remote Management Configuration & Checkup Utility
John Howard, Hyper-V Team, Microsoft Corporation.
http://blogs.technet.com/jhoward
Version 0.7 7th August 2009

INFO: Computername is windows7client
INFO: Computer is in workgroup WORKGROUP
INFO: Current user is windows7client\clientuser
INFO: Assuming /mode:client as the Hyper-V role is not installed
INFO: Build 7600.17017.amd64fre.win7_gdr.120503-2030
INFO: Detected Windows 7/Windows Server 2008 R2 OS
INFO: This appears to be a server SKU

-------------------------------------------------------------------------------
DACL for COM Security Access Permissions
-------------------------------------------------------------------------------

\Everyone (S-1-1-0)
Allow: LocalLaunch RemoteLaunch (7)

BUILTIN\Performance Log Users (S-1-5-32-559)
Allow: LocalLaunch RemoteLaunch (7)

BUILTIN\Distributed COM Users (S-1-5-32-562)
Allow: LocalLaunch RemoteLaunch (7)

NT AUTHORITY\ANONYMOUS LOGON (S-1-5-7)
Allow: LocalLaunch RemoteLaunch (7)

-------------------------------------------------------------------------------
ANONYMOUS LOGON Machine DCOM Access
-------------------------------------------------------------------------------

ANONYMOUS LOGON has remote access

-------------------------------------------------------------------------------
Firewall Settings for Hyper-V Management Clients
-------------------------------------------------------------------------------

Private Firewall Profile is active
Public Firewall Profile is active

Enabled: Hyper-V Management Clients - WMI (Async-In)
Enabled: Hyper-V Management Clients - WMI (TCP-Out)
Enabled: Hyper-V Management Clients - WMI (TCP-In)
Enabled: Hyper-V Management Clients - WMI (DCOM-In)

-------------------------------------------------------------------------------
Windows Firewall exception rule(s) for mmc.exe
-------------------------------------------------------------------------------

Private Firewall Profile is active
Public Firewall Profile is active

Enabled: Microsoft Management Console (UDP)
Enabled: Microsoft Management Console (TCP)
Enabled: Microsoft Management Console (UDP)
Enabled: Microsoft Management Console (TCP)

-------------------------------------------------------------------------------
IP Configuration
-------------------------------------------------------------------------------


Windows IP Configuration

Host Name . . . . . . . . . . . . : windows7client
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
Physical Address. . . . . . . . . : 00-15-5D-63-DD-51
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6153:af24:5d7d:2670%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.10.244(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.254
DHCPv6 IAID . . . . . . . . . . . : 234886493
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-D0-0B-1E-00-15-5D-63-DD-51

DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{CF85E17D-436D-498C-823D-1BE7CEE8ED2D}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{794716C4-28E0-452F-ABEE-CF9798810420}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


-------------------------------------------------------------------------------
Stored Credentials
-------------------------------------------------------------------------------

Currently stored credentials:

Target: Domain:target=TERMSRV/192.168.10.4
Type: Domain Password
User: administrator
Local machine persistence

-------------------------------------------------------------------------------
Testing connectivity to server:windows2008r2host
-------------------------------------------------------------------------------

1: - nslookup for DNS verification.

Note that failure is OK if you don't have a DNS infrastructure

~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Server: google-public-dns-a.google.com
Address: 8.8.8.8


      • google-public-dns-a.google.com can't find windows2008r2host: Non-existent domain

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

2: - ping attempt (ping -4 -n -1 windows2008r2host)

Note the ping may timeout - that is OK. However, if you get an
error that windows2008r2host could not be found, you need to fix DNS
or add an entry to the hosts file. Test 3 will fail and provide more
guidance.

This may take a second or two...

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

Pinging windows2008r2host 192.168.10.4 with 32 bytes of data:
Reply from 192.168.10.4: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.10.4:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

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


3: - Connect to root\cimv2 WMI namespace
PASS - Connection established

4: - Connect to root\virtualization WMI namespace
PASS - Connection established

5: - Simple query to root\cimv2 WMI namespace
PASS - Simple query succeeded

6: - Simple query to root\virtualization WMI namespace
PASS - Simple query succeeded
- 9 computer system(s) located

7: - Async notification query to root\virtualization WMI namespace
FAIL - Notification query failed The RPC server is unavailable.

The most likely cause of this failure is that you have not restarted the
server after having added a user account for the first time. Either restart
the server, or restart the Windows Management Instrumentation service
and all dependent services on the server before retrying.

Alternately, there is a DNS issue and the server cannot locate this
machine. You should check this by performing a ping test from the
server to this machine verifying that the IP address the server
is trying to reach matches the IPv4 address shown in the output above.
Note that it does not matter if the ping succeeds or fails, just that
the IP address is correct.

Run on windows2008r2host: ping -4 windows7client

Note that if you do not have DNS in your infrastructure, you can edit
the \windows\system32\drivers\etc\hosts file on the server to add an
entry for windows7client

If you do have DNS in your infrastructure, you may want to try flushing
the DNS cache on the server, and re-registering against DNS on the client

Run on windows2008r2host: ipconfig /flushdns
Run on windows7client: ipconfig /registerdns

If you are connected over a VPN, see http://tinyurl.com/o4lsbw for
information about another likely cause.



INFO: Are running the latest version

-------------------------------------------------------------------------------
1 warning(s) or error(s) were found in the configuration. Review the
detailed output above to determine whether you need to take further action.
Summary is below.

1: Cannot perform async query against root\virtualization
Please see resolution steps above.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

From windows 2008 r2 host to windows 7 client

C:\hyperv>cscript hvremote.wsf /show /target:windows7client
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.


Hyper-V Remote Management Configuration & Checkup U
↧
Search

NEW POST: Anybody had luck with this on Windows 8?

August 25, 2012, 1:38 pm
$
0
0
Hi,

I have two Windows 8 machines in a workgroup and have been having trouble trying to connect to Hyper-V from one machine to the other. They both have the Hyper-V feature enabled, which results in the 'client' (i.e. my laptop) being picked up as a server so I disabled Hyper-V on it when running the scripts then re-enabled afterwards. Still unable to connect, has anybody else had any success with this?
↧
↧

NEW POST: Anybody had luck with this on Windows 8?

September 1, 2012, 4:16 am
$
0
0
Hi there,

I am in exactly the same scenario and getting the same results. Spent an hour trying various things to no avail. Would seem that it isn't possible to connect between Windows 8 machines.
↧

NEW POST: Server 2012 Core Hyper V

September 6, 2012, 8:41 am
$
0
0
Hi Ive just tried to run the script in Server 2012 Core Hyper-V RTM freshly from msdn and I keep getting an error message unknown OS type, so far the initial installation for hyper v 2012 seemed easy enough with remote management enabled by default but for the life of me I cant access it via computer management, which is highly frustrating. Any Ideas folks
↧

NEW POST: Support for Windows 8 Accounts

September 6, 2012, 1:31 pm
$
0
0
I successfully used HVRemote to connect from Windows 8 Pro to Windows Server 2012. I found a few caveats however, and am left with one question.

1) Since my Win 8 machine had hyper-v features installed, most client side commands had to specify /mode:client.
2) Probably not a common issue, but my Norton 360 firewall would block async notifications. Once I added a rule to allow all traffic on the local subnet, all was well. (This is for a home network. Security is not a major issue.)
3) I had to convert my account to a local account as opposed to being paired with a Microsoft account.

This is my question. When I connect from a Microsoft account, it connects to the hyper-v server as the email address. However, there doesn't seem to be a way to create a matching user on the server. You can't create a user name with an @ in it. Note that both of these machines are workgroup machines. For now, I've converted to a local account and everything works, but I'd like to upgrade this.

Thanks for any suggestions.
↧
↧

UPDATED WIKI: Home

September 10, 2012, 9:30 am
$
0
0

About

    • HVRemote reduces the manual configuration steps needed for Hyper-V Remote Management down to a few simple commands.
    • HVRemote can diagnose common configuration errors.
    • HVRemote is locale neutral, although output is in English only.
    • HVRemote can configure all combinations of workgroup and domain joined clients and servers.
If you find HVRemote useful, please drop me an email through my blog, or add a comment to this post :)

10-second guide


Configuration Where Purpose Commands
Client and Server both workgroup Server Create a local account (eg "john") Use net user /? or Computer Management
Server Grant the user access cscript hvremote.wsf /add:accountname ***
Client Allow Anonymous Logon remote DCOM access cscript hvremote.wsf /anondcom:grant
Client Logon with matching local account. Ctrl+Alt+Del :)
Client If passwords do not match cmdkey /add:servername /user:servername\account /pass
Client Set firewall exception cscript hvremote.wsf /mmc:enable
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername
-------------------------
Client workgroup, Server domain Server Grant domain account access cscript hvremote.wsf /add:domain\account ***
Client Allow Anonymous Logon remote DCOM access cscript hvremote.wsf /anondcom:grant
Client Set credentials for domain account cmdkey /add:servername /user:domain\account /pass
Client Set firewall exception cscript hvremote.wsf /mmc:enable
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername
-------------------------
Client domain, Server workgroup Server Create a local account (eg "john") Use net user /? or Computer Management
Server Grant the user access cscript hvremote.wsf /add:accountname ***
Client Allow Anonymous Logon remote DCOM access cscript hvremote.wsf /anondcom:grant
Client Set credentials for local account Use cmdkey /add:servername /user:servername\accountname /pass
Client Set firewall exception cscript hvremote.wsf /mmc:enable
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername
-------------------------
Client and Server both domain Server Grant the non-admin user access cscript hvremote.wsf /add:domain\account ***
Client Set firewall exception cscript hvremote.wsf /mmc:enable
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername


*** Restart server if this is the first time an account has been added. Not required for Windows 8 Client Hyper-V or Windows Server 2012

Supported Servers:

    • Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), Core & Full installations
    • Windows Server 2008 SP2, Core & Full installations
    • Microsoft Hyper-V Server 2008 SP1 (already contains Hyper-V RTM update)
    • Microsoft Hyper-V Server 2008 SP2
    • Windows Server 2008 R2, Core & Full installations
    • Windows Server 2008 R2 SP1, Core & Full installations
    • Microsoft Hyper-V Server 2008 R2
    • Microsoft Hyper-V Server 2008 R2 SP1
    • Windows Server 2012 Core & Full installations (Version 1.x or later)
    • Microsoft Hyper-V Server 2012 (Version 1.x or later)
    • Windows 8 Client Hyper-V (Version 1.x or later)

Supported Clients:

    • Windows Vista Business, Enterprise and Ultimate x86 & x64, SP1 and SP2, with KB952627 applied
    • Windows 7 Professional, Enterprise and Ultimate x86 & x64 with RSAT installed and Hyper-V tools feature enabled
    • Windows 8 (Version 1.x or later)
    • Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), x86 and x64
    • Windows Server 2008 SP2 x86 and x64
    • Windows Server 2008 R2
    • Windows Server 2008 R2 SP1
    • Windows Server 2012 (Version 1.x or later)

Command summary


Please see the documentation for more information - below is not a complete list of all command line options, just the most commonly needed commands. Commands should be run from an elevated command prompt.

If the default scripting engine is already CScript, you can run each command exactly as shown in the table. To change the default scripting engine to cscript, run cscript //h:cscript. Alternately, launch each command using the longer format: cscript hvremote.wsf command

Applicability Operation Command
Server Grant account access hvremote /add:domain\account (Domain) or hvremote /add:account (Workgroup)
Server Revoke account access hvremote /add:domain\account (Domain) or hvremote /add:account (Workgroup)
Both Display settings hvremote /show
Client Display settings and test server connectivity hvremote /show /target:servercomputername
Server Display settings and test client connectivity hvremote /show /target:clientcomputername
Both Display help hvremote /?
Client Permit ANONYMOUS LOGON remote DCOM access hvremote /AnonDCOM:grant
Client Deny ANONYMOUS LOGON remote DCOM access hvremote /AnonDCOM:revoke

Installation


Save HVRemote.wsf from the Downloads tab to a directory on the local disk (eg c:\HVRemote)

Disclaimer


Although I work for Microsoft and am a Program Manager in the Hyper-V team, I must point you to the disclaimer on my blog, the disclaimer in the documentation, and the license conditions on this site before use. HVRemote and the associated documentation are provided "as-is". You bear the risk of using it. No express warranties, guarantees or conditions are provided. It is not supported or endorsed by Microsoft Corporation and should be used at your own risk.

Thanks,
John.
↧

NEW POST: Remote access to Hyper-V 2008 r2

September 17, 2012, 1:33 am
$
0
0
Hi,
I have hyper-v servers which are not on the same LAN. I would like to manage them with the same computer.
How can i configure admin computeur and/or firewalls to do this ?
Thanks a lot

Greg
↧

NEW POST: Remote Manage of Hyper-V 2008 R2 over the Internet

September 20, 2012, 6:01 pm
$
0
0
I leased a dedicated server in a datacenter with Hyper-V 2008 R2 and would like to know how to manage it from my home. I've run the script I found here and lots of other things and have managed to get access with Hyper-V Manager but have yet to get access with Server Manager, something about WinRM client. Is there an easy document explaining how to manager an Hyper-V 2008 R2 server over the Internet somewhere? Also, how to get Server Manager to work from my home would be nice. Thanks.
↧
Search

NEW POST: If it isn't the RPC server unavailable error I get it is a permission error

October 19, 2012, 10:12 am
$
0
0
I had VMs working on my machine just a few days ago and today I get this error when trying to build a Windows Server 2012 VM. When I click Finish at the end of the wizard to create the VHD I get the error: Cannot connect to the RPC service on computer 'localhost'. Make sure your RPC service is running.

I ran the settings manually before trying run the HVremote script and nothing has worked. What is my next step to troubleshoot. Also my machines do work if I am logged in to the local machine as the administrator.
↧
↧

NEW POST: Support for Windows 8 Accounts

November 9, 2012, 2:27 am
$
0
0
Hallo!

I realice that this is a rather old post, but I write an answer anyway since I just spent hours trying to manage Hyper-V Server 2012 from Windows 8 in Workgroup mode and maybe this post can help someone else if evan though the original poster may never read this.

I have noticed that if you look in "Computer Management" under "local users and groups"->"Users" on a Windows 8 computer then you see that the username stored on your computer is called something like "albert000" for a Microsoft account e-mail address called "albert.who@that.com". I have not tried this, but perhaps you can create the same account, ex. "albert000", on your Windows Server 2012 server? Please ensure that the account is given the correct permissions.

An other way that I have tried is to use server manager and to manage the server as another user and then use <server_name>\<local administrator>, for example myserver\administrator, and this seams to work. I can at least manage NIC Teaming and use the Hyper-V Manager. I followed instructions in this post: http://www.tumblr.com/tagged/server-2012.

Hope this helps!
↧

NEW POST: When will full support for Hyper-V Server 2012 and Windows 8 be added?

November 9, 2012, 2:38 am
$
0
0
You can read following on the start page:

"Support for Windows Server 2012 and Windows 8

10th Sept 2012 - Coming very soon in version 1.x, currently completing testing. It is not recommended you use version 0.7 on these operating systems and it may leave your system misconfigured."

This was posted over 2 months ago so my question is, when will version 1.x be finished?

I have already gotten it to work enough for my needs the manual way by using the post: http://www.tumblr.com/tagged/server-2012 as inspiration, but a new version with full support for Hyper-V Server 2012 and Windows 8 would be most welcome!
↧

NEW POST: Support for Windows 8 Accounts

December 13, 2012, 7:09 am
$
0
0
We found that we still could not access after running through the guide, but following Phillips post at http://blog.mpecsinc.ca/2009/06/hyper-v-error-access-denied-unable-to.html we were able to connect. Just need to add the anonymous remote access rights in dcomcnfg.
↧

NEW POST: Error message: "Cannot connect to RPC service on computer. Make sure your RPC serice is running"

December 14, 2012, 6:11 pm
$
0
0
I have a Windows 2008 R2 server running server core. The server is in a workgroup and the client I am using to connect is on a Windows domain. The client is using HyperV manager on Windows 7 pro. The firewall on the server is not on. The firewall on the client is not on. I used the cmdkey function to add the credentials for the client connecting to the server. I am not sure what else to do. Any help on this will be much appreciated.
↧
↧

NEW POST: Connection issues

March 1, 2013, 8:44 am
$
0
0
I can only apologise if this is solved elsewhere here but I am tearing my hair out with this.

I have windows 7 client connected to a domain - 345-20110802-01
I have Hyper-V core server - 345-vhost-01

I cannot connect to server from Hyper-V Manager

Here is my hvremote client output

C:\Users\Public\Lees Docs>cscript hvremote.wsf /show /target:345-vhost-01
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Hyper-V Remote Management Configuration & Checkup Utility
John Howard, Hyper-V Team, Microsoft Corporation.
http://blogs.technet.com/jhoward
Version 0.7 7th August 2009

INFO: Computername is 345-20110802-01
INFO: Computer is in domain 345GR.local
INFO: Current user is 345GR\admin
INFO: Assuming /mode:client as the Hyper-V role is not installed
INFO: Build 7601.18044.amd64fre.win7sp1_gdr.130104-1431
INFO: Detected Windows 7/Windows Server 2008 R2 OS
INFO: This appears to be a server SKU
-------------------------------------------------------------------------------
DACL for COM Security Access Permissions
-------------------------------------------------------------------------------
\Everyone (S-1-1-0)
Allow: LocalLaunch RemoteLaunch (7)
NT AUTHORITY\ANONYMOUS LOGON (S-1-5-7)
Allow: LocalLaunch RemoteLaunch (7)
BUILTIN\Distributed COM Users (S-1-5-32-562)
Allow: LocalLaunch RemoteLaunch (7)
BUILTIN\Performance Log Users (S-1-5-32-559)
Allow: LocalLaunch RemoteLaunch (7)
-------------------------------------------------------------------------------
ANONYMOUS LOGON Machine DCOM Access
-------------------------------------------------------------------------------
WARN: ANONYMOUS LOGON does have remote access
This setting should only be enabled if required as security on this
machine has been lowered. It is needed if you need to manage Hyper-V
on a remote server which is either in an an untrusted domain from this
machine, or both machines are in a workgroup.
Use hvremote /mode:client /anondcom:revoke to turn off
-------------------------------------------------------------------------------
Firewall Settings for Hyper-V Management Clients
-------------------------------------------------------------------------------

Private Firewall Profile is active

Enabled: Hyper-V Management Clients - WMI (Async-In)
Enabled: Hyper-V Management Clients - WMI (TCP-Out)
Enabled: Hyper-V Management Clients - WMI (TCP-In)
Enabled: Hyper-V Management Clients - WMI (DCOM-In)

-------------------------------------------------------------------------------
Windows Firewall exception rule(s) for mmc.exe
-------------------------------------------------------------------------------

Private Firewall Profile is active

Enabled: Microsoft Management Console (UDP)
Enabled: Microsoft Management Console (TCP)

-------------------------------------------------------------------------------
Additional configuration may be necessary
-------------------------------------------------------------------------------

This computer is in a domain. If the target server is in a workgroup,
you may need to set credentials for the server for Hyper-V Remote
Management to operate correctly. This step should not be necssary if
the target server is in the same or trusted domain as this computer.

If necessary, from a NON elevated command prompt, enter:

cmdkey /add:ServerComputerName /user:ServerComputerName\UserName /pass

Note that you MUST enter ServerComputerName to BOTH parameters.
You will be prompted for a password after entering the command.
-------------------------------------------------------------------------------
IP Configuration
-------------------------------------------------------------------------------
Windows IP Configuration
Host Name . . . . . . . . . . . . : 345-20110802-01
Primary Dns Suffix . . . . . . . : 345GR.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 345GR.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82567V-4 Gigabit Network Connect
ion
Physical Address. . . . . . . . . : 78-AC-C0-97-77-3A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 01 March 2013 14:50:05
Lease Expires . . . . . . . . . . : 02 March 2013 14:50:05
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 194.168.4.100
194.168.8.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{879E8D97-9C03-4FEF-9AE9-0044C33F3AEE}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:304b:2404:3f57:fffc(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::304b:2404:3f57:fffc%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled


-------------------------------------------------------------------------------
Stored Credentials
-------------------------------------------------------------------------------


Currently stored credentials:

Target: WindowsLive:target=virtualapp/didlogical
Type: Generic
User: 02uizvdjdlnp
Local machine persistence



-------------------------------------------------------------------------------
Testing connectivity to server:345-vhost-01
-------------------------------------------------------------------------------

1: - nslookup for DNS verification.

Note that failure is OK if you don't have a DNS infrastructure

~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Server: cache1.service.virginmedia.net
Address: 194.168.4.100


      • cache1.service.virginmedia.net can't find 345-vhost-01: Non-existent domain

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

2: - ping attempt (ping -4 -n -1 345-vhost-01)

Note the ping may timeout - that is OK. However, if you get an
error that 345-vhost-01 could not be found, you need to fix DNS
or add an entry to the hosts file. Test 3 will fail and provide more
guidance.

This may take a second or two...

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

Pinging 345-vhost-01 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.101:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

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


3: - Connect to root\cimv2 WMI namespace
          • Failed to connect to root\cimv2
          • Error: -2147023174 The RPC server is unavailable.
          • Namespace: root\cimv2
FAIL - Was unable to connect. Diagnosis steps:

- Have you run hvremote /add:user or hvremote /add:domain\user
on 345-vhost-01 to grant access?

- Are you sure the server name '345-vhost-01' is correct?

- Did you use cmdkey if needed? More information higher up.

- Did you restart 345-vhost-01 after running hvremote /add for
the very first time? (Subsequent adds, no restart needed.)

- Is DNS operating correctly and was 345-vhost-01 found?
Look at the output of tests 1 and 2 above to verify that the
IPv4 address matches the output of 'ipconfig /all' when run on
345-vhost-01. If you do not have a DNS infrastructure,
edit \windows\system32\drivers\etc on 345-20110802-01
to add an entry for 345-vhost-01.

INFO: Are running the latest version

-------------------------------------------------------------------------------
3 warning(s) or error(s) were found in the configuration. Review the
detailed output above to determine whether you need to take further action.
Summary is below.

1: Anonymous Logon has remote access (may be ok)
2: You may need to set credentials for access to the server
3: Cannot connect to root\cimv2 on 345-vhost-01

-------------------------------------------------------------------------------

C:\Users\Public\Lees Docs>

Here is my hvremote server output

...in next post as run out of space!
↧

NEW POST: When will full support for Hyper-V Server 2012 and Windows 8 be added?

March 24, 2013, 8:40 am
$
0
0
Please remember that John is doing this voluntarily and I am sure he has many other things that are on his plate. If you have looked through the code then you can appreciate the time it takes to pull all this together. Remember that Google is your dearest friend in this. It has been frustrating for me too to try and learn all about this on my own but from the resources on the web and asking our system admins, I have learned a lot. Hopefully MS will one day make it as easy as VM Ware but until then, hang in there.
↧
Search

UPDATED RELEASE: HVRemote Version 1.06 (Mar 28, 2013)

March 28, 2013, 10:57 am
↧

UPDATED WIKI: Home

March 28, 2013, 11:00 am
$
0
0

About

    • HVRemote reduces the manual configuration steps needed for Hyper-V Remote Management down to a few simple commands.
    • HVRemote can diagnose common configuration errors.
    • HVRemote is locale neutral, although output is in English only.
    • HVRemote can configure all combinations of workgroup and domain joined clients and servers.
If you find HVRemote useful, please drop me an email through my blog, or add a comment to this post :)

Support for Windows Server 2012 and Windows 8

28th March 2013. Version 1.06 is the first public version which includes Windows Server 2012 and Windows 8. Note that only local and domain accounts have been tested and verified, not Microsoft accounts. If using Windows Server 2012 or Windows 8, you should use this version, NOT version 0.7. I am treating this release as a 'Release Candidate' purely because it has not undergone exhaustive verification on down-level operating systems. However, there are no known issues at this time.

10-second guide


ConfigurationWherePurposeCommands
Client and Server both workgroup Server Create a local account (eg "john") Use net user /? or Computer Management
Server Grant the user access cscript hvremote.wsf /add:accountname ***
Client Allow Anonymous Logon remote DCOM access cscript hvremote.wsf /anondcom:grant
Client Logon with matching local account. Ctrl+Alt+Del :)
Client If passwords do not match cmdkey /add:servername /user:servername\account /pass
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername
-------------------------
Client workgroup, Server domain Server Grant domain account access cscript hvremote.wsf /add:domain\account ***
Client Allow Anonymous Logon remote DCOM access cscript hvremote.wsf /anondcom:grant
Client Set credentials for domain account cmdkey /add:servername /user:domain\account /pass
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername
-------------------------
Client domain, Server workgroup Server Create a local account (eg "john") Use net user /? or Computer Management
Server Grant the user access cscript hvremote.wsf /add:accountname ***
Client Allow Anonymous Logon remote DCOM access cscript hvremote.wsf /anondcom:grant
Client Set credentials for local account Use cmdkey /add:servername /user:servername\accountname /pass
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername
-------------------------
Client and Server both domain Server Grant the non-admin user access cscript hvremote.wsf /add:domain\account ***
Both Verify configuration for errors cscript hvremote.wsf /show /target:othercomputername


*** Restart server if this is the first time an account has been added. Not required for Windows 8 Client Hyper-V or Windows Server 2012

Supported Servers:

    • Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), Core & Full installations
    • Windows Server 2008 SP2, Core & Full installations
    • Microsoft Hyper-V Server 2008 SP1 (already contains Hyper-V RTM update)
    • Microsoft Hyper-V Server 2008 SP2
    • Windows Server 2008 R2, Core & Full installations
    • Windows Server 2008 R2 SP1, Core & Full installations
    • Microsoft Hyper-V Server 2008 R2
    • Microsoft Hyper-V Server 2008 R2 SP1
    • Windows Server 2012 Core & Full installations (Version 1.x or later)
    • Microsoft Hyper-V Server 2012 (Version 1.x or later)
    • Windows 8 Client Hyper-V (Version 1.x or later)

Supported Clients:

    • Windows Vista Business, Enterprise and Ultimate x86 & x64, SP1 and SP2, with KB952627 applied
    • Windows 7 Professional, Enterprise and Ultimate x86 & x64 with RSAT installed and Hyper-V tools feature enabled
    • Windows 8 Pro and Enterprise x86 and x64 with Hyper-V Management Tools feature enabled (Version 1.x or later)
    • Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), x86 and x64
    • Windows Server 2008 SP2 x86 and x64
    • Windows Server 2008 R2
    • Windows Server 2008 R2 SP1
    • Windows Server 2012 (Version 1.x or later)

Command summary


Please see the documentation for more information - below is not a complete list of all command line options, just the most commonly needed commands. Commands should be run from an elevated command prompt.

If the default scripting engine is already CScript, you can run each command exactly as shown in the table. To change the default scripting engine to cscript, run cscript //h:cscript. Alternately, launch each command using the longer format: cscript hvremote.wsf command

ApplicabilityOperationCommand
Server Grant account access hvremote /add:domain\account (Domain)or hvremote /add:account (Workgroup)
Server Revoke account access hvremote /add:domain\account (Domain)or hvremote /add:account (Workgroup)
Both Display settings hvremote /show
Client Display settings and test server connectivity hvremote /show /target:servercomputername
Server Display settings and test client connectivity hvremote /show /target:clientcomputername
Both Display help hvremote /?
Client Permit ANONYMOUS LOGON remote DCOM access hvremote /AnonDCOM:grant
Client Deny ANONYMOUS LOGON remote DCOM access hvremote /AnonDCOM:revoke

Installation


Save HVRemote.wsf from the Downloads tab to a directory on the local disk (eg c:\HVRemote)

Disclaimer


Although I work for Microsoft and am a Program Manager in the Hyper-V team, I must point you to the disclaimer on my blog, the disclaimer in the documentation, and the license conditions on this site before use. HVRemote and the associated documentation are provided "as-is". You bear the risk of using it. No express warranties, guarantees or conditions are provided. It is not supported or endorsed by Microsoft Corporation and should be used at your own risk.

Thanks,
John.
↧
↧
Viewing all 37 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>