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

NEW POST: Cannot Create VHD

July 21, 2011, 2:46 pm
$
0
0
Issue solve
Scenario Hyper-V and Windows 7 Hyper-V manager same work group and same credential (Password and user)
1- At the Hyper-V server join the user to the admin group, log off administrator and log in with the user account.
2- At the Windows 7 machine make sure you are logging as the user your create in the Server and proceed create a Virtual Machine.

Some suggestion.

Create a folder outside users folder containing your HD images for easy access.

Hope it helps

Thanks
↧
Search

NEW POST: Cannot Create VHD

July 25, 2011, 7:38 am
$
0
0
Thanks but I still need to have two domain members Hyper-V servers managed by my stand alone notebook.
Otherwise I would have already configured my notebook as domain member, the fact is that the two servers are members of two different domains.
↧
↧

NEW POST: Cannot Create VHD

August 20, 2011, 12:27 am
$
0
0
Somewhat solved but can't say exactly why but it works now.

I have 1 hyper-v Server 2008 r2 sp1 in a workgroup and W7 64 bit client in the same workgroup.

I have done all the hvremote.wsf stuff and I am now able to connect remotely using windows 7 with hyper-v Manager to the hyper-v Server 2008 r2 sp1.

Now when I try to create a new VM and vhd drive while creating the VM it always fails as it is creating the disk. After failing I see that RPC error stuff.
I turned off the W7 Norton 2011 firewall and still no help.
So I said since it looks like it fails when creating the vhd.... why not create the vhd 1st???

So 1st I created the VHD at 1 gig fixed no OS. VHD created ok.
2nd I Created a VM and said to use the previously created VHD in the VM creation process......
YES!! >>> IT WORKED!!

Now I decided to stop all the hyper-v services on the server and erase everything in the VHD storage dir and config dir... then I restarted all the services... there are 3 services... may not have had to stop all 3 but I did.
NOTE: I am using W7 computer management then connect to another computer... then services....

Now I tried to create a VM and a new vhd as I was in the VM creation. WOW it worked and now I don't have to create a vhd 1st.

I know this isn't real technical way to do this and I can't tell you why.... I just got tired after doing all the tech stuff and did the "chick or the egg" routine.

Now maybe someone can better technically explain this.
Before any of the above both systems had been rebooted many times... some services stopped and restarted many times. Locations of the vhd and configs changed many times.....

I have worked on this many hours and will test more on another day.
↧

NEW POST: RPC Server Unavailable - Exception 0x800706BA

August 30, 2011, 9:16 pm
$
0
0
I have a workgroup using W7 client for remote management of my Hyper-v Server 2008 R2 in my test environment and could not do any diskmanagement. I have Norton Internet Security installed on W7 client and thought only using it for a firewall. I have the IP of the Hyper-v server setup as a trusted IP. Still not enough.....
I had to go to services and turn off the W7 firewall service. You would think since Norton Internet Security takes over the firewall that you would not have to disable the windows firewall service.

↧

NEW POST: Cannot Create VHD

September 8, 2011, 3:18 pm
$
0
0
I am still able to replicate this issue on many systems, the fact is that nothing happens when both client and Hyper-V server are domain members neither when both are stand alone computers (a.k.a. workgroup members), but it does happen when the Hyper-V server is domain member and the client isn't. I can create and delete VM without any error but I have not to manipulate any vhd files, I only can create vhd files with vhdtool.exe, modify them with 3rd party tools and then link them to the VM or remove them. I don't have to try to manage vhd files within the Hyper-V management console, otherwise it get stuck.
↧
↧

NEW POST: Server 2008 Hyper-v clients connect fine, Windows 7 clients get RPC error

October 6, 2011, 8:00 am
$
0
0
I have carefully set up Hyper-v and a couple of clients according to the directions at http://technet.microsoft.com/en-us/library/ee256062%28WS.10%29.aspx
On a Windows Server 2008 R2 virtual machine, I can run the Hyper-V Manager and connect to my Hyper-V server without any problems. However, on a Windows 7 machine, I consistently get "RPC Server Unavailable". I tried running hvremote.wsf /show /target:hyper-vhost.domain, which passed on every step except 7 (as shown below). I tried and verified all solutions suggested in step 7, including DNS verifications, with no joy. I have also tried disabling the client's firewall with no joy.

Does anyone see any problem I might not have addressed?

Text of error portion:

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 hyper-v.campus.wm.edu: ping -4 TESTFS11N

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 TESTFS11N

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 hyper-vserver.domain: ipconfig /flushdns
Run on TESTFS11N: ipconfig /registerdns

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

If the server is in an untrusted domain to this client, you need to
enable anonymous logon access to DCOM on this machine:

Run 'hvremote.wsf /mode:client /anondcom:grant' and retry.

If this machine has IPSec policy enforced on it, and the server is
in a workgroup, inbound connections to the client may be blocked
by your administrator. You may be able to temporarily work around
this by running net stop bfe on this machine, but you may lose access
to some network services while that service is stopped.



INFO: Are running the latest version

-------------------------------------------------------------------------------
2 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 does not have remote access (may be ok)
2: Cannot perform async query against root\virtualization
Please see resolution steps above.

-------------------------------------------------------------------------------
↧

NEW POST: Unable to connect to root\cimv2

October 17, 2011, 1:44 pm
$
0
0
everything seems to be configured correct, no errors from the script as seen below, but yet I still cannot connect to the hyper v server (HOST)
C:\2008_Server\HyperV>cscript hvremote.wsf /show /target:192.168.2.112
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 MIKEHOME
INFO: Computer is in workgroup WORKGROUP
INFO: Current user is MIKEHOME\mike
INFO: Assuming /mode:client as the Hyper-V role is not installed
INFO: Build 7601.17640.x86fre.win7sp1_gdr.110622-1506
INFO: Detected Windows 7/Windows Server 2008 R2 OS

WARN: The Windows firewall is not active in one or more active profiles.
Not all functionality of HVRemote will be available.
Use 'netsh advfirewall set currentprofile state on' to turn it on!

INFO: Remote Server Administration Tools are installed
INFO: Hyper-V Tools Windows feature is enabled

-------------------------------------------------------------------------------
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
-------------------------------------------------------------------------------

          • Skipping. The firewall is not running or turned off

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

          • Skipping. The firewall is not running or turned off

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


Windows IP Configuration

Host Name . . . . . . . . . . . . : MIKEHOME
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : burnnitro.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : burnnitro.net
Description . . . . . . . . . . . : Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controll
r
Physical Address. . . . . . . . . : 00-1F-C6-26-2A-08
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6828:ed8f:1137:c309%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, October 17, 2011 2:21:14 PM
Lease Expires . . . . . . . . . . : Tuesday, October 18, 2011 2:21:14 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 234889158
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-73-B4-66-00-1F-C6-26-2A-08
DNS Servers . . . . . . . . . . . : 4.2.2.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.burnnitro.net:

Connection-specific DNS Suffix . : burnnitro.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.101%11(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 4.2.2.2
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

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
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:c5e:a36:3f57:fd9a(Preferred)
Link-local IPv6 Address . . . . . : fe80::c5e:a36:3f57:fd9a%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled


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


Currently stored credentials:

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



-------------------------------------------------------------------------------
Testing connectivity to server:192.168.2.112
-------------------------------------------------------------------------------

1: - nslookup for DNS verification.

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

~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2


      • vnsc-bak.sys.gtei.net can't find 192.168.2.112: Non-existent domain

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

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

Note the ping may timeout - that is OK. However, if you get an
error that 192.168.2.112 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 192.168.2.112 with 32 bytes of data:
Reply from 192.168.2.112: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.2.112:
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
- 1 computer system(s) located

7: - Async notification query to root\virtualization WMI namespace
PASS - Async notification query succeeded

INFO: Are running the latest version

-------------------------------------------------------------------------------
2 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: Firewall is not active
2: Firewall not running (skipped Hyper-V Management Clients)

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

C:\2008_Server\HyperV>
↧

NEW POST: Workgroup mode : Cannot connect to the rpc service

November 1, 2011, 8:36 pm
↧
Search

NEW POST: Hyper-V Management From Different Client PC's on Different Domains

November 8, 2011, 10:27 pm
$
0
0
I'd also like to know about this one. Hyper-V Server is joined to one domain, client management PC is in another. Any way to accomplish this?
↧
↧

NEW POST: Hyper-V Management From Different Client PC's on Different Domains

November 17, 2011, 11:39 am
$
0
0
Treat them as workgroup machines and follow those steps if both domain joined, but with no trust.
~John.
↧

NEW POST: Unable to connect to root\cimv2

December 13, 2011, 5:02 am
$
0
0
Same problem here. With the same domain credentials works from one pc and not from another. The output is:


E:\Downloads>cscript hvremote.wsf /show /target:hyper1
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 SERVER1
INFO: Computer is in domain PSS.local
INFO: Current user is SERVER1\Demetrios
INFO: Assuming /mode:client as the Hyper-V role is not installed
INFO: Build 7601.17640.amd64fre.win7sp1_gdr.110622-1506
INFO: Detected Windows 7/Windows Server 2008 R2 OS
INFO: Remote Server Administration Tools are installed
INFO: Hyper-V Tools Windows feature is enabled
WARN: UI tracing is turned on. Use 'hvremote /trace:off' to turn off

-------------------------------------------------------------------------------
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
-------------------------------------------------------------------------------

Domain 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
-------------------------------------------------------------------------------

Domain Firewall Profile is active

Enabled: Microsoft Management Console (HVRemote.wsf Created) (UDP)
Enabled: Microsoft Management Console (HVRemote.wsf Created) (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 . . . . . . . . . . . . : SERVER1
Primary Dns Suffix . . . . . . . : PSS.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : PSS.local

Ethernet adapter Local Area Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-C2-26-C9-48
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TeamViewer VPN Adapter
Physical Address. . . . . . . . . : 00-FF-55-EE-A9-AE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : PSS.local
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-25-22-7D-B5-D6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.150(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : ??ε??, 13 ???????ε?? 2011 14:31:37
Lease Expires . . . . . . . . . . : ???α???, 14 ???????ε?? 2011 14:31:36
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.120
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.PSS.local:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : PSS.local
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* 11:

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.{55EEA9AE-E18B-4F82-AEEF-10EBE1FD6569}:

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

Tunnel adapter isatap.{C226C948-80E8-4FB6-BF34-9BF07C3B3C3B}:

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


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


Currently stored credentials:


-------------------------------------------------------------------------------
Testing connectivity to server:hyper1
-------------------------------------------------------------------------------

1: - nslookup for DNS verification.

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

~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Server: UnKnown
Address: 192.168.1.120

Name: hyper1.PSS.local
Addresses: 192.168.1.100
192.168.1.99


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

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

Note the ping may timeout - that is OK. However, if you get an
error that hyper1 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 HYPER1.PSS.local 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time=3ms TTL=128

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

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


3: - Connect to root\cimv2 WMI namespace
          • Failed to connect to root\cimv2
          • Error: -2147024891 Access is denied.
          • Namespace: root\cimv2
FAIL - Was unable to connect. Diagnosis steps:

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

- Are you sure the server name 'hyper1' is correct?

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

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

- Is DNS operating correctly and was hyper1 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
hyper1. If you do not have a DNS infrastructure,
edit \windows\system32\drivers\etc on SERVER1
to add an entry for hyper1.

INFO: Are running the latest version

-------------------------------------------------------------------------------
4 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: UI tracing is turned on. Run 'hvremote /trace:off'
2: Anonymous Logon has remote access (may be ok)
3: You may need to set credentials for access to the server
4: Cannot connect to root\cimv2 on hyper1

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

E:\Download
↧

NEW POST: RPC Server Unavailable - again

December 30, 2011, 2:32 am
$
0
0
HI,

in my Server (workgroup) and client (same wokrgroup) I was not able to get the Hyper-V Manager to work. hvremote tests were all good.

I could manage to get things running after disabling the public firewall. Is there a way to force a server core 2008 R2 server to use the private private firewall profile?

Tracking down the problem i need to enable at least the "(Network Discovery (LLMNR-UDP-In)" service in the Public Firewallprofile to get the thing working. I also noticed
that I can do a PING SERVERNAME after enabling the the service in the servercore firewall (always STOP and start the ping -t to watch this), this wasn't working when the "(Network Discovery (LLMNR-UDP-In)" service was turned off.

Can anybody confirm this, because a connection test to this firewall rule, would be a nice addition to the hvremote script.
↧

NEW POST: Unable to connect to root\cimv2

January 14, 2012, 12:45 pm
$
0
0
I had the same problem, try this:
go on the PC where hyperv manager is running and type the following:
cmdkey /delete:<hypervservername>

That worked for me.
Regards
GiaGT
↧
↧

NEW POST: Windows 7 issues

February 2, 2012, 6:52 am
$
0
0
Hello, I have exactly the same problem. Can you say me what GPO's denied the access?

My envairoment is a Workgroup, with Windows 7 Profesional for de Administrator Hyper-V and a Hyper-V 2008 Core installation.

Thank you very much.
↧

NEW POST: Black screen "Connecting to 'New Virtual Machine'"

February 20, 2012, 3:49 pm
$
0
0
Hi,

I have a new fresh server from my hoster with Windows 2008 R2 and i have just installed the hyper-V role. If i create a new virtual machine and start it, i can see the bios and windows setup etc. in the small preview window at the bottom of the hyper-V server manager. But i cannot connect using the "virutal machine connection".

I tried everything, installed updates, changed network settings, created virtual networks, ran hvremote etc. But nothing helps. I still get the black screen with "Connecting to "New Virtual Machine".

Does anyone know what´s wrong?
Thanks,

Sven
↧
Search

NEW POST: RPC Server Unavailable - again

March 31, 2012, 8:15 am
$
0
0
I had the same issue with tha same configuration (Server and client in the same wokrgroup, Hyper-V Manager error "RPC Server Unavailable", hvremote tests all good).
Disabling public firewall on server worked for me too.
Thank to your post I could solve the problem.
↧

NEW POST: My HyperV server is 'now' remotly managed !

April 5, 2012, 3:29 am
$
0
0
And i had most of trouble explain in that wiki.
I lost lot of time to debug and find why my remote management does not work. Please, Microsoft, add the hyperc remote snapin inside HyperV Server !!!
My config is : hyperv server and my admin computer are in different workgroûp, not in the same ip network.
My admin computer is behing a firewall with NAT activated and with a private IP adress.
My hyperv server has a public IP Adress correctly declared in the DNS.

I'm just sharing here what i've done to do it working (of course i used hvremote script for major task, see hvremote doc ) :

- in my admin computer :
- i added in the host file (c:\windows\system32\drivers\etc\host) the shortname of my server (without domain) and its public IP

- in my hyperv Server :
- i added in the host file the name of my admin computer and the public IP seen (attached to the firewall, not the private ip of my computer)

- i configure both computer (server and admin) with hvremote script

but i still add trouble shoot : i can create network with hyperv management but filling vm list failed, ..... It appears that hyper V i making DCOM callback to the admin client. (that why he need to link the public IP to my admin computer name).
Then hyperv server need to use a specific service : the RPC Port mapper on my admin computer to make DCOM CallBack. The RPC port mapper is accessible on the IP port 135 ....
and then the firewall need to forward the ip port 135 to my admin computer.
Your windows firewall need to allow this port access too.

another point to check : if you network card has a public profil, hvremote rule are not activated on public profil. You have to do that manually

WARNING : forwarding/opening this type of port could break your computer/netword security and integrity ! DO NOT OPEN IT IF YOU ARE NOT SURE WHAT YOU'RE DOING ! RESTRICT ALLOWED SOURCE IP TO YOUR HYPERVSERVER ! DEACTIVATE FORWARDING WHEN NOT NEEDED. I will not take responsability of consequences. !


have a nice management day :)
Nicolas.

--
Nicolas CLERC
Microsoft Regional Director
QuidMind CTO
http://www.Quidmind.com


↧
↧

NEW POST: Unable to connect root\cimv2

April 10, 2012, 3:34 pm
$
0
0
I am currently failing the test 3 related to connecting root\cimv2.

The ideal is that i have two windows server core servers in Germany data center and client computer is in USA, will be connecting to the servers via WAN and using server manager/hyper-v to manage the servers.

I am kinda new to the whole domain, users, Cerf and stuffs like that, so please bear with me.

I have spend last three whole days struggling various combinations of names/methods/ideas to resolve this problem.

For testing purpose, i have completely disabled firewall on both server / client side and is able to ping each to other using PC name.

Here's the /show for client and server.

client /show : http://pastebin.com/8Ep5FXdU
server /show : http://pastebin.com/Hict02ZX

I am aware that I am currently failing the test 3, i have tried to follow the procedure, when trying to hwremote /add:PKO-PC\PKO I get trusteefailed and I have setup local account on server with same username/password as client has.

any help is really appreciated.
↧

NEW POST: Unable to connect root\cimv2

August 17, 2012, 1:51 am
$
0
0
I installed the Server Core Hyper-V on my HP Microserver (workgroup/microserver) to run 2 or 3 virtual machines.

I ran your script and the only error is "Unable to connect root\cimv2" on my client. Ping/dns all that works fine.

So I went back to your blog and started reading that I need to create a user account with matching credentials. Now it is possible that is wahts causing the problem?

I added my client "dell" in the server-core blue command. Then ran /add:dell - it did all the things and ended happily. Reboot.

I do a /show:microserver on my dell client. "Unable to connect root\cimv2"

So it is permission issues... I will try and sort it out using your blog.

But the problem here is that hyper-v server core enforces very strict password and my dell client, well, I turned on allow empty passwords for remote connection so I can SSH tunnel to my Dell using Windows RDP.

I think your script need to check this issue too- check client machine if a password exists and whether it matches the strict password policy for the server? (I think it is safe to say 90% of the time it will fail?)

I do not know if that is the cause yet why my client hyper-v snap is still says cannot connect or not. But if matching users are requires for workgroups then it would be good to mention it on the script results somewhere? :-)

Thanks for a great script anyway and your blog is the only one out there explaining this slight nightmare. Thanks a billion!
↧

NEW POST: Unable to connect root\cimv2

August 17, 2012, 10:27 am
$
0
0
I am having the exact same issue. I was able to connect to hyper-v server by temporarily joining the server to a domain. So the problem lies in authenticating the user. But my server needs to be in a work group environment. It is a pity that MS will make this so difficult to manage if one has no domain. Hope we both get an answer soon.

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