DHCP Failover feature in Windows 2012

I am planning to configure DHCP on windows 2012 failover (Load balanced)mode.Just want to confirm two things:
1.How will the DCHP address be assigned to clients incase the DHCP Servers loose communication between them.
2.Regarding IP helpers that i need to put onto my network switches would it be Ips for both the server or does configuration of  failover feature uses single IP (as is used in cluster config)

Hi,
Sorry for the delay. I think we need to get more people monitoring this forum :)
Your questions are answered in documentation here:
http://technet.microsoft.com/en-us/library/dn338978.aspx.
From DHCP Failover Modes:
In load balancing mode, when a DHCP server loses contact with its failover partner it will begin granting leases to all DHCP clients. If it receives a lease renewal request from a DHCP client that is assigned to its failover partner, it will temporarily
renew the same IP address lease for the duration of the MCLT. If it receives a request from a client that was not previously assigned a lease, it will grant a new lease from its free IP address pool until this is exhausted, and then it will begin using the
free IP address pool of its failover partner. If the DHCP server enters a partner down state, it will wait for the MCLT duration and then assume responsibility for 100% of the IP address pool.
From DHCP Failover Architecture:
When you deploy DHCP failover, a single DHCP relay address might not be sufficient, since DHCP clients must always be able to communicate with both the primary DHCP server and the failover partner server. If both DHCP servers are located on a different subnet
than DHCP clients, this requires at least two DHCP relay agents. For example:
ip helper-address 10.0.1.1
ip helper-address 10.0.1.2
In this example, both DHCP servers are on the same subnet (10.0.1.0/24). The primary DHCP server’s IP address is 10.0.1.1 and 10.0.1.2 is the IP address for the failover partner server. If both DHCP servers are located on the same subnet, you can also configure
the subnet broadcast address (ex: 10.0.1.255) as a single DHCP relay. The use of a subnet broadcast address as a single DHCP relay is not possible if DHCP servers are located on separate subnets.
-Greg

Similar Messages

  • DHCP failover from 2003 to 2012?

    I know 2012 has some new DHCP failover features built in but our DC's are still 2003. :(
    I'm looking for suggestions / options on how to handle this scenario.  Upgrading all of the DC's isn't an option at the moment.

    Hi,
    The question is a little broad. How many 2012 servers are you planning to introduce and are all your DCs also DHCP servers? Are you upgrading in place or migrating to new hardware? If some DHCP servers are not also DCs I would focus on these first.
    See this topic for some suggestions about how to migrate the configuration once you are ready:
    Migrate to DHCP Failover.
    If all your DHCP servers are also DCs I suggest adding a 2012 server to the environment and making it only a DHCP server, then add this DHCP server to your existing domain. Keep in mind that adding a 2012 server or 2012 R2 server to a 2003 domain will automatically
    update the schema. I don't know if this will have any consequences for your environment - probably not - but I wanted to make you aware that this will happen.
    -Greg

  • DHCP Failover in Windows 2008 R2 and Windows 2012 R2 Environment

    Hi Everyone,
    We are trying to implement DHCP failover in our environment. Our IT Infrastructure consists of 4 – windows server 2008 R2 servers and 7 – Windows Server 2012 servers; 1 Main Office with 2 – DC’s and 9 branch/remote offices with one DNS server in every remote
    office. All the DNS servers have 2 scopes defined on them for VOICE and Data with different Subnets.
    What would be the best method to implement failover in 2008 R2 – Windows Failover Cluster or Split scope? And how to implement DHCP Failover in Windows Server 2012 R2?
    Please let me know if you need more information.
    Thank you for your help!
    -kN

    Hi,
    if you can choose between 2008 R2 and 2012 R2 than go with 2012 R2 it is easy to create a DHCP failover there. Actually that is one of the new features of Windows 2012.
    With Server 2012 you setup your fist DHCP server with the scopes you want to setup. Than you install the second 2012 server with DHCP role and authorized. If you have done this you going back to your first server, where you already configured your scopes.
    Now right click onto the scope you want to setup for failover and select 'Configure Failover'. You can than set it up as kind of split scope (Load balance Mode) or as real fail over setup (Hot Standby). In Load balance Mode you can configure the balance of
    IP addresses between the both servers, like primary has 60% IP addresses and secondary has 40%.
    With Server 2008 R2 the easiest configuration is split scope. But here it depends how many IP leases you will max have and if you can absorb if one of the server is going down. Lets say you have 50 DHCP leases max, than sure, set it up as split scope. But
    if you have 200 DHCP clients, than I would go with failover cluster. At the end it depends on your environment.
    Sven

  • DHCP Mirgation from 2008 to 2012

    Hi,
    I am migrating DHCP server 2008 to 2012
    Environment. Please let me know the Best practice of migration.
    I have configured DHCP failover in Windows 2008 R2
    Environment.
    Any help would be very grateful.
    Thankx & Regards,
    DD6

    Hi,
    This type of question is already running in technet portal.
    http://social.technet.microsoft.com/Forums/en-US/fed16caa-fb53-4037-a578-5f8dfc61e4e3/dhcp-failover-migrate-dhcp-server-to-another-machine?forum=winservergen
    Process of Migration DHCP Server 2008R2 to Windows 2012
    • Firstly, you can disable the DHCP role in Windows Server 2008 R2. However, if the Windows Server 2012 is down, the clients cannot renew their IP lease duration and obtain IP address.
    Therefore, it is recommended to leave the DHCP role in Windows Server 2008 R2 and deploy high availability. Windows Server 2012 brings the new feature: DHCP failover. However it requires both DHCP Servers are Windows Server 2012. Consider another Server
    is Windows Server 2008 R2, we have to choose one of the following:
    >> DHCP in a Windows failover cluster. This option places the DHCP server in a cluster with an additional server configured with the DHCP service that assumes the load if the primary DHCP server fails. The clustering deployment option uses a single
    shared storage. This makes the storage a single point of failure, and requires additional investment in redundancy for storage. In addition, clustering involves relatively complex setup and maintenance.
    >> Split scope DHCP. Split scope DHCP uses two independent DHCP servers that share responsibility for a scope. Typically 70% of the addresses in the scope are assigned to the primary server and the remaining 30% are assigned to the backup server.
    If clients cannot reach the primary server then they can get an IP configuration from the secondary server. Split scope deployment does not provide IP address continuity and is unusable in scenarios where the scope is already running at high utilization of
    address space, which is very common with Internet Protocol version 4 (IPv4).
    More references:
    Step-by-Step: Configure DHCP for Failover (Windows
    Server 2012)
    How
    to configure split-scope using wizard
    DHCP
    Step-by-Step Guide: Demonstrate DHCP Split Scope with Delay on a Secondary Server in a Test Lab
    DHCP
    Step-by-Step Guide: Demonstrate DHCP Failover – Clustering in a Test Lab
    If you need snap shot of migration then follow these links.
    http://blogs.technet.com/b/canitpro/archive/2013/04/29/step-by-step-migration-of-dhcp-from-windows-server-2003-to-windows-server-2012.aspx
    http://www.mehrban.net/migrating-dhcp-from-windows-2008-to-windows-2012
    Deepak Kotian. MCP, MCTS, MCITP Exchange 2010 Ent. Administrator Disclaimer: Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognizes useful
    contributions. Thanks! All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

  • DHCP Failover / Migrate DHCP Server to another Machine

    We have DHCP Server Installed in Domain Controller with Windows Server 2008 R2 Based OS.
    I have Checked that there is no way to make the DHCP Failover in Server 2008 R2.
    Can anyone help me to get some level of Failover in DHCP?
    or
    If I want to migrate the DHCP to Server 2012 what is the Best Practice?

    Hello,
    There is no big challenge for configuring DHCP failover in Windows 2008 platform. Kindly go through with this link for configuring DHCP failover. I am sure it will help you to completing your task.
    1> Step-by-Step: Configure DHCP for Failover
    http://technet.microsoft.com/en-us/library/hh831385.aspx
    2> DHCP Step-by-Step Guide: Demonstrate DHCP Failover – Clustering in a Test Lab
    http://technet.microsoft.com/en-us/library/ee405263(v=ws.10).aspx
    Process of Migration DHCP Server 2008R2 to Windows 2012
    • Firstly, you can disable the DHCP role in Windows Server 2008 R2. However, if the Windows Server 2012 is down, the clients cannot renew their IP lease duration and obtain IP address.
    Therefore, it is recommended to leave the DHCP role in Windows Server 2008 R2 and deploy high availability. Windows Server 2012 brings the new feature: DHCP failover. However it requires both DHCP Servers are Windows Server 2012. Consider another Server
    is Windows Server 2008 R2, we have to choose one of the following:
    >> DHCP in a Windows failover cluster. This option places the DHCP server in a cluster with an additional server configured with the DHCP service that assumes the load if the primary DHCP server fails. The clustering deployment option uses
    a single shared storage. This makes the storage a single point of failure, and requires additional investment in redundancy for storage. In addition, clustering involves relatively complex setup and maintenance.
    >> Split scope DHCP. Split scope DHCP uses two independent DHCP servers that share responsibility for a scope. Typically 70% of the addresses in the scope are assigned to the primary server and the remaining 30% are assigned to the backup server.
    If clients cannot reach the primary server then they can get an IP configuration from the secondary server. Split scope deployment does not provide IP address continuity and is unusable in scenarios where the scope is already running at high utilization of
    address space, which is very common with Internet Protocol version 4 (IPv4).
    More references:
    Step-by-Step: Configure DHCP for Failover (Windows
    Server 2012)
    How
    to configure split-scope using wizard
    DHCP
    Step-by-Step Guide: Demonstrate DHCP Split Scope with Delay on a Secondary Server in a Test Lab
    DHCP
    Step-by-Step Guide: Demonstrate DHCP Failover – Clustering in a Test Lab
    If you need snap shot of migration then follow these links.
    http://blogs.technet.com/b/canitpro/archive/2013/04/29/step-by-step-migration-of-dhcp-from-windows-server-2003-to-windows-server-2012.aspx
    http://www.mehrban.net/migrating-dhcp-from-windows-2008-to-windows-2012
    Deepak Kotian.
    MCP, MCTS, MCITP Exchange 2010 Ent. Administrator
    Disclaimer:
    Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!
    All the opinions expressed here is mine. This posting is provided "AS IS" with no
    warranties or guarantees and confers no rights.

  • Can I failover a DHCP failover server?

    Greetings,
    I'm in the process of putting together an enterprise wide DHCP design.  I'm planning on leveraging the hot failover feature in Server 2012.  I'll be using a hub-and-spoke topology with a server in our primary datacenter acting as the failover partner
    for all the DHCP servers at branch offices.
    My question is can I failover the failover server?  Basically can I configure the failover partner for all the primary servers to fail over to yet another DHCP server in a secondary datacenter?
    Thanks!

    One line answer to your question is no. Since a given scope on a DHCP server can be part of one and only one failover relationship and given that all the scopes on your Hub DHCP server are part of different failover relationships distributed across
    your spoke servers you cannot make those scopes a part of failover relationship with another DHCP Server.
    Having said that, in case your hub DHCP Server fails the spoke DHCP servers can take over. Yet if you are concerned about data loss then you can have appropriate disaster recovery\backup solutions in place to safeguard the DHCP data on the hub server.

  • DHCP Failover Windows 2012

    What is the OS Flavour required for doing DHCP failover in Windows 2012. Is it Standard Edition or Data Centre Edition?

    The requirements are mentioned here: http://technet.microsoft.com/en-gb/library/dn338982.aspx
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Windows 2012 DHCP Failover "Lost contact with partner"

    We have stood up a pair of Windows 2012 DHCP servers and configured DHCP failover (in Load Balancing mode) as per the Microsoft Technet article.  The two servers are on the same subnet, and time is in sync between them.  Almost immediately after
    configuring scopes to failover, one node loses contact with the other, and the alternate node goes to failover mode "Recover".
    We have restarted both servers and services.  Both DHCP servers show as available.  Clicking "Replicate Failover Scopes" completes successfully with no errors, and the only two warnings in the Event Log are about credentials for Dynamic
    DNS updates and a dynamic IPv6 address (which we don't use at all.)
    How come they can replicate, but have "lost contact"; and how do we get the one out of "Recover" mode?

    You should see Recover state only if one of the DHCP server actually went down and came back up. In this case the server which comes back up would be in Recover state but will transition to Recover_Wait state and come back to Normal after it syncs it
    leases. This should be relatively quickly. Did your servers continue to remain in the Lost Contact...\Recover state for long.
    Did you see any events in the DHCP Server admin channel
    Microsoft\Windows\DHCP Server\Admin.
    You can also enable AuditLogs (Microsoft\Windows\DHCP
    Server\AuditLogs) which logs all the server to server messages. You can enable the log by right clicking on
    Microsoft\Windows\DHCP Server. View->Show Analytical and Debug Logs. This will show the
    Microsoft\Windows\DHCP Server\AuditLogs in event viewer. You can then right click and enable the log and see if there are any failures
    being logged there.

  • How to test Windows 2012 R2 DHCP Failover without shutting down the service?

    How can I test the Win2012R2 DHCP Failover?
    There is a command or script, that i could use to test if DHCP failover is working properly?
    How to monitor the sync of the objects?
    How to make sure that it will do the job, if required?
    Or i have to really stop DHCP server main server and see the failover?

    Hello,
    you have to keep in mind that this has ONLY effect for machines that request during the downtime a lease. So if your lease time is for example 8 hours a computer will ask after 4 hours for the renewal of the lease.
    Means there is no problem for running machines during the test. You just need a computer to start after the service is shutdown on the first DHCP server, should take only some minutes to check if the fail over works. Then you could already start the service
    again if you see the lease on the new server.
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

    I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

    Hi KamarasJaranger,
    According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
    and refer to the
    PDF file.
    1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
    2.Discover target portals.
    3.Connect targets and configuring Multipathing.
    4.Initialize and format the Disks.
    5.Verify the Storage Replication Process.
    6.Run the Failover Cluster Validation Wizard.
    7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
    8.Tune Cluster Heartbeat Settings.
    9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
    10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
    11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
    12.Test application connectivity.
    Regards,
    Michelle Li

  • FTP in Windows 2012 Failover Cluster

    Hi,
    Understand that Windows 2012 is having much improved Failover Clustering features,however i have faced issues when i configured FTP in Windows 2012 Failover Cluster.
    1) As per the process configured the shared disk for FTP data path.
    2)Installaed FTP feature in both Nodes of Clustert
    3)Finally created the Generic Service in Cluster Roles for FTP Service.
    After the configuration i found everything working fine but when i try to failover the FTP role found that FTP resource is not moving smoothly. Also i observed that Microsoft FTP service gets in to "starting" mode in the destination Node. To run the FTP
    resource Microsft FTP service should be in Started mode.
    This happens only when we try to failover else it works fine if you start freshly.
    Have any one tried this? Any clue about such issue ?
    Regards:Mahesh

    Hi,
    In earlier versions of Internet Information Services, Microsoft provided generic resource monitor components to support high availability Web server instances by using the Microsoft Clustering infrastructure. However, custom code was needed to fully realize
    the potential of this solution. Also, the generic scripts that Microsoft provided did not satisfy customer needs.
    From IIS 7 to configure IIS in a clustered environment by using Windows Server failover clustering, you have to use a custom (scripting) code to enable such a high availability scenario.
    Note:
    We recommend that administrators carefully evaluate the use of Network Load Balancing (NLB) instead of using failover clustering as the primary and preferred method for improving the scalability and availability of Web applications that have multiple servers
    that are running new IIS (from IIS 7) . One benefit of NLB is that all servers can actively participate in the concurrent handling of incoming HTTP requests. Another benefit is that in an NLB IIS environment, it can be much easier to support rolling updates
    and rollbacks while still providing high availability of Web applications.
    To configure high availability for IIS FTP servers using Failover Clustering:
    Install the Web Server role on all cluster nodes.
    Install the Failover Clustering feature on all cluster nodes and create the cluster.
    Set up a file share that will be used for IIS shared configuration
    Configure the IIS shared configuration on all cluster nodes
    Configure Offline Files for IIS Shared Configuration on all cluster nodes
    Configure the FTP site and specify the location of its content on one cluster node
    Configure high availability for your FTP site by creating a generic script in Failover Cluster Manager
    For more detailed configuration procedure please refer to following MS articles:
    Note: I didn’t find IIS 8 in Windows Server 2012 failover cluster configuration guide, below guide was published for II 7 in Windows server 2008 and Windows Server 2008 R2, but its basis configuration procedures should also apply to Windows Server 2012.
    How to configure FTP 7.5 for IIS 7.0 in a Windows Server 2008 failover cluster
    http://support.microsoft.com/kb/974603
    Configure IIS Network Load Balancing
    http://www.iis.net/learn/web-hosting/configuring-servers-in-the-windows-web-platform/network-load-balancing
    Deploying IIS on a Failover Cluster
    http://blogs.msdn.com/b/clustering/archive/2009/06/01/9674799.aspx
    Hope this helps!
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Lawrence
    TechNet Community Support

  • Guest two node Failover Cluster with SAS HBA and Windows 2012 R1

    Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
    LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
    disks, or i have to use iSCSI to present the disks to my cluster?
    Thank you in advance, George
      

    Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
    LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
    disks, or i have to use iSCSI to present the disks to my cluster?
    Thank you in advance, George
    1) Update to R2 and use shared VHDX which is a better way to go. See:
    Shared VHDX
    http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
    Clustering
    Options
    http://blogs.technet.com/b/josebda/archive/2013/07/31/windows-server-2012-r2-storage-step-by-step-with-storage-spaces-smb-scale-out-and-shared-vhdx-virtual.aspx
    2) If you want to stick with non-R2 (which is a BAD idea b/c tons of reasons) you can spawn an iSCSI target on top of your storage, make it clustered and make it provide LUs to your guest VMs. See:
    iSCSI Target in Failover
    http://technet.microsoft.com/en-us/library/gg232632(v=ws.10).aspx
    iSCSI Target Failover Step-by-Step
    http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
    3) Use third-party software providing clustered storage (active-active) out-of-box. 
    I would strongly recommend to upgrade to R2 and use shared VHDX.
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • DHCP Failover Server 2012

    Hi,
    I have a Problem with DHCP Failover in Windows Server 2012
    We configured 2 Windows Server 2012 with DHCP Role and created a Scope with loadbalancing algorithm.
    The Problem is, that the two DHCP Servers Show different statistic Information. DHCP 1 has 254 addresses and 218 in use. DHCP Server 2 has 254 addressses and 187 in use.
    We found situations when one DHCP Server has no available IP addresses and the other one has about 40% available addresses.
    Why do the Servers have different available address spaces ? We have one scope with one class c net, 254 addresses.
    Our Szenario is with this config not high available, cause of sometimes running out of IP addresses on one DHCP Server.
    Thanks for help
    Björn
    Björn Schiemann LemonTec IT Systems KG htttp://www.lemontec.de

    Hi Bjoern,
    Would you please provide us your detailed load balance configurations.
    In load-balance mode of operation both the servers respond to client requests. Here’s how the servers ensure the distribution of client requests between themselves:
    Each DHCP server on receiving the client request calculates hash of the MAC address in the client request as per hashing algorithm specified in RFC 3074. Each server hashes any MAC address
    to a value between 1 and 256. If the load distribution ratio between the 2 servers is left at the default of 50:50; and if the hash of the MAC address falls between 1 and 128 then the first server will respond to the client request else if the hash is any
    value between 129 and 256, the other server responds to the client. This ensures that only one server responds for a specific client. If the load distribution ratio has been changed by the admin to a different value, the distribution of hash buckets would
    be in that proportion. The admin does not need to configure the MAC addresses on any server configuration a-priori.
    Quote from DHCP Failover Load Balance Mode
    http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx
    In addition, I notice that you have a Class C network for the scope, why does each DHCP server have 254 IP address available?
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Unable to install windows features on windows server 2012 core datacenter

    If I attempt to install, remove, or get windows features via powershell in windows server 2012 core datacenter I get the following error:
    PS C:\Users\BB> Invoke-Command -ComputerName CORE1 {Install-WindowsFeature Web-CertProvider}
    The given key was not present in the dictionary.
        + CategoryInfo          : NotSpecified: (:) [Install-WindowsFeature], KeyN
       otFoundException
        + FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,
       Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
        + PSComputerName        : CORE1
    I get the same error regardless of weather I use install-windowsfeature, remove-windowsfeature or get-windowsfeature. I've tried it on the server, and remotely.
    I've also tried managing the computer remotely using another windows 2012 server using the server manager GUI. That causes the server manager to crash with the following error:
    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: servermanager.exe
      Problem Signature 02: 6.2.9200.16384
      Problem Signature 03: 50107b22
      Problem Signature 04: mscorlib
      Problem Signature 05: 4.0.30319.17929
      Problem Signature 06: 4ffa57ca
      Problem Signature 07: 210b
      Problem Signature 08: c
      Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
      OS Version: 6.2.9200.2.0.0.400.8
      Locale ID: 1033
      Additional Information 1: 7a77
      Additional Information 2: 7a77983701ecc7870d72712ffa4c3c88
      Additional Information 3: 0b4b
      Additional Information 4: 0b4b0ba1592ebbc56adc05832bb92aa6
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=190175
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    The server is running all Microsoft updates. Rebooting doesn't help. I've checked the event logs and I don't see anything relevant.
    Help!
    Thanks
    Brad

    Hi,
    I would like to suggest you first run get-windowsfeature command on the core locally not remotely. And if it works, then try to remote run it.
     Invoke-Command -ComputerName CORE1 {get-WindowsFeature }
    Regards,
    Yan Li
    Cataleya Li
    TechNet Community Support

  • Windows 2012 Failover Cluster - File server role (vCO)

    Hi, 
    I wonder if anybody can shed some light on a query i have.
    A windows 2012 failover cluster will be built in AD domain example.uk.  Cluster File server roles will be created and will reside in this domain also.
    We also have a requirement to run a cluster file server role in the child domain off secure.example.uk.  Is this possible? or do the file server roles and related vCO's have to reside in the same domain as the cluster (CNO).
    I know the CNO can be used to create the VCO but could a prestage a VCO in the child domain of secure.example.uk.
    Mark

    Hi Mark,
    By default CNO will create 
    VCO automatically in default domain computer OU, we generally use the
    KISS principle to place the CNO and VCO to the same OU, and as far as I know there no known design document indicate the VCO can be placed in different domain, therefore I suggest you place the CNO and V CO at same OU.
    More information:
    When Creating a New Resource or Role in Windows Server 2012 R2 Failover Cluster, the Network Name Fails to Come Online or Failed to Create Associated Computer Object in Domain
    http://blogs.technet.com/b/askpfeplat/archive/2014/11/17/when-creating-a-new-resource-or-role-in-windows-server-2012-r2-failover-cluster-the-network-name-fails-to-come-online-or-failed-to-create-associated-computer-object-in-domain.aspx
    CNO Blog Series: Increasing Awareness around the Cluster Name Object (CNO)
    http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
    How to Create a Cluster in a Restrictive Active Directory Environment
    http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
    Prestage Cluster Computer Objects in Active Directory Domain Services
    https://technet.microsoft.com/en-us/library/dn466519.aspx
    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]

Maybe you are looking for