Licensing Windows Server in a Cluster (Passive Node)

Do I need to purchase a Windows Server license for passive nodes in a Fail-Over cluster? Passive means it is running behind a VIP but no users are accessing the passive node as long as the active node is up and running. Both nodes are
identical (running the same version and edition of Windows server). Please tell me if this differs for version 2008,2003 or even for Ent, Data Center or Standard editions.

Hello,
I confirm that for Windows Server Software you need to license each instance(Active and passive).
on this link: http://bit.ly/1kxHZEH you can download the Microsoft document for confirmation. you have the following on th edocument:
Clustering, Failing Over, and Moving Instances
Two common scenarios for higher availability and dynamic datacenters involve:
Running the same workload simultaneously on two servers, or
Only run the workload during maintenance.
Running a workload on a primary server and periodically moving it to a second server due to a failure, load balancing, patching, or planned downtime.
In both scenarios, regardless of whether the workloads are running in physical or virtual OSEs, each server must have the appropriate number of licenses assigned to it prior to the workload running
on it. This holds true regardless of whether you plan the workload to:
Always run on a single server.
Run in parallel on the server as a backup when the primary server fails.
Run the workload if the primary server is down.
Load balance when the primary server has high use.
thanks
diramoh

Similar Messages

  • Windows Server 2008 R2 SP1 2-Node cluster - Replace failed node

    Hi -  I have a two node Windows Server 2008 R2 SP1 fail-over cluster (DHCP, File, Print) where one of the nodes have failed beyond recovery. What I would like to do is to evict the failed cluster node and install a new machine with Windows Server 2008
    R2  SP1 and re use the same name and Ip adress and then join this machine as a node in the cluster. 
    Is there any recommended steps to do this, i'm mostly thinking about the part of re-using the same name and ip address for the new node? (e.g. is there any cleanup more than evict the node?)
    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

    Hi,
    I agree with Noah Sparks, you can evict the corrupt node, if you reinstall then add the new server system you can just join it to cluster, it shouldn’t any error.
     If you have seen some the evicted node rejoin to cluster meet “The cluster node is already a member of the cluster” error, it may need pack the KB2549472
    hotfix.
    The related KB:
    How to Evict a Node from a Windows Server 2008 Failover Cluster
    http://technet.microsoft.com/en-us/library/bb676524(v=exchg.80).aspx
    Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2
    http://support.microsoft.com/kb/2549472
    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.

  • Windows 2012 Server multinode failover cluster (6 nodes)

    Dear All,
    We are facing problem of Huge time takes for cluster validation test on IBM Blade Server with Storage. The details are given below. 
    Escalated with IBM OEM, confirmed that "there is no hardware issue with Server and storage, Please take support from OS (Microsoft) OEM as 2 node validation test is working fine".   
    Server : IBM BladeCenter S-HS23
    OS : Windows 2012 X64 Datacenter Edition
    MPIO.SYS Version: Default came from OS
    Note : Failover cluster validation test is successful on 2 nodes in 15 min with 5 shared volumes between 2 nodes and also between set of 2 on other 6 nodes.
    When we are running validation test on 6 nodes its taking 30 min in list and more than 45 min potential cluster disk.
    Thanks in adv for support from your end....
    T & R,
    Kamlesh
    kamlesh

    Hello,
    I'd ask in the
    High Availability (Clustering) subforum of the Windows Server forums.
    Karl
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
    My Blog:http://unlockpowershell.wordpress.com
    My Book:Windows PowerShell 2.0 Bible
    My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

  • Windows Server 2008 failover cluster in VirtualBox

    Hi,
    I'm a Windows NT student and I need help with understanding how to do clustering using multiple Windows 2008 R2 Enterprise servers in VirtualBox 4.3.8. I have a Windows 7 host computer. I was wondering if someone could provide clearly detailed step-by-step
    directions (ex. Click this, then click that) on what I need to do prior to clustering, as well as starting the clustering process. Please ask if you need additional information. 
    Thank You.

    I'm sorry. I'm such a noob. Should I have 3 virtual machines, where one is the domain controller and the other 2 are nodes? Or is it ok to just have 2 virtual machines?
    It's optional. You just need your both cluster nodes (VMs) belong to the same domain. It can be own domain serviced by your private VM or it can be "external" one. See:
    Using Guest Clustering for High Availability
    http://technet.microsoft.com/en-us/library/dn440540.aspx
    Active Directory domain requirements
    Failover clusters require that nodes of the same cluster are members of the same Active Directory domain. However, there is no requirement that a guest cluster belongs to the same Active Directory
    domain as the physical hosts on which the virtual machines are running.
    Also you'll need some shared storage. See (same URL as above):
    Storage options
    The following tables lists the storage types that you can use to provide shared storage for a guest cluster.
    Storage Type
    Description
    Shared virtual hard disk
    New in Windows Server 2012 R2, you can configure multiple virtual machines to connect to and use a single virtual hard disk (.vhdx) file. Each virtual machine can access the virtual hard disk
    just like servers would connect to the same LUN in a storage area network (SAN). For more information, see Deploy a Guest Cluster Using a Shared Virtual
    Hard Disk.
    Virtual Fibre Channel
    Introduced in Windows Server 2012, virtual Fibre Channel enables you to connect virtual machines to LUNs on a Fibre Channel SAN. For more information, see Hyper-V
    Virtual Fibre Channel Overview.
    iSCSI
    The iSCSI initiator inside a virtual machine enables you to connect over the network to an iSCSI target. For more information, see iSCSI
    Target Block Storage Overview and the blog post Introduction of iSCSI Target
    in Windows Server 2012.
    Shared VHDX is out as you don't have proper software (Windows 7 is not supported as a host and Windows 2008 R2 does not support shared VHDX as a guest), virtual Fibre Channel is out as you again don't have Windows Server 2012 R2 (and don't have any FC gear).
    So iSCSI is your only choice. Either spawn dedicated Windows (or other OS if you like UNIX) VM with iSCSI stack or use third-party Windows software running on your host. Windows Server 2008 R2 does not have iSCSI target embedded so you can get it here:
    MSFT iSCSI Target 3.3 Download
    http://www.microsoft.com/en-us/download/details.aspx?id=19867
    Good luck and happy clustering :)
    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.

  • Windows Server 2012 Failover Cluster (Hyper-V) Event Id 1196

    Hi All,
    I just installed Failover Cluster for Hyper-V on windows server 2012 with 2 nodes. I got following error event id 1196.
    reCreated / deleted Cluster Host A record on DNS and nothing happened.
    Any suggestion?
    There is similar topic but it couldnt help
    http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/2ad0afaf-8d86-4f16-b748-49bf9ac447a3/
    Regards

    Hi,
    You may refer to this article to troubleshoot this issue;
    Event ID 1196 — Network Name Resource Availability
    http://technet.microsoft.com/en-us/library/dd354022(v=WS.10).aspx
    Check the following:
    Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.
    Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.
    Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.
    For more information please refer to following MS articles:
    DNS Registration with the Network Name Resource
    http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
    Lawrence
    TechNet Community Support

  • Windows Server 2012R2 Failover Cluster error with mounted volumes

    Hi all,
    I've a problem with mounted volume on a WSFC build on top of Windows Server 2012R2, the situation is:
    M: is the volume hosting mounting points
    disk-1, disk-2, disk-3 are volume mounted on M:\SomeFolder
    Theese volumes are used by a SQL Server Failover Cluster Instance, but my problem is related to WSFC. I've set dependencies so disk-1, disk-2, disk-3 depend upon H:
    If I try a failover of the role "SQL Server" I observe that when the disk come online in the other node they fail with this error:
    Cluster resource 'disk-1' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster
    Manager or the Get-ClusterResource Windows PowerShell cmdlet.
    If I manually take offline H: and than bring it online and then manually take online all disk (1 to 3) they come online with no error.
    I'm going crazy!

    I've found the root of the problem: the servers are virtual machine on a VMware ESX 5.5 infrastructure, VMware claims that on 5.5 multipath is supported for raw device mapping disks but disabling multipath (I've set to fixed path) the Windows Server Failover
    Cluster stops to get problems.
    Now we have opened a support call with VMware.

  • Migrating Windows Server 2003 File Cluster to Windows Server 2008 R2

    Hello,
    I have a very large Windows Server 2003 2 node file cluster that I would like to upgrade to Windows 2008 R2. I need to do this inplace (same server hardware) and I would like to use the existing storage if possible (I could buy more if it would make things
    easier).
    Is there a step by step guide that can tell me how to do this upgrade inplace or can anyone give me details on how to do this? I've looked at a few articles and they are not very descriptive on what to do.

    What Microsoft calls an inplace upgrade is option 2 below
    There are two basic migration/upgrade methods for a 2003 cluster to 2008
    1) Build on new hardware, and move the disk/migrate the data. 
    2) Break cluster and remove one node, use that node to build a new one node cluster.  Repeat by removing nodes and adding to new cluster.
    Here is the MS Step-by-step guide for both of these approaches.
    http://technet.microsoft.com/en-us/library/cc754481(WS.10).aspx

  • RDS invalid licensing Windows Server 2003 Client

    I have two Windows Server 2012 Session Host Server and two Windows 2012 Connection Brokers. One Connection Broker configured with remote desktop License.We are Using License type is per device cal.
    On Server A, I can access RDP from Windows 7 clients and from Windows XP clients Windows Server 2003 Clients.
    On Server B I can only RDP from Windows 7 clients and Windows XP Clients NOT from Windows Server 2003 Clients). The error is"The remote session was disconnected because the remote computer received an invalid licensing message from this computer"

    Hi Gyan,
    Which version of client RDP you are using in your environment?
    Did you receive any particular Event ID during this issue?
    Here for your issue I found something to let u know, if licensing mode on the terminal server is set to Per Device but the license server is configured to issue only Per User CALs, then only temporary Per Device licenses are issued from the available pool of
    licenses. The license cannot upgraded. 
    Please check the license is properly configured and activated. If not then you can contact MS clearing house or try to change the terminal server licensing mode.
    Please refer below link for more information.
    The remote session was disconnected because the local computer's client access license could not be upgraded or renewed
    http://technet.microsoft.com/en-us/library/cc737592(v=ws.10).aspx
    You need to verify the terminal server because it can’t able to locate the license server.
    The terminal server cannot locate the license server
    http://technet.microsoft.com/en-us/library/cc758805(v=ws.10).aspx
    Hope it helps!
    Regards.

  • Licensing - Windows Server Datacenter Edition

    Hello,
    I have 2hosts on which ESX have been installed.
    i have lots of VMs running on the hosts.
    Can i still buy Windows Server 2012 Datacenter edition LICENSE and use in my environment?? that is i want to buy datacenter edt and use the product key on any VM that am setting up..
    How many licenses should i buy as the two hosts will be in redundant mode, that is a vm can migrate or moved to another host.
    an exact reply will be appreciated..

    Yes, this is possible. See here fot the technical note. You need 1 windows datacenter license per host. If you have 2 hosts, that means you need 2 licenses.
    http://www.google.fr/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=2&ved=0CEoQFjAB&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F7%2F7%2F0%2F7707E736-4557-4310-9709-87358F7E6D1A%2FWindowsServer2012VirtualTech_VLBrief.pdf&ei=2OIOU4_lPOKH0AX5vIHgBg&usg=AFQjCNHVFeEE4c__48Pw3v1M8sHyxh27PQ&sig2=NIWCKQ7Aq9-ZRlyuRYwH0Q&bvm=bv.61965928,d.d2k

  • Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

    I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
    Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
    When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
    Any suggestion on resolving this problem?
    Thanks
    Ikad

    Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
    Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
    Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
    to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
    Ikad

  • Windows Server 2012r2 Failover Cluster Event Trace Log files

    Hi
    The only documentation I can find regarding event trace log files (Diagnostic.etl.*) for Failover Clustering relate to Server 2008/2008r2, which state that the etl files should be in C:\Windows\System32\winevt\Logs.
    I have been exploring a clustering lab for Server 2012r2 and cannot find these files in that folder.
    Strangely the PS cmdlet Get-ClusterLog still works!
    Where are the etl files?
    TIA

    Hi,
    Please check if the log is available in C:\ProgramData\Microsoft\Windows\WER\ReportQueue\.
    If not, you can use Get-ClusterLog with the Destination parameter to get the log file.
    Destination
    Specifies the location to copy the cluster log(s) to. To copy to the current folder use "-Destination ." for this parameter.
    http://technet.microsoft.com/en-us/library/ee461045.aspx
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Windows Server 2012 HyperV Cluster - Dynamic Memory Config

    Hello There,
    I am about to configure two node HyperV Cluster on Windows 2012 R2.
    There is 192 GB RAM on each node but my VMs requirement is around 216 GB but some VMs doesn't require the full memory capacity all the time so in this scenario what is the best method to use dynamic memory utilization.
    RAM
    48 GB
    48 GB
    16 GB
    48 GB
    48 GB
    8 GB
    I need to provision 6 VMs with the above memory config but want to utilize it effectively through dynamic memory, please suggest.
    I don't need the full RAM capacity all the time as in the table.
    Thanks,
    maqsood
    Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

    Of course you can, this is the aim of the dynamic memory feature.
    In the VM's memory configuration, you will find three parameters:
    Start up RAM : This is the memory allocated to the VM when it's started
    Maximum RAM : This is the maximum amount of memory that a VM can request from the Hypervisor. If there is available memory the host will grant it more memory, if not, the VM will not receive memory
    Minimum RAM : Because the memory configuration is dynamic, when a VM will not use memory, it will give back its memory resources to the host, but it will never go down its Minimum RAM value (The total minimum RAM of all VMs can never exceed the available
    memory, otherwise the VMs will not even start)
    And there is the Priority option that tell the hypervisor which VM to satisfy first.
    Look here for more explanation
    Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com

  • How to add a cloud machine as a node to existing windows fail over cluster having on-premise node in Windows server 2008 R2

    Hi All,
    We have a windows fail over cluster having one windows machine on local network as one of its node.
    I want to add a virtual cloud machine available on microsoft azure as another node to this existing cluster.
    Please suggest how to do this?
    Thanking all in advance,
    Raghvendra

    Before you even start working on the SQL side, you will need to create a Windows Server 2008 R2 cluster with no shared storage.  You can actually test that in-house.  Create a VM running 2008 R2 and cluster it with your physical (from your description,
    I am assuming physical) 2008 R2 machine. Create it with a file share witness for quorum. Then configure your environment to see that it works as expected.
    Once you know how to configure the cluster between physical and VM with a file share witness, build it to Azure.  The location of the FSW gets to be an interesting choice.  To have a FSW in Azure means that you will need another VM in Azure to
    host the file share, meaning you have two quorum votes in Azure and one in-house.  Or, you could create a file share witness on an in-house system, giving you two quorum votes in-house and one in Azure.
    In the FSW in Azure scenario, if you have a loss of the in-house server, automatic failover occurs because two quorum votes exist in Azure.  With FSW in-house, depending on the loss you have in-house, you might have to force quorum to get the Azure
    single-node cluster to run.  Loss of access to Azure reverses those scenarios.  Neither one is optimal, but it does provide some level of recoverability.
    . : | : . : | : . tim

  • Maximum Nodes supported for NLB and Cluster in Windows Server 2008 Standard Edition ?

    Hi.
    I am looking for information How many nodes supported for NLB and Cluster in Windows Server 2008 Standard Edition ?
    If you can provide for all the versions that would be great.
    -Thanks
    - Ajay Chanana

    Hi,
    You can configure a Windows server 2008 NLB cluster with up to 32 nodes. However,
    scaling beyond 8 nodes will cause a slight performance hit because the network traffic is broadcasted to every node and only one NLB node accepts the connection.
    For more detailed information, please refer to the link below:
    FAQ Week for NLB: Tuesday
    Best regards,
    Susie

  • CUA: One or more errors occurred while checking the status of Windows Firewall on the cluster nodes

    Cluster with 2 hosts 2012 R2
    Scheduled CAU fails with:
    CAU run {4EFE116C-AB49-456D-8EED-F7EDC764DA49} on cluster Cluster1 failed. Error Message:One or more errors occurred while checking the status of Windows Firewall on the cluster nodes. Review the errors for more information on how to resolve the problems.
    Error Code:-2146233088 Stack:   at MS.Internal.ClusterAwareUpdating.Util.<CheckFirewallsAsync>d__3a.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.<_ProcessCluster>d__78.MoveNext()
    If I run CAU "Analyze Readiness" ALL comes as PASS
    If I run CUA by hand on same hosts with NO change to the system (not even reboot) it finishes OK
    Anybody any ideas?
    Thanks
    Seb

    Hi,
    In some case if you disabled the connection in Windows firewall inbound of
     "Cluster aware updating" service it will can’t use the CAU.
    More information:
    Starting with Cluster-Aware Updating: Self-Updating
    http://blogs.technet.com/b/filecab/archive/2012/05/17/starting-with-cluster-aware-updating-self-updating.aspx
    What is Cluster Aware Updating in Windows Server 2012? (Part 1)
    http://blogs.technet.com/b/mspfe/archive/2013/02/06/what-is-cluster-aware-updating-in-windows-server-2012.aspx
    Cluster-Aware Updating Overview
    http://technet.microsoft.com/en-us/library/hh831694.aspx
    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.

Maybe you are looking for