Running domain controller as VMs on a hyper-v 2012 cluster

Hi gurus
I have a question. I want to run two VMs on a Hyper-v cluster. I want to make these VMs as domain controller and leverage the cluster. Can I do this? I have not been able find any information on this. The hyper-v is running on windows 2012, but it can be
upgraded to R2 if there are any benefits associated with this.
Any help will be appreciated.
Regards

Hi,
Additional, you can deploy your DC on failover cluster, but we recommend that your clustered servers be member servers. If they are, you need an additional server that acts
as the domain controller in the domain that contains your failover cluster.
And same time, you should attempt to avoid creating potential single points of failure when you plan your virtual domain controller deployment. You can avoid introducing potential
single points of failure by implementing system redundancy. For example, consider the following recommendations while keeping in mind the potential for increases in the cost of administration:
1. Run at least two virtualized domain controllers per domain on different virtualization hosts, which reduces the risk of losing all domain controllers if a single virtualization
host fails.
2. As recommended for other technologies, diversify the hardware (using different CPUs, motherboards, network adapters, or other hardware) on which the domain controllers
are running. Hardware diversification limits the damage that might be caused by a malfunction that is specific to a vendor configuration, a driver, or a single piece or type of hardware.
3. If possible, domain controllers should be running on hardware that is located in different regions of the world. This helps to reduce the impact of a disaster or failure
that affects a site at which the domain controllers are hosted.
4. Maintain physical domain controllers in each of your domains. This mitigates the risk of a virtualization platform malfunction that affects all host systems that use that
platform.
The related KB:
Hyper-V: Using Hyper-V and Failover Clustering
http://technet.microsoft.com/es-es/library/cc732181(v=ws.10).aspx
Running Domain Controllers in Hyper-V
http://technet.microsoft.com/en-us/library/d2cae85b-41ac-497f-8cd1-5fbaa6740ffe(v=ws.10)#usn_and_usn_rollback
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • Can we run domain controller windows 2008 32 bit and additional domain controller on 2003 server

    im my environment we are trying to upgrade from server 2k3 to 2k8, out testing done on server 2k3 to 2k8, but can we run domain controller windows 2008 32 bit and additional domain controller on 2003 server ...kindly suggest
    Nitin Gaurav
    [email protected]

    Yes you can. If you have two 2003 AD servers currently and upgrade one of them to 2008 AD then they'll continue to be able to work together. The domains functional level will remain as 2003 across both servers so at this stage you won't get any benefit from
    the new AD functionality available in 2008.
    Once you've then upgraded the second 2003 server to 2008 you can then upgrade the functionality levels in AD to make it 2008. It's been a while, but I believe it doesn't happen automatically, so once all AD servers have been upgraded you have to go into
    AD and upgrade the functionality levels yourself.

  • ¿Is it possible to upgrade from SCCM 2012 a domain controller in Windows Server 2008 R2 TO 2012 R2?

    Hi all.
    I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
    Thanks.
    Regards.

    Hi all.
    I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
    Thanks.
    Regards.
    Anything is possible if you can script it. You could create a task sequence to do the following (with scripts):
    1. Demote 2008R2 DC to member server
    2. Remove 2008R2 member server from domain
    3. Build new 2012R2 member server and join to domain
    4. Promote 2012R2 member server to DC
    You can do this. However, why would you? Just because you can doesn't mean you should. In my opinion it's more trouble and testing than it's worth. How many times would you need to do this?
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Moving VMs From One Hyper-v 2012 R2 to Another Hyper-v 2012 R2

    Hi everyone, was hoping for some help in something I am confused about
    Currently I have SERVER1 running hyper-v 2012 R2
    I want to move all my VMs (around 20)  to SERVER2 also running Hyper-v 2012 R2
    But I am confused on the best way to do this
    1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
    2) Should I do an export and then import
    3) should I setup replication from Server1 to Server2 and then do a failover?
    4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
    I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
    thanks

    Hi everyone, was hoping for some help in something I am confused about
    Currently I have SERVER1 running hyper-v 2012 R2
    I want to move all my VMs (around 20)  to SERVER2 also running Hyper-v 2012 R2
    But I am confused on the best way to do this
    1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
    2) Should I do an export and then import
    3) should I setup replication from Server1 to Server2 and then do a failover?
    4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
    I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
    thanks
    It all depends on your environment and your current Hyper-V configuration.
    I asume both servers are domain-member of the same domain and don't use SCVMM. If so, then make sure you do the following:
    First enable the "Live Migration" feature in the Hyper-V settings on both Hyper-V Servers.
    Make sure both Hyper-V Servers have a vSwitch configured with the same display name and connectivity. They must be somewhat identical, but not everything. As long as the connectivity is the same.
    Make sure you have a location to store the VM files on SERVER2.
    Then do a Live Migration from SERVER1 to SERVER2, follow the wizard. By using the Hyper-V Manager console on SERVER1.
    NOTE1: Without computer certificates and Kerberos configuration on your Live Migration settings you cannot initiate a Live Migration from the Hyper-V Manager cconsole on SERVER2. With the default configuration, you have to login on (or connect
    to) SERVER1 en then initiate the Live Migration. 
    NOTE2: If you can't configure the vSwitches the same. Then you have to shut down the VMs and do a Quick Migration. Then re-configure the VM network properties and power on the VMs.
    I hope this information will help you goin on. If you need more detailed information use the following link:
    Configure Live Migration and Migrating Virtual Machines without Failover Clustering
    http://technet.microsoft.com/nl-nl/library/jj134199.aspx
    Boudewijn Plomp | BPMi Infrastructure & Security
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

  • Guest VM failover cluster on Hyper-V 2012 Cluster does not work across hosts

    Hi all,
    We are evaluating Hyper-V on Windows Server 2012, and I have bumped in to this problem:
    I have a Exchange 2010SP2 DAG installed on 2 vms in our Hyper-V cluster (a DAG forms a failover cluster, but does not use any shared storage). As long as my vms are on the same host, all is good. However, if I live migrate or shutdown-->move-->start one
    of the guest nodes on another pysical host, it loses connectivity with the cluster. "regular" network is fine across hosts, and I can ping/browse one guest node from the other. I have tried looking for guidance for Exchange on Hyper-V clusters but have not
    been able to find anything.
    According to the Exchange documentation this configuration is supported, so I guess I'm asking for any tips and pointers on where to troubleshoot this.
    regards,
    Trond

    Hi All,
    so some updates...
    We have a ticket logged with Microsoft, more of a check box exercise to reassure the business we're doing the needful.  Anyway, they had us....
    Apply hotfix http://support.microsoft.com/kb/2789968?wa=wsignin1.0  to both guest DAG nodes, which seems pretty random, but they wanted to update the TCP/IP stack...
    There was no change in error, move guest to another Hyper-V node, and the failover cluster, well, fails with the following event ids I the node that fails...
    1564 -File share witness resource 'xxxx)' failed to arbitrate for the file share 'xxx'. Please ensure that file share '\xxx' exists and is accessible by the cluster..
    1069 - Cluster resource 'File Share Witness (xxxxx)' in clustered service or application 'Cluster Group' failed
    1573 - Node xxxx  failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available
    The other node stays up, and the Exchange DB's mounted on that node stay up, the ones mounted on the way that fails failover to the remaining node...
    So we then
    Removed 3 x Nic's in one of the 4 x NIC teams, so, leaving a single NIC in the team (no change)
    Removed one NIC from the LACP group on each Hyper-V host
    Created new Virtual Switch using this simple trunk port NIC on each Hyper-V host
    Moved the DAG nodes to this vSwitch
    Failover cluster works as expected, guest VM's running on separate Hyper-V hosts, when on this vswitch with single NIC
    So Microsoft were keen to close the call, as there scope was, I kid you not, to "consider this issue
    resolved once we are able to find the cause of the above mentioned issue", which we have now done, as in, teaming is the cause... argh.
    But after talking, they are now escalating internally.
    The other thing we are doing, is building Server 2010 Guests, and installing Exchange 2010 SP3, to get a Exchange 2010 DAG running on Server 2010 and see if this has the same issue, as people indicate that this is perhaps not got the same problem.
    Cheers
    Ben
    Name                   : Virtual Machine Network 1
    Members                : {Ethernet, Ethernet 9, Ethernet 7, Ethernet 12}
    TeamNics               : Virtual Machine Network 1
    TeamingMode            : Lacp
    LoadBalancingAlgorithm : HyperVPort
    Status                 : Up
    Name                   : Parent Partition
    Members                : {Ethernet 8, Ethernet 6}
    TeamNics               : Parent Partition
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : TransportPorts
    Status                 : Up
    Name                   : Heartbeat
    Members                : {Ethernet 3, Ethernet 11}
    TeamNics               : Heartbeat
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : TransportPorts
    Status                 : Up
    Name                   : Virtual Machine Network 2
    Members                : {Ethernet 5, Ethernet 10, Ethernet 4}
    TeamNics               : Virtual Machine Network 2
    TeamingMode            : Lacp
    LoadBalancingAlgorithm : HyperVPort
    Status                 : Up
    A Cloud Mechanic.

  • Migration of VMs from WS2012 Hyper-V Hosts Cluster to WS2012 R2 Hyper-V Hosts Cluster

    Hello All,
    We’re currently running our production VMs on a Failover Cluster of Windows Server 2012 Hyper-V Hosts. We’re planning to migrate these VMs to the cluster of
    Windows Server 2012 R2 Hyper-V Hosts.
    I have created a failover cluster of Windows Server 2012 R2 Hyper-V Hosts, and successfully tested the HA of my new test VMs on this new cluster.
    Anyone please tell me the procedure, steps and best practices to migrate these VMs from Windows Server 2012 Hyper-V Hosts to Windows Server 2012 R2 Hyper-V
    Hosts.
    Thank you.
    Regards,
    Hasan Bin Hasib

    Hi Hasan Bin Hasib,
    You can refer the following related cross-version live migration KB:
    Hyper-V: Migration Options
    https://technet.microsoft.com/en-us/library/dn486792.aspx?f=255&MSPPError=-2147217396
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Domain Controller upgrade windows 2008 r2 to windows 2012

    I currently have 3 windows 2008 r2 domain controllers. 1 physical and 2 virtual. I am looking to see what the best upgrade path would be. the physical is the primary and has dhcp and dns services
    Stonecold31666

    See this,
    http://social.technet.microsoft.com/wiki/contents/articles/16797.upgrade-to-active-directory-2012.aspx
    Regards
    Biswajit Biswas
    My
    Blogs|TechnetWiki
    Ninja
    Best regards Biswajit Biswas Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin

  • Domain controller VMs using dynamic VHDx corrupt after power failure

    Over the past couple of months I have experienced 4 dead 2008 R2 SP1 domain controllers after power failure on Hyper-V 2012 hosts. The domain controller VMs will start after power failure and have varying degrees of file system corruption. In each instance
    the corruption has rendered the domain controller unusable. The problem has not occurred with every power failure, but in testing the failure rate has been over 10%.
    The Hyper-v 2012 hosts are as follows:
    Dell PowerEdge r720 with flash backed write cache on Raid controller
    Dell PowerEdge T710 with battery backed write cache on Raid controller
    Dell PowerEdge T310 with a single SATA hard drive and write cache disabled
    Generic system with a single SATA hard drive and write cache disabled
    The VM configuration experiencing corruption is as follows:
    Each VM was created from a base 2008 R2 SP1 syspreped VHDx image template file (40 Gigs)
    The image template was originally created as a VHD and was then converted to a VHDx
    The VHDx file has 512k sectors instead of the native 512e of VHDx files (a result of VHD - VHDx conversion)
    Each VM was assigned 1024 Meg RAM and 1 virtual processor
    The domain controllers were created by promoting the base 2008 r2 install to a DC after base image deployment
    Only one corrupt VM was not running the 2012 integration components. The rest were running current 2012 integration components
    I have done extensive testing on this issue and the problem for me seems to revolve around the VHDx file format. I have managed numerous Hyper-v installations since the original 2008 server version was released and I have never seen corruption like this
    until 2012 and VHDx.
    For the past few days I have been testing fixed sized VHD VMs on a 2012 host and I have not been able to reproduce the data corruption issue. I seem to only be able to reproduce the problem when using dynamic VHDx files. I have not done any testing on 2012
    hosts with fixed size VHDx files or dynamic VHD files.
    It would be great to hear from anybody else experiencing similar issues so that we can compare notes and hopefully get to the bottom of this problem.

    To be honest I was excited to see this fix released, but there are two problems.
    1. The hotfix causes BSOD if you have VLANs with a teamed NIC configuration. I found this out the hard way on a production system. How in the world did this thing get through testing and into automatic updates?
    2. The hotfix does not seem to resolve the issue in my test environment.
    I opened up a case with support and they informed me that they would not provide support for this issue and that I had to open a case with premier support. Premier support informed me that I cannot open a case with them unless I sign a $50,000 per year service
    contract. Is there anywhere to get support on this issue?

  • Hyper-V host fails with "RPC Server unavailable" error when I try to promote Windows Server in virtual machine to a domain controller

    Host: Windows Server 2012 R2 with Hyper-V and RRAS (for Internet over NAT)
    VM: Windows Server 2012 R2 with installed Active Directory Domain Services
    When I open AD DS configuration window (“promote this server to a domain controller”) many services and programs on my host (include Hyper-V, RRAS & Server Manager) fails with RPC Server unavailable error.

    Hello Aleksandr,
    There wasn't any configuration information, ipconfig /all, network setup, etc. So it's difficult to tell.
    More importantly, are you trying to promote the host server? If yes, that is not advised, for one, because it's a Hyper-V server, (not suggested at all), and two, RRAS is installed. RRAS is problematic with any domain controller because it turns it into
    a multihomed domain controller.
    Active Directory communication fails on multihomed domain controllers
    http://support.microsoft.com/kb/272294/
    Multihomed DCs (with more than one unteamed NIC or multiple IPs) with DNS, RRAS, iSCSI, Clustering interfaces, management interfaces, backup interfaces, and/or PPPoE adapters - A multihomed DC is not a recommended configuration, however there are ways to
    configure a DC with registry mods:
    http://blogs.msmvps.com/acefekay/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters/
    7 Reasons not to Make Hyper-V a Domain Controller
    http://www.altaro.com/hyper-v/reasons-not-to-make-hyper-v-a-domain-controller/
    Domain Controller as Hyper-V host
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/4ff14bec-a815-473b-8d2a-33e91e17197b/domain-controller-as-hyperv-host?forum=winserverhyperv
    Networking?
    I don't know how your networking is setup, whether there are multiple NICs on the host server, if they are teamed, if you have the host interface set to allow the operating system to share administration, or if there are separate interfaces for each. Can
    the host OS ping/communicate with the DC virtual machine?
    If there are more than one NIC, you have the choice to team the NICs and share the Teamed NICs for the Hyper-V OS and the VMs, or keep them separate where one is devoted for the Hyper-V OS, and one for the VMs.
    Hyper-V Server VLAN Network Configuration
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/0aa71d2a-ebf9-4a3e-bbf5-94db55339fa2/hyperv-server-vlan-network-configuration?forum=winserverhyperv 
    Recommendation:
    Why not just create another VM DC?
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

  • Problematic issues in installing backup domain controller on Virtual Machine

    Hello,<o:p></o:p>
    I have a physical domain controller - windows Server 2012 R2 Standard installed
    in my domain environment and this is a first root domain controller.
    I have also Hyper-V Server 2012 R2 installed and joined in that domain. 
    Now I want to install an additional (Backup) domain controller as a virtual
    machine hosted on Hyper-V Server. So while promoting VM as a DC all actions and
    steps go well but the problem arise when I press the install button at the end
    of the promotion - installation gets stuck in the process of writing some
    configuration files on first DC and also in the process of replication. Unfortunately
    VM does not promote as a DC and it goes to restart.
    The error event log with - NETLOGON source is logged on the virtual machine as
    well.
    Do you have some suggestions with this issue, or experience how to resolve this..
    Thanks a lot in advance,
    GMG
    <o:p></o:p>

    Now I want to install an additional (Backup) domain controller
    There is no backup DC. All DCs are RW except RODCs.
    I would recommend first checking the health status of the existing DC using
    dcdiag command. Also, please check the IP settings in use: Please make sure that the existing DC has its primary IP address in use and that public DNS servers are set as forwarders and not in IP settings of the DC. For the new DC, please make sure
    that it points to the existing DC as primary DNS server and once promoted you can see the recommendations here to update the configuration: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
    Please also disable temporary all security software in use on the DCs and make sure that needed ports for AD replication and authentication are not blocked or filtered between the DCs.
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Get Active Directory User Last Logon
    Create an Active Directory test domain similar to the production one
    Management of test accounts in an Active Directory production domain - Part I
    Management of test accounts in an Active Directory production domain - Part II
    Management of test accounts in an Active Directory production domain - Part III
    Reset Active Directory user password

  • Remove a domain controller

    I have SBS 2008 with a Windows Server 2008 SP2 server as a second domain controller.  I've added a new 2012 server and made it a domain controller.  I need to demote the 2008 box.  If I run dcpromo, it doesn't detect that it is a domain
    controller and just wants to create a new one.  I notice that the AD DS service is not running, it is disabled.  When I try to start it, it just stops.  dsquery server shows all three as domain controllers.  What is the best way to remove
    this DC?

    I have gone through the thread. Please check the following:
    1. Login to 2012 DC, and check "NTDS Settings" are not seen under 2008 DC in Active Directory Sites and Services snap-in
    2. Ensure that 2012 DC have all FSMO roles
    3. Do your clients point to 2008 DNS for resolution or 2012 DC for resolution? If they use 2008, plan to change them to 2012
    4. Ensure that 2008 DC doesn't run any other services like - WINS, DFS, DHCP, Certificate Services etc.
    5. Run repadmin /replsummary to see replication state for 2008 DC
    Once the above are answered, I would suggest that you clean-up the Active Directory metadata by using NTDSUTIL on 2012 DC.
    If there are any configuration issues with 2008 DC and it is not completely removed from the configuration then you could end up with having Lingering Objects in your environment and it might create more issues.
    I suggest to clean-up AD before Tombstone period kicks in for 2008DC.
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Hyper-V guest SQL 2012 cluster live migration failure

    I have two IBM HX5 nodes connected to IBM DS5300. Hyper-V 2012 cluster was built on blades. In HV cluster was made six virtual machines, connected to DS5300 via HV Virtual SAN. These VMs was formed a guest SQL Cluster. Databases' files are placed on
    DS5300 storage and available through VM FibreChannel Adapters. IBM MPIO Module is installed on all hosts and VMs.
    SQL Server instances work without problem. But! When I try to live migrate SQL VM to another HV node an SQL Instance fails. In SQL error log I see:
    2013-06-19 10:39:44.07 spid1s      Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.07 spid1s      SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.
    2013-06-19 10:39:44.07 spid1s      Write error during log flush.
    2013-06-19 10:39:44.07 spid55      Error: 9001, Severity: 21, State: 4.
    2013-06-19 10:39:44.07 spid55      The log for database 'Admin' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    2013-06-19 10:39:44.07 spid55      Database Admin was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
    2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.33 spid36s     Starting up database 'Admin'.
    2013-06-19 10:39:44.58 spid36s     349 transactions rolled forward in database 'Admin' (6:0). This is an informational message only. No user action is required.
    2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail (failure): alignBuf 0x000000001A75D000, writeSize 0x400, filePos 0x156adc00
    2013-06-19 10:39:44.58 spid36s     blankSize 0x3c0000, blkOffset 0x1056e, fileSeqNo 1313, totBytesWritten 0x0
    2013-06-19 10:39:44.58 spid36s     fcb status 0x42, handle 0x0000000000000BC0, size 262144 pages
    2013-06-19 10:39:44.58 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail: Operating system error 170(The requested resource is in use.) encountered.
    2013-06-19 10:39:44.58 spid36s     Error: 5159, Severity: 24, State: 13.
    2013-06-19 10:39:44.58 spid36s     Operating system error 170(The requested resource is in use.) on file "v:\MSSQL\log\Admin\Log.ldf" during FixupLogTail.
    2013-06-19 10:39:44.58 spid36s     Error: 3414, Severity: 21, State: 1.
    2013-06-19 10:39:44.58 spid36s     An error occurred during recovery, preventing the database 'Admin' (6:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected,
    contact Technical Support.
    In windows system log I see a lot of warnings like this:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Microsoft-Windows-Ntfs" Guid="{3FF37A1C-A68D-4D6E-8C9B-F79E8B16C482}" />
      <EventID>140</EventID>
      <Version>0</Version>
      <Level>3</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000008</Keywords>
      <TimeCreated
    SystemTime="2013-06-19T06:39:44.314400200Z" />
      <EventRecordID>25239</EventRecordID>
      <Correlation
    />
      <Execution
    ProcessID="4620" ThreadID="4284" />
      <Channel>System</Channel>
      <Computer>sql-node-5.local.net</Computer>
      <Security
    UserID="S-1-5-21-796845957-515967899-725345543-17066" />
      </System>
    - <EventData>
      <Data Name="VolumeId">\\?\Volume{752f0849-6201-48e9-8821-7db897a10305}</Data>
      <Data Name="DeviceName">\Device\HarddiskVolume70</Data>
      <Data Name="Error">0x80000011</Data>
      </EventData>
     </Event>
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{752f0849-6201-48e9-8821-7db897a10305}, DeviceName: \Device\HarddiskVolume70.
    ({Device Busy}
    The device is currently busy.)
    There aren't any error or warning in HV hosts.

    Hello,
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
    Thank you for your understanding and support.
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click 
    here.
    Fanny Liu
    TechNet Community Support

  • Hyper-V 2012 VM Placement by SCVMM 2012 SP1

    Hi,
    I'd like to understand the logic behind VM placement in SCVMM 2012 SP1 and a 8 Node Hyper-v 2012 cluster. Each Node has 32GB RAM and each is a completely identical HP DL360.
    Here is the current placement as performed by SCVMM
    Node 1: 1 VM
    Node 2: 2 VM's
    Node 3: 6 VM's
    Node 4: 1 VM
    Node 5: 2 VM's
    Node 6: 7 VM's
    Node 7: 1 VM
    Node 8: 1 VM
    There are 2 x 16GB VM's, the rest of between 2GB and 8GB. Each of the overloaded hosts has a 16GB VM running on it.
    I have a cluster reserve set to 1 Node failure. Why has it decided to favour Node 3 and 6? I appreciate the Maths to work out Node suitability are very complex but this seems rather odd.
    Thanks in advance.
    Eddie

    Hi,
    Please check “Preferred Owners” settings for each clustered resource.
    There are some scenarios to help you understand failover process:
    Scenario 1: If a node or resource fails and the Preferred Owner List has been defined, the Cluster Service fails the Group to the next available node in the Node List. The Node List is composed of the Preferred Owners List followed by the remaining nodes
    arranged by their Node ID. The Node ID is defined when a node is joined to a cluster or if a node is evicted or and re-added.
    Scenario 2A: If a resource fails and the Preferred Owner List is not set, the Group follows a Node List much like it did in Scenario 1. The Node List is built only from the Node ID. Upon a node or resource failure, resources follow a downward path failing
    to the subsequent node in the Node List. When it reaches the last listed node in the Node List, it starts with the first node in the Node List.
    Scenario 2B: If a node fails and the Preferred Owner List is not set for a group on that node, then an available node will be selected randomly for the group to be moved to. This will distribute the groups among the available nodes.
    Scenario 3: If a Cluster administrator manually chooses Move group and selects Best Possible and the Preferred Owner List is configured, the Group will always start at the top of the Node List. As in Scenario 1, the Node List is composed of the Preferred
    Owner List and the installation order.
    Scenario 4: If, as Cluster administrator, you manually choose Move group and you select Best Possible and the Preferred Owner List is not configured, an active node is chosen randomly to host the group. Without the Preferred Owner List configured, it is
    possible that a Group may move to a Node that is already running several other Groups.
    We recommend that you configure the Preferred Owner list on a large node cluster if the load between nodes is significantly different or if the nodes are not homogeneous.
    For more information please refer to following MS articles:
    Failover behavior on clusters of three or more nodes
    http://support.microsoft.com/kb/299631
    Preferred Owners in a Cluster
    http://blogs.msdn.com/b/clustering/archive/2008/10/14/9000092.aspx
    Lawrence
    TechNet Community Support

  • Running 2008 R2 DCs - Can we use ADFS from 2012 R2?

    Do we have to upgrade our Active Directory DCs to 2012 R2 in order to use ADFS in 2012 R2?  2012R2 uses ADFS 3.0, right?  And that requires GMSA accounts to work in a farm if I understand it right.  Does 2008R2 support GMSAs?  I cannot
    find anything on it and powershell commands do not work for creating GMSA accounts.  
    Do I need to update all our DCs to 2012 R2 before doing ADFS in 2012 R2?  We currently do not use ADFS, and I'd like to stick with the latest and greatest if possible... 

    Hi,
    Yes, ADFS 3.0 needs to be installed on Windows Server 2012 R2, but you don’t need to upgrade all your DCs, you can upgrade one of them in order to use ADFS 3.0.
    In addition, gMSA is a new object class after AD schema is extended for Windows Server 2012, which means you need to have at least one Windows 2012 Domain Controller and at least one Windows Server 2012 or Windows 8 domain member
    to use the gMSA.
    Here are some related links below I suggest you refer to:
    ADFS and Domain Functional Level
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/5cc0e898-eae2-46ce-8491-5ccf61380423/adfs-and-domain-functional-level?forum=winserverDS
    Windows Server 2012: Group Managed Service Accounts
    http://blogs.technet.com/b/askpfeplat/archive/2012/12/17/windows-server-2012-group-managed-service-accounts.aspx
    ADFS 2.0 compatibility with ADFS 3.0
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/45b579ca-ba3b-49e6-8cbd-285516de6cc3/adfs-20-compatibility-with-adfs-30?forum=winserverDS
    Best Regards,
    Amy

  • Windows Domain Controller on Windows Server 2012 R2: Hyper-V roaming profiles not loading due to slow connection

    I have racked my brain and done everything that I know to do for about two weeks now.  I am setting up a new system at our fire department and I am having the worst luck with getting the workstations to login to the domain controller with roaming
    profiles.  It keeps telling me that the roaming profile could not be loaded because of a slow connection.  These are workstations that are connected directly to the switch that the DC is connected to.  I have tried multiple connections regarding
    the layout (DC into the router, router into the switch).  The router is a Cisco RV220W.  I have two VLANS, one for public and one for private domain.  The Private VLAN has DHCP turned off since I am providing it through the DC.  I currently
    have a connection from the Private VLAN going to the unmanaged switch that the workstations and server are plugged into.
    The server is a Dell PowerEdge R420 that has 6 NIC ports (1 dual port and 1 quad port).  I have a virtual switch setup on Hyper-V for an external port (let's say Card 2 Port 3) that is assigned to the WS 2012R2 Domain Controller.  The DC can see
    the internet fine and the workstations can connect to the shared folders on the server.  I can retrieve files by just using the computer name or FQDN.  The DC is also running DNS and DHCP.  The DNS has the _msdcs setup from when I installed
    the active directory role.  I have attempted to assign static IP addresses to the workstations:
    IP:                     10.0.0.80
    Subnet:             255.255.255.0
    IPV4 Gateway:  10.0.0.1
    IPV4 DNS:        10.0.0.12
    I've attempted "append the specific DNS suffix", I've "registered the connection in DNS", I've used "use this connections suffix in DNS registration".
    The server is assigned:
    IP:                     10.0.0.12
    Subnet:             255.255.255.0
    IPV4 Gateway:  10.0.0.1
    IPV4 DNS:         10.0.0.12
    The DNS entries have forwarders that forward to my ISP DNS servers for lookup
    I've enabled and disabled DHCP, I've installed a new VM just to create another DC to make sure that I didn't goof up when I created it.
    I've lost my patience with this project and am sinking fast.  Can someone please offer some advice as to what I've done wrong?  I've created this exact scenario at work many times but, I've never done it with Windows Server 2012.  Is this
    possibly something to do with the Dell PowerEdge server (Generation 12) with the SR-IOV?  I am going to attempt to work on it some more tomorrow when I get over there.  I think there may be an issue with the SR-IOV not being enabled on the machine
    through the Dell Bios.  Would the SR-IOV really cause the workstations to report a slow connection?  When I login at the domain controller the roaming profiles and folder redirection work fine so, I know the GPO settings are correct.  I don't
    have "ignore slow connections" or any of those GPO's set.  I need to get it working the correct way so, I didn't want to fool the server when there is another underlying problem.  Any help that someone can offer, I am more than willing
    to listen.  If you need more information, please ask.
    Thanks,
    Jay

    So, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
    post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
    virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
    Im disappointed in MS right now.

Maybe you are looking for