70-412 Ch 1-5 Computer Science

Two ***To create a failover using Windows Server 2012, you need a minimum of two servers that meet the minimum requirements of Windows Server 2012 and that have identical hardware components.

All servers must be joined to an Active Directory domain ***Correctly stated, this requirement is that all servers in the failover cluster must be joined to the same Active Directory domain.

Node Majority ***The Node Majority quorum type can sustain the loss of one-half of the cluster nodes (rounded up), minus one.

4,000 ***In Windows Server 2012, a failover cluster can have 64 physical nodes and can run 4,000 virtual machines on each cluster.

Using UDP port 3343 unicast ***Cluster nodes are kept aware of the status of the other nodes and services through the use of heartbeats. Heartbeats transmit and receive using UDP port 3343 unicast (legacy clusters used UDP broadcast).

The fabric ***If the cluster communicates to shared storage using Fibre Channel, the Fibre Channel will connect using a dedicated network known as a fabric.

SAS ***Shared serial attached SCSI (SAS) is a low-cost option that requires the cluster nodes to be physically close to the drives. Typically, the SAS has a limited number of connections for cluster nodes.

By using LUN masking or zoning ***A storage device can be assigned to only one cluster. This is usually accomplished with logical unit number (LUN) masking or zoning.

Server Message Block (SMB) Multichannel ***CSV in Windows Server 2012 offers multisubnet support for CSVs so you can achieve faster throughput when integrated with Server Message Block (SMB) Multichannel and it allows the network adapters to support Remote Direct Memory Access (RDMA).

A witness ***If there is an even number of nodes in a cluster, then the cluster needs to have a witness assigned to the cluster to break the tie during failures of cluster nodes. The witness can be either a disk or a file share.

Add-ClusterGroup ***You would need to use the Add-ClusterGroup cmdlet to add an empty resource group to the failover cluster configuration, in preparation for adding clustered resources to the group.

Set-ClusterOwnerNode ***You would need to use the Set-ClusterOwnerNode cmdlet to specify which nodes can own a resource in a failover cluster or to specify the order of preference among owner nodes for a clustered role, or a resource group.

Remote-updating mode ***With remote-updating mode, you install the failover clustering administrative tools on a CAU orchestrator (a remote computer running Windows 8 or Windows Server 2012 that is not a member of the cluster). The CAU is included in the Remote Server Administration Tool (RSAT). The administrator triggers the update process on the orchestrator computer.

Windows Server 2008, Windows Server 2008 R2 ***You can migrate clusters running Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

The disks must be only GPT, not MBR. ***To use a shared disk, you must use the following guidelines: - For the disk type, use basic disks, not dynamic disks. - For the file system type, format the disk as New Technology File System (NTFS). - For the partition style of the disk, you can use either master boot record (MBR) or globally unique identifier (GUID) partition table (GPT). - The storage device must follow the SCSI Primary Commands-3 (SPC-3) standard including supporting Persistent Reservations. - The miniport driver used for the storage must work with the Storport storage driver. - A storage device can be assigned to only one cluster. This is usually accomplished with logical unit number (LUN) masking or zoning.

Cluster resource ***A cluster resource is the most basic and smallest configurable unit that may provide a service to clients, or it is an important component that makes up the cluster.

Each clustered server should have one or more network adapters or host bus adapters dedicated to the cluster storage ***If you use iSCSI storage connections, each clustered server should have one or more network adapters or host bus adapters dedicated to the cluster storage.

AD DS does not require clustering for fault tolerance ***It is not recommended that you install the Active Directory Domain Services (AD DS) role on any of the nodes. Having multiple domain controllers provides fault tolerance without using a cluster.

No Majority (Disk Only) ***The No Majority (Disk Only) quorum type allows the cluster to function as long as one node is available and the disks are online. However, this configuration is not recommended, because the disk might be a single point of failure.

Node Majority ***The Node Majority quorum type is recommended for clusters with an odd number of nodes. It can sustain failures of half the nodes (rounding up) minus one.

Node and File Share Majority ***The Node and File Share Majority quorum type is used for clusters with special configurations. Instead of using a disk witness, it uses a file share witness.

Node and Disk Majority ***The Node and Disk Majority quorum type is recommended for clusters with an even number of nodes. It can sustain failures of half the nodes (rounding up) if the disk witness remains online.

