MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  0@{@/.rsrc00@@0H rx(y@~Xp        0 @ P ` p@| X.0184\5(7p:L<MUI.F[[<;ǁPEw ќ MUI en-US in organizational unit Bind to domain controller %1.\Check whether the computer object %1 for node %2 exists in the domain. Domain controller %3.1Computer object for node %1 exists in the domain.9Computer object for node %1 does not exist in the domain.LCreate computer object %1 on domain controller %2 in organizational unit %3.{The specified organizational unit %1 does not match the organizational unit %2 where the cluster computer object is found. Computer object %1 is disabled on a read-only domain controller %2. The account for the cluster computer object must be manually enabled on a read-write domain controller to successfully create the cluster.Computer object %1 is enabled and may be in use. Ensure that this is not being used and disable the computer object if it is not being used.2Enable computer object %1 on domain controller %2.aChecking for account information for the computer object in the 'UserAccountControl' flag for %1.{Computer object %1 is not found on read only domain controller %2. The computer object needs to be pre-created and enabled.Set password on %1.HCreating computer object in organizational unit %1 where node %2 exists.)Get GUID of computer object with FQDN: %1Adding special permissions to the computer object failed. Trying to add 'Full-Access' permissions for security principal %1 to computer object %2 failed. Verify that the user running create cluster has permissions to update the computer object in Active Directory Domain Services.?Provide permissions to protect object from accidental deletion.Providing 'Deny delete' and 'Deny delete subtree' permissions to protect computer object %1 from accidental deletion failed. Verify that the user running create cluster has permissions to update the computer object in Active Directory Domain Services.<Write service principal name list to the computer object %1.Writing service principal name list to the computer object %1 failed with error code 0x%2!lx!. Verify that the user running create cluster has permissions to update the computer object in Active Directory Domain Services.CSet supported encryption types in Active Directory Domain Services.Setting supported encryption types in Active Directory Domain Services failed with error code 0x%1!lx!. Verify that the user running create cluster has permissions to update the computer object in Active Directory Domain Services.\Adding the configuration for the new node %1 to the cluster failed with error code 0x%2!lx!.Cluster service on node %1 did not reach the running state. The error code is 0x%2!lx!. For more information check the cluster log and the system event log from node %1.Error getting a handle to node %1. The operation failed with error code 0x%2!lx!. For more information check the cluster log and the system event log from node %1.Failover Cluster feature is not installed on node %1. This feature is required to installed before the node is added to the cluster.iNode %1 appears to be a member of a cluster. It is either a member of an existing cluster or the node was not cleaned up after being evicted from a cluster. If you are sure this is not a member of a cluster run the Remove-ClusterNode cmdlet with the  Force parameter to clean up the cluster information from the node and then try to add it to the cluster again..Find a suitable domain controller for node %1.ESet operating system and version in Active Directory Domain Services.%Enables servers to work together as a cluster to keep server-based applications highly available, regardless of individual component failures. If this service is stopped, clustering will be unavailable. If this service is disabled, any services that explicitly depend on it will fail to start.Cluster Service Cluster Group Cluster NameCluster IP AddressCluster IP Address %wsDiskCluster Network %uAvailable Storage-Failover cluster virtual network name accountPFile Description: This file is the Failover Cluster tombstone file for a disk that was previously designated as a quorum disk. This file ensures that nodes that were offline during the quorum designation change are notified that this is no longer used as a quorum disk. Do not delete this file until all nodes have joined the cluster.Cluster Pool %dGeneric ApplicationGeneric Service Network Name Physical DiskPA Print Spooler File Share IP Address DHCP Service WINS ServiceMessage Queuing#Distributed Transaction CoordinatorGeneric ScriptVolume Shadow Copy Service Task IPv6 AddressIPv6 Tunnel AddressMessage Queue Triggers NFS ShareiSNS Cluster ResourceFile Share Quorum Witness File ServerDistributed File SystemDFS Replicated FolderVirtual MachineVirtual Machine ConfigurationScale Out File ServerDistributed Network Name Storage PooliSCSI Target ServerTask Scheduler"Virtual Machine Replication BrokerNetwork File System/Hyper-V Network Virtualization Provider AddressNetwork Address TranslatorDisjoint IPv4 AddressDisjoint IPv6 AddressPA@XPPtCluster Reconnect Critical Error Warning Information Verbose `Microsoft-Windows-FailoverClustering-Client xMicrosoft-Windows-FailoverClustering-Client/Diagnostic %1 4VS_VERSION_INFO@%@%?StringFileInfo040904B0LCompanyNameMicrosoft CorporationPFileDescriptionCluster API Libraryr)FileVersion6.3.9600.16384 (winblue_rtm.130821-1623)0InternalNameclusapi.LegalCopyright Microsoft Corporation. All rights reserved.8OriginalFilenameclusapij%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.16384DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING