Hello,

I have two sites with a unique Hyper-V Cluster at each site.   At each of the sites I have two CSV's, neither of which is large enough to hold all of my virtual machines. I would like to setup Hyper-V Replica so that if I have a failure at either site I can spin up my virtual machines.

When configuring Hyper-V Replica Broker I can add the Replica Broker Name as an authenticated server and choose a default location for the machines to be stored.  But how do I configure it so that half of my machines are replicated to one CSV and half to the other?  Can I add in the individual names of the Hyper-V Clustered Servers? But even if I could add them how can I ensure that the individual machines will always end up in the correct spot?  Filling up a CSV leads to bad behavior.

Any thoughts on how can I get around?  If you pre-stage the files can you use different replica locations?

Thank you,

Matt

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012

The following guide will enable you to:

1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager

! This should also work for Core installations of server 2012, but I haven't tried.

This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.


* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.

- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.

> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)

1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.

! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012

2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.

> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
----------------------------------------------------------------------


> Next, is to get the MMC firewall snap-in working.
   The reason for this, is to have a GUI available to configure it.
   If you're happy without it, you may skip this and use a shell instead to do so.

? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)

! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level 
# (In other words: allows the firewall to be remotely managed)

! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.

? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.

! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done

! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon, 
# and choose run as admin on the bar below.

! Client: application MMC: select "file" --> Add/remove snap-in 
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)

* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.

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

! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.


! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.

! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate

# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
#
# I recommend to choose yes; unless you like to pull some more hairs...

! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
!  select yes

! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server

Done.

You can now manage your remote server through the familiar computer management GUI.

! Right-click your remote server, and select "Computer Management"

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

A few side notes:

? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.


If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.

Cheers!

Hello,

I have successfully configured other Window 7 Workstations for Remote Management of Hyper-V following the steps in this article:  

http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/11/configuring-remote-management-of-hyper-v-server-in-a-workgroup.aspx

This explains how to setup Hyper-V Manager when your server is not part of a domain.  However, I am having problems with one of my pc's.  After successfully executing winrm quickconfig I have the following problem executing the following command:

      winrm set winrm/config/client @{TrustedHosts="rlpserver"}

it comes back with the error:  Error: Invalid URI - cannot locate last token for root node name

rlpserver is a Windows 2008 R2 CORE Server that is running Hyper-V.  The server side has been successfully configured for Remote Management as I am able to manage Hyper-V from other devices.  I am able to successfully ping rlpserver.

Any assistance to resolve this problem will be greatly appreciated.

Regards,

Matt Paisley

mpaisley@optonline.net

Matthew Paisley

Hello all,

Over the next few months i am going to be setting up hyper-v on server 2012. The virtual machines will only host MDT 2012, WDS and Windows 7 as a reference computer. I am after some advice on the configuration of the host servers hard disks. The host will have some roles installed like AD DS, Print and File services. The virtual machines will not be doing much until we deploy images from them.

The host server will have 3 2TB hard drives configured to use RAID. How would you partition the drives to allow for a few virtual machines but also allow the host to have some roles installed?

Thanks for any help in advance

Shane

I'm starting to learn Hyper-V and other great tools from Microsoft and I want to have a Laptop that can do the job. ( on a friendly budget )

Obviously, this is a test environment so it won't have a ton of users. Only me testing app's, websites, policies, and all related Hyper-V stuff.

I am planing to have of a Domain Controller, a Backup Server, Exchange and SharePoint.

We are talking about 4 to 6 servers as far as I know. 

I've check out some HP laptops with the new A8 and A10 CPU's with AMD graphics and found that the G6 and G7 have the same specs. A8 1.9Ghz 4mb L2 Cache Quad with 4GB DDR3 Ram with ATI 7450 video card and 500GB HD.

BB have t in 15.6 inch $399 and 17.3 inch $499

Any comments and suggestion are greatly appreciated.

I have a windows 8 Host to a Virtual Domain Controller (Windows Server 2012). The host and all other PCs have no problem joining the domain. My problem is that when I attempt to logon to the domain with a user account on the Host it says no domain server is available, yet all other PCs joined to the domain have no trouble finding the server when a user attempts to logon. Why can't a person logon on the domain from the host? What am I missing? All network adapters are pointing to the Domain server as the primary DNS. The host is the only one that can't logon, even though I am able to join the domain and assign users to the PC from the domain. Basically as long as I am already logged on with a local PC Account (not domain account) I can do any network thing any other pc can do.

KRom

Hi there,

I’m trying to export VM from our ‘old’ Hyper-V 2008 R2 server onto the ‘new’ 2012 one. Both Hyper-V hosts are in the same Active Directory domain. Since core editions don't have GUI I’m using Hyper-V Manager console on my workstation (Client1).

As soon as I click ‘export’ button I have windows popup immediately with the error message: “Failed to create export directory… (0x80070005)”?!

I have setup appropriate share and NTFS permission as recommended by this post: “Error 0x80070005 when exporting Hyper-V VMs over the Network” (http://support.microsoft.com/kb/2008849). I even gave Client1 the same permission but still have the same error message?! From Client1 or Server1 I can connect to the \\Server65\Export$ folder, can copy/delete/create folders and files without any problems. What I have missed?! Please help, thanks.

I can not print to my network Dell 2155cn printer either by USB or network.

Hi,

I am looking for a list of virtualized NICs in Hyper-V and which drivers I will need.

Which NICs virtualized in Hyper-v for Guests OSs?

i will be glad to get a link to a refrence of virtualized hardware list in Hyper-v.

BTW, does Hyper-V has support for paravirtualized guests?

Thanks,

Tole 

Hi,

I create virtual machine with 2 processor and 32 gb memory. My hyper-V server have 128 GB memory, 2 proc (16 core). OS: windows server 2008 R2 enterprise.

If I shutdown/ restart virtual machine, stopping process is very long time about 20 - 25 minutes.

I just get warnig on Hyper-V-worker event viewer like below:

Let me preface this question with my background.  I'm coming from a VMware environment where I assigned/presented large volumes to each hypervisor and I put all of the VM's(VMDKS) in those big LUNS/Volumes and this was done via fibre channel...  Here we are using ISCSI and I have limited experience with this technology (but learning). They have in the past here created a new volumes for every single VM and Volume and presented all of those to the Hyper-V servers.

I've heard great things about Hyper-V, excited to learned, and want to get this new environment running much better than it is now.  The problem is I'm seeing a lot of errors on our Hyper-V boxes and we've had them bluescreen a couple times. In the systems logs I see a lot of the following:

Error Event ID 55 Source Ntfs - The file system structure on the disk is corrupt and unusable. Please run the chkdsk utilitiliy on volume _

Warning: Event ID 57 Source Ntfs - The system failed to flush data to the transaction lo.g corruption may occur,  

Information Event ID 2 Scource:MPIO - Added device to \Device\MPIODISK#. DumpData contains the current number of paths

My assumption is that with all of these volumes there is alot more ISCIS chatter on that network that is causing volumes to drop....  Where do I begin? 

Thanks you for any assistance in advance

Brand new Server 2012 Hyper-V installed on Dell R720 with dual quad Broadcom NICs.  Set up NIC teaming inside the Guest OS since SR-IOV enabled (http://blogs.technet.com/b/jhoward/archive/2012/03/20/everything-you-wanted-to-know-about-sr-iov-in-hyper-v-part-7.aspx).

I do not use DHCP for servers and so was trying to set static IP for each VM.  Since the NICs are teamed in the Guest, the only thing to select is the Team, so I gave it a static IP.  I can RDP into the VMs, yet I can't ping that IP or the Name of the server from my admin box or from the Hyper-V parent server itself.  However, the VM can ping anything and everything it wants. 

Am I missing something in the setup that allows me to ping the VMs?

OK, here goes. I have a client who had a Windows 2003 server that crashed due to major hardware issues. It is a Doctors office with patient records dating back 15 years. We tried to remove the databases and move them to another server and kept running into corruption errors. We worked with the manufacturer of the software but got nowhere as the application was sold to IBM in '07 and there is no support options left. We made a VHD of the OS and put it on a Windows 2008R2 w/Hyper-V server. We demoted the OS and joined it to the new 2008 servers domain. Everything was working fine for the initial tests for access to the data. The next step was to get connectivity from the workstations to the VM OS for the application, again all worked well. The sticking point right now is that I have the VM (W2K3) configured so that everyone has access to the "old server" for the legacy software, but cannot figure out how to configure access for the 2nd nic which connects directly to the Xray machine. The hierarchy I have in mind is this:

Nic one is an  Intel 82574L. It is configured with a 192.168.21.20 IP

Nic2 is a Intel 82579LM with an IP of 10.0.0.1 (the vm nic has 10.0.0.2)

This is the way the old server was connected. The first network card for the internal network and the second nic configured for 10.0.0.1 connected to the Xray machine.

This is my f1rst attempt into the virtual arena and I am getting confused as to the proper way to configure this. After playing around with the network connections naming I have attempted to name the connections for their purpose.

In the Virtual Network Manager I have 3 listings:

1: Scanner Network Connection. It is set up as external on the 82579LM card (Nic2) Allow management checked.

2: W2K3VM Connection is on the 82574L (Nic1) also as external with All management checked

3: Local area connection set for internal only. I am assuming that it was there upon installing the Hyper-V.

Within the VM I can click on the lan connection which I named "domain name" connection it shows the proper IP address 192.168.21.21.

When I try and enable the 2nd virtual nic it has an IP of 10.0.0.2 along with the proper subnet for connection to the Xray machine. The only problem is it does not connect and the connection with the workstations on the lan is interrupted.

Upon trying to connect the second nic on the host server It says there is connectivity. With the vm it shows it is also connected but the cannot access the xray machine and the workstations have no access. It is hopefully something simple that I just do not see. Any suggestions would be appreciated.

It now seems that the AD DNS which worked fine before enabling the second nic had malfunctioned. The host OS DNS gives an error now that says: The server scan could not be contacted ther error was: A security package specific error occurred.

They are using Symantec End Point Protection 12.1.2 and I have set up (as a test) rule to allow all traffic both ways for IP and UDP traffic.

I have looked at so many posts I am lost for a solution.

Sorry for the convoluted post. Thanks for the help!

Devin

Hi

We have a Dell Poweredge R710 rack server running Hyper-V server 2008 as the OS, the problem is.... no one seems to know how much physical RAM the server actually has!!! It's easy to find out using a Windows OS, as you simply right click My Computer and select properties but I cant figure it out using the Hyper-V Manager???

Any advice would be very welcome, thanks.

I have a host server running Windows Server 2008 and on this I have a Virtual Server (using Hyper-V) running Windows Server 2003. The Virtual server hosts websites specifically. I am trying to use the Windows Firewalls on them (Host and Virtual Servers) to secure them incase my Hardware Firewall goes down (again). I need to have RDP enabled and Specific IP's only allowed. I have this working for the host. However, when I did the same process for the virtual server, RDP wasn't restricted to the specific IPs. Meaning that I could still access the virtual server from an IP that wasn't on the list. So my question is, How is the virtual server's firewalling handled differently? The VSwitch is set external. It is my understanding that this means that traffic is routed from within the physical NIC by Hyper-V? I'm still learning virtualization and Hyper-V. Also the virtual server is running in snapshot mode. Not sure if that makes a difference with the firewall issue.

Any insight would be greatly appreciated.

Thanks,

KV

When I create a new snapshot in HyperV, the GUI does not update.  Sometimes I think it didnt register my mouse action so I do it again only to not have the GUI refresh.   If you close the MMC and restart Hyper MMC snapin, then all of a sudden you see all of your snapshots.  Why does the GUI not update after taking a new snapshot?

I support Small Business Server 2011 and 2008 clients and need to look at Small Business Essentials 2012 support to grow my business.

I currently have enough hardware to do all my configurations but believe I am missing the point by not using Hyper-v to it's full capacity:

I have a physical Dell PowerEdge r710 running my own sbs2011 domain that I want to leave as a physical server at least to start. It of course has a network connection back through my router to a public IP address supplied by my ISP.

I have a PowerEdge r710 with tons of memory and hard drive capacity running server 2012 hyper-v. This server has multiple gigabit network adapters.

I want to end up with a Hyper-V 2012 standalone server with sbs2011 virtual server with it's own public IP address and 192.168.x.y LAN, a sbs2008 virtual server with it's own public IP address and 192.168.z.z LAN and lastly a SBS2012 Essential with it's own public IP address and 192.168.y.y LAN.

I have all appropriate licensing it's the configuration of the networks that I need some reading material on. I have access to the four static public IP addresses.

Can someone point me to a good quality document for this type of configuration. Thanks

Guzzifrank

Hi,

I have a Windows Server 2008 R2 failover Cluster and I installed a new VM running Windows Server 2012. When I configured the backup to this VM using DPM 2012, the backup is offline (Saved State). 

I've checked with diskshadow and the Hyper-V vss writer, always gives me the same thing, backup to this VM will be using saved state.

Why can't I run an online backup, using snapshot? Is'it a problem with Hyper-V R2 and Windows 2012 Child VM?

Note: I already checked all the conditions why the backup of a VM could be running on saved state and none of them are applicable to my scenario.

Regards,

Carlos.

Michael T. Glenn