Network Load Balancing ***Network Load Balancing (NLB) transparently distributes traffic across multiple servers by using virtual IP addresses and a shared name. With NLB, you gain fault tolerance and enhanced performance. It is often used with mission-critical web servers but can also be found with other types of servers.

Network adapters in the NLB cluster can use both multicast and unicast simultaneously. ***Within each cluster, all network adapters must be either multicast or unicast. You cannot have some nodes configured as multicast while other nodes are configured as unicast within a single cluster.

Server Manager ***To add the NLB feature to a computer running Windows Server 2012, you use Server Manager.

Firewall rules ***To configure the NLB cluster, you must configure three types of parameters: - Host parameter: Defines what each node can do in an NLB cluster. - Cluster parameter: Configures the NLB cluster as a whole. - Port rules: Controls what ports the NLB cluster services and how requests are balanced across all servers.

Add-WindowsFeature NLB,RSAT-NLB ***To install the NLB cluster and the NLB tools using PowerShell, you can use the following cmdlet: Add-WindowsFeature NLB,RSAT-NLB

Add-NlbClusterNodeDip ***You can use the Add-NlbClusterNodeDip cmdlet to add a dedicated IP to an NLB cluster node.

Remove-NlbCluster ***You can use the Remove-NlbCluster cmdlet to delete a specified NLB cluster.

Get-NlbCluster | Set-NlbCluster -ClusterPrimaryIP IPaddress ***You would need to use the Get-NlbCluster | Set-NlbCluster -ClusterPrimaryIP IPaddress PowerShell one-liner to change or set the primary IP address of the cluster.

The node IP address the rule should apply to ***When you configure the port rules, you configure the following: - The virtual IP address that the rule should apply to - The TCP or UDP port range that this rule should apply to - The protocols that this rule should apply to, including TCP, UDP, or both - The filtering mode that specifies how the cluster handles traffic, which is described by the port range and the protocols

Unicast ***When you configure an NLB cluster to use unicast mode, NLB replaces the network card's original MAC address, and all cluster hosts use the same unicast MAC address.

You will need separate cluster and management network adapters if you manage the nodes from a different TCP/IP subnet than the cluster network. ***When you use unicast mode with a single network adapter on each node, the computer can communicate only with other computers within the same subnet. If you perform management tasks on the computer, you need to perform these tasks on a computer that is on the same TCP/IP subnet as the node, or you have to use a second network adapter and address.

IGMP Multicast ***Another mode available is the Internet Group Management Protocol Multicast mode, which is a special form of multicast mode that prevents the network switch from flooding with traffic. When you use IGMP multicast mode, traffic is forwarded only through the switch ports that are part of the NLB cluster.

Drainstop ***To perform maintenance on an NLB node that needs to be temporarily removed from the NLB cluster, you should choose drainstop so that connections are not prematurely stopped before the requests are completed.

Stop ***The stop action terminates all existing connections to the cluster node and stops the NLB service. This would most likely be the best option if you needed to immediately take the server out of the NLB cluster for maintenance; although, it will result in client session interruption, so it should be used with caution and an understanding of the net result.

Mainboards (motherboards) ***To make a server more fault tolerant, you should first look at what components are the most likely to fail and implement technology to make the system less likely to fail. Some of the components that are made redundant within a system are usually the following: - Disks: Use some form of RAID and hot spares. - Power supplies: Use redundant power supplies. - Network cards: Use redundant network cards.

To ensure there are no misunderstandings ***If there is miscommunication about service-level expectations between the customer and the IT department, poor business decisions, unsuitable investment levels, and customer dissatisfaction are likely to occur. Therefore, you need to express availability requirements clearly so that there are no misunderstandings about the implications.

They define which ports are balanced among the hosts of the cluster ***Port rules define which incoming TCP/IP requests are balanced among the hosts in the NLB cluster.

Selecting the "Single" option will force a single cluster node to handle all client requests from a specific client ***When you select the "Single" affinity option, a single cluster node handles all requests from a single client. This option is useful for stateful applications where the status of a process or transaction is maintained through the entire connection, including when using SSL and e-commerce shopping cart applications.

Five nines (99.999%) ***The maximum allowable downtime for each "9" of availability is: - 99%—3.65 days per year, or 7.20 hours per month - 99.9% ("three nines")—8.76 hours per year, or 43.8 minutes per month - 99.99% ("four nines")—52.6 minutes per year, or 4.32 minutes per month - 99.999% ("five nines")—5.26 minutes per year, or 25.9 seconds per month - 99.9999% ("six nines")—31.5 seconds per year, or 2.59 seconds per month

Four nines (99.99%) ***The maximum allowable downtime for each "9" of availability is: - 99%—3.65 days per year, or 7.20 hours per month - 99.9% ("three nines")—8.76 hours per year, or 43.8 minutes per month - 99.99% ("four nines")—52.6 minutes per year, or 4.32 minutes per month - 99.999% ("five nines")—5.26 minutes per year, or 25.9 seconds per month - 99.9999% ("six nines")—31.5 seconds per year, or 2.59 seconds per month

Six nines (99.9999%) ***The maximum allowable downtime for each "9" of availability is: - 99%—3.65 days per year, or 7.20 hours per month - 99.9% ("three nines")—8.76 hours per year, or 43.8 minutes per month - 99.99% ("four nines")—52.6 minutes per year, or 4.32 minutes per month - 99.999% ("five nines")—5.26 minutes per year, or 25.9 seconds per month - 99.9999% ("six nines")—31.5 seconds per year, or 2.59 seconds per month

Three nines (99.9%) ***The maximum allowable downtime for each "9" of availability is: - 99%—3.65 days per year, or 7.20 hours per month - 99.9% ("three nines")—8.76 hours per year, or 43.8 minutes per month - 99.99% ("four nines")—52.6 minutes per year, or 4.32 minutes per month - 99.999% ("five nines")—5.26 minutes per year, or 25.9 seconds per month - 99.9999% ("six nines")—31.5 seconds per year, or 2.59 seconds per month

Distributed Transaction Coordinator (DTC), Exchange Server ***The High Availability Wizard offers the following services and applications to choose from: DFS Namespace Server, DHCP Server, Distributed Transaction Coordinator (DTC), File Server, Generic Application, Generic Script, Generic Service, iSCSI Target Server, Internet Storage Name Service (iSNS) Server, Message Queuing, Other Server, Virtual Machine (VM), WINS Server.

Uses multiple network interfaces, Introduces bandwidth aggregation and network fault tolerance, SMB 1.0 and SMB 2.x clients will use a single SMB connection ***SMB Multichannel uses multiple network interfaces to provide both high performance through bandwidth aggregation and network fault tolerance through the use of multiple network paths to data on an SMB share. SMB 1.0 and SMB 2.x clients will use a single SMB connection.

PowerShell cmdlets for SMB ***SMB PowerShell management cmdlets were introduced in Windows Server 2012 and in Windows 8 with SMB 3.0.

DFS replication, File Server Resource Manager, NFS ***Unlike a General Use File Server cluster, the Scale-Out File Server cluster is an active-active failover cluster where all file shares are online on all nodes simultaneously. Although the Scale-Out File Server supports SMB, it does not support NFS, Data Deduplication, DFS Replication, or File Server Resource Manager.

CSV and CSV cache ***To support multiple nodes to access the same volume at the same time, the Scale-Out File Server uses a CSV. It also uses a CSV cache, which is a read cache that significantly improves performance in certain scenarios, such as Virtual Desktop Infrastructure.

Create Computer Objects ***When you first create a cluster or add servers to a cluster, you must be logged on to the domain with an administrator's account on all the cluster's servers. If the account is not a domain administrator, the account must have the Create Computer Objects permission in the domain.

List the servers in the preferred order ***Select the server to be preferred from the list of available servers, then use the Up and Down buttons to move that server to the top or bottom of the listing.

The order in which roles are started up ***If a cluster has multiple roles, you can categorize the priority for each role. Roles with higher priorities are started before roles with lower priorities. If you don't want a role to start, you select No Auto Start.

Allows you to control which node the resources come online on after a failure ***When configuring the Failback option, you can specify when failback will occur and whether or not to failback to the preferred owner after the preferred owner is brought back online.

The maximum number of failures that can occur, The length of time in hours ***You will configure the maximum number of failures that can occur in the selected number of hours. If the cluster fails more times within the selected period of time, it can be configured to be left offline for manual intervention.

1250 ***When the service is determined to be unhealthy, the Event ID 1250 will be logged.

System ***The events (event ID 1250) will be logged in the System log.

Add-ClusterVMMonitoredItem -VirtualMachine "VM42" -Service DHCPClient ***You would correctly use the PowerShell cmdlet Add-ClusterVMMonitoredItem -VirtualMachine "VM42" -Service DHCPClient to configure this monitoring configuration.

Move the VM to another cluster node and restart it again ***When the service is determined to be unhealthy, the Event ID 1250 will be shown in the System Log. VM Monitoring will then restart the VM gracefully on the host that it's currently running on. If the VM fails again, VM Monitoring will move the VM to another node and start the VM.

Support for SMB 3.0 ***The General Use File Server role provides a central location for users to share files or for server applications that open and close files frequently. It also supports SMB, Network File System (NFS), Data Deduplication, File Server Resource Manager, DFS Replication, and other File Services role services. The only significant difference between Windows Server 2008 R2 and Windows Server 2012 is that Windows Server 2012 supports SMB 3.0.

Enable continuous availability, Encrypt data access ***The Enable continuous availability and Encrypt data access options are selected by default. The Enable continuous availability takes advantage of SMB v3 functionality (Transparent Failover), whereas the Encrypt data access enables encryption of the SMB connections.

Provide hardware-assisted virtualization ***Hosts require an x64-based processor with hardware-assisted virtualization.

SMB Direct ***SMB Direct (SMB over Remote Direct Memory Access [RDMA]) enables direct memory-to-memory data transfers between servers, with minimal CPU utilization and low latency, using standard RDMA-capable network adapters (iWARP, InfiniBand, and RoCE). It also minimizes the processor utilization when performing large file I/O operations.

SMB Transparent Failover ***SMB Transparent Failover provides Continuously Available properties that allow SMB 3 clients to not lose an SMB session when failover occurs. Both the SMB client and SMB server must support SMB 3.0 to take advantage of the SMB Transparent Failover functionality.

SMB Directory Leasing ***SMB Directory Leasing reduces the latency when accessing files over slow WAN links by caching directory and file meta-data for longer periods, which reduces the associated round-trips to fetch the meta-data from the server.

SMB Scale Out ***SMB Scale Out allows users to scale shared bandwidth by adding cluster nodes.

SMB Encryption ***SMB Encryption performs encryption by selecting a check box. Both the SMB client and SMB server must support SMB 3.0 to take advantage of the SMB Encryption functionality.

All hosts must use processors from the same manufacturer, All hosts must support hardware virtualization ***Additionally, the involved hosts must be running Windows Server 2012, must be in the same Active Directory domain (or trusting domains), the VMs must be using VMD or VMDX disks and you must have the required administrative permissions to perform the LM.

Configure Kerberos constrained delegation on the source server ***If you are using remote management tools, you need to configure constrained delegation and select Kerberos as the authentication protocol. You will perform the delegation on the source server, selecting services on the target server.

Move only the snapshot files ***There is no option when performing a Live Migration to move only snapshot files.

Move the VM's data to different locations ***There is no option "Move the VM's data to different locations" in the advanced options available to you when using the "Move the virtual machine's data by selecting where to move the items" Live Migration option.

A failover cluster ***Quick Migration occurs within the confines of a cluster, allowing you to quickly migrate a running VM from one cluster node to another.

The speed of the network between the source and destination servers, The amount of memory that needs to be written to disk ***The speed of the Quick Migration is dependent on how much memory needs to be written to disk and the speed of the network connection between the source and destination servers.

Restore the virtual machine (create a new unique ID) ***There is no option available to "Restore the virtual machine (create a new unique ID)".

Run sysprep ***If you want to use an exported VM as a template to create multiple VMs, you should run sysprep on the VM prior to performing the export.

Windows Server 2012 only ***SCVMM SP1 runs only on Windows Server 2012

OVF, VMware, Citrix XenServer ***Currently, SCVMM supports migrations from VMware, XenServer, or OVF. You wouldn't migrate a VHD, you would export and import it instead.

Apply the OVF Import/Export tool ***Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual machines and needs the OVF Import/Export tool, which is available from the Microsoft Download Center. The OVF Import/Export tool must be installed into an existing VMM management server that has the VMM console installed.

256 MB of RAM installed, Uses BitLocker Drive Encryption on the data volume ***Source servers to be migrated using P2V must have at least 512 MB of RAM and cannot have any encrypted volumes.

Windows Server 2003 SP1 32-bit ***VMM does not support P2V conversion for computers running NT Server 4.0 or Windows Server 2003 SP1.

3.5 update 5 ***The prerequisites for V2V using SCVMM are as follows: - VMware ESX/ESXi version 3.5 update 5 or higher (4.0, 4.1, or 5.1). - The VMware Tools must be removed. - VMware virtual hard disks cannot be connected to an IDE bus.

Servers with FAT32 volumes, Servers that are domain controllers ***An offline P2V conversion is the only way to migrate FAT volumes and domain controllers.

Move the VM's data automatically ***The "Move the VM's data automatically" option maintains the file and folder structure of the source on the destination.

Move the VM's hard disks to different locations ***The "Move the VM's items to different locations" option allows you to specify the location of each moving item.

Copy the virtual machine (create a new unique ID) ***The "Copy the virtual machine (create a new unique ID)" option is used when you have an exported VM that you are using as a template and want to import many times.

Storage Migration ***Storage Migration is the process of moving the storage of a VM from one physical server to another without a cluster.

Quick Migration ***Quick Migration is the process of moving an entire VM or parts of a VM to another physical server using a cluster.

Exporting ***Exporting a VM is the process by which you take a partially or completely configured VM and create other VMs without having to perform the installation and configuration from scratch.

Live Migration ***Live Migration is the process of moving an entire VM or parts of a VM to another physical server without a cluster.

NFS ***Network File System (NFS) is a distributed file system protocol that is used to access files over a network, similar to accessing a file using a shared folder in Windows (which uses Server Message Block (SMB). It is used with UNIX and Linux file server clients and VMware.

Identity Management for UNIX ***Identity Management for UNIX enables you to integrate Windows users into an existing UNIX or Linux environment, including managing user accounts and passwords on Windows and UNIX systems.

Server for NFS ***When you install the Server for NFS role, it extends the Active Directory schema by adding UNIX attributes.

Login script ***You can configure the following UNIX attributes: NIS domain, UID, login shell, Home directory, and Primary group.

NFS ***BranchCache supports HTTP/HTTPS, SMB and BITS.

Hosted cache mode ***The hosted cache mode uses one or more dedicated servers to host the cache.

Fewer than 50 ***Distributed cache mode is designed for branch offices with fewer than 50 users that do not have a dedicated server in the branch office. BranchCache works across a single subnet only.

Configure switches to support BranchCache ***You will not need to make any changes to your network infrastructure (switches, routers) to support BranchCache.

Disallow hash publication on shared folders on which BranchCache is not enabled ***There is no Group Policy option for BranchCache hash publication to "Disallow hash publication on shared folders on which BranchCache is not enabled."

File classification ***File classification allows you to configure automatic procedures for defining a desired property on a file, based on the conditions specified in classification rules. Once the classification has been made, however, you can then do many other things such as deleting files, archiving files, or other automated tasks.

Specify files to be audited, Enable object access auditing ***When you want to audit files, you must first enable object access auditing. Then you must specify what files you want to audit.

Success, Fail, All ***You will need to select Success, Fail, or the All type when configuring what type of actions to perform auditing on.

Global Object Access Auditing ***Starting with Windows 7 and Windows Server 2008 R2, you can enable Global Object Access Auditing, which enables you to configure object access auditing for every file and folder in a computer's file system.

Dynamic Access Control ***You can use Dynamic Access Control to create targeted audit policies based on resource properties, and expressions, so that you don't have to audit every file.

Using dism.exe ***You must install the Identity Management for UNIX using the Deployment Image Servicing and management command-line tool, dism.exe.

UID and GID ***Users are identified with a user identifier (UID) value and a group identifier (GID). Whenever a file is accessed using NFS, the UID and GID are sent to the NFS server to see whether the user has the proper permissions for access.

The File Services role, The Server for NFS role service, The Failover Clustering feature ***After you install all three prerequisites and create a cluster, you can configure the cluster to provide high availability for NFS and create an NFS share.

Authorization ***Authentication is used to prove the identity of a user. Authorization gives access to the user who was authenticated.

Enable-BCLocal ***You will use the Enable-BCLocal cmdlet to configure BranchCache in local caching mode.

Set-BCCache ***You will use the Set-BCCache cmdlet to modify BranchCache configuration.

Add-BCDataCacheExtension ***You will use the Add-BCDataCacheExtension cmdlet to increase the BranchCache storage space.

Enable-BCDistributed ***You will use the Enable-BCDistributed cmdlet to configure BranchCache on a computer in distributed caching mode.