1 Configuring Windows Server Clusters In Enterprise network, group of servers are often used to provide a common set of services. For example, Different physical computers can be used to answer request directed at a common web site or database server. These servers group are often referred as Clusters. In Windows Server 2008, we can configure three types of server groups for load balancing, scalability and high availability. In this article we will discuss about the load balancing and high-availability server clusters we can configure in Windows Server We can configure three types of server groups in windows server Round-Robin Distribution Group Network Load Balancing (NLB) cluster Failover Cluster First, a Round-Robin distribution group is a group or set of computers that uses DNS to provide basic load balancing with minimal configuration requirements. It is very simple method for distributing a workload among multiple servers. In round-robin, a DNS server is configured with more than one record to resolve another server s name to an IP address. The purpose of DNS round robin is to load balance client request among servers. Its main advantage is that it is very easy to configure. Round-Robin DNS is enabled by default in most of the DNS servers, so you only need to create the appropriate records on the DNS server. However the biggest drawback is that if one of the servers goes down, the DNS servers does not respond to this event and will keep directing client request to this inactive server until administrators removes the DNS record from the DNS servers. Another disadvantage is that every record is given equal weightage, regardless of whether one target server is more powerful than another. Because of these serious limitations this method is not recommended to use in a large production network. And we will see next how network load balancing overcome these limitations. NETWORK LOAD BALANCING NLB or Network Load Balancing cluster is an installable feature of server 2008 which distributes client request among servers in an NLB cluster by using virtual IP address and a shared name. From the client perspective, NLB cluster appears to be a single server. In a common scenario, NLB is used to create a Web farm a group of computers to support a web site or a set of web sites. Also it can be used to create a terminal server farm, a VPN server farm, or an ISA server firewall cluster. But it s not suitable for the clusters where data changing occurs most, for example SQL database cluster, file server cluster. For this type of group of servers Microsoft has a cluster solution knows as failover cluster which we will see later in this article.
2 NLB provides some advantages over round-robin DNS method. First of all, NLB automatically detects servers that have been disconnected from the NLB cluster and then redistributes client requests to the remaining live hosts. This feature prevents clients from sending their request to failed server. Another difference is NLB have the option to specify a load percentage that each host will handle. CONFIGURING AN NLB CLUSTER In this section we will learn how to configure an NLB cluster. To demonstrate I have used following servers and role in my lab: Domain: abhi.local Domain Controller: DC01.abhi.local with an IP address Member Servers: Node1.abhi.local with an IP address Node2.abhi.local with an IP address Creating an NLB cluster is very simple process. To begin, on both nodes Node1.abhi.local and Node2.abhi.local configure the service or application (such as IIS) that it provide to clients. Please make sure to create identical configurations because you want the client experience to be identical regardless of which server users are connected to. For this lab purpose I have installed IIS and configured a default web site on both the nodes. The next step is to install Network Load Balancing feature on both the nodes since both node are going to join NLB cluster. To do so, perform following steps on both the nodes: Open Server Manager, and then click Add Features. In this wizard, select Network Load Balancing, click next and follow the prompts to install.
3 Once this install on both the nodes, the next step is to use Network Load Balancing Manager to configure the cluster. To configure, perform the following steps: Launch Network Load Balancing Manager from Administrative Tools or you can also open by typing Nlbmgr.exe from a command prompt. In the Network Load Balancing Manager console tree, right click Network Load Balancing Clusters and then click New Cluster. Connect to the host that is part of this new cluster. In this lab the node is Node1.abhi.local and Node2.abhi.local. I will add Node1 first and configure the properties then I will show you how to add another node in cluster. As you seen from above figure I have entered the Node1 and clicks connect, then I have to select the interface which we want to use with cluster. In this case it is Node IP address The other interface is having the IP address of different subnet than local area network because that one will used for cluster communication, which we will see later during failover configuration.
4 On the Host Parameters page, select a value in priority. The host with lowest numerical priority among the current members handles all the clusters network traffic not covered by a port rule. For this lab I have given priority 1 to Node1. On the Cluster IP Address page, click Add to enter the cluster IP address shared by every host in the cluster. Please note that NLB doesn t support DHCP. NLB disables DHCP on each interface it configures, so the IP address must be static. Also note that the IP Address which we entered here is not the IP address of any servers/node, this IP address will represent the cluster IP address. Here in this lab I have given an IP address Click next
5 On the Cluster Parameters page, in the Cluster IP Configuration area, verify appropriate values for IP address and subnet mask, and then type a fully qualified domain name for cluster. As you seen from above figure I have verified the IP address details and entered the FQDN of cluster as nlbcluster.abhi.local. This wizard generates a uniquely cluster MAC address which client used for serving request to group of servers. Here it s a very interesting thing, if you notice the IP generated MAC address, the last four bit is hexadecimal value of the given IP address. Also please note that FQDN is not needed when using NLB with Terminal Servers. Also from above figure, we have three options for Cluster Operation mode. In Unicast mode, the MAC address of the cluster is assigned to the network adapter of the computer, and the built-in MAC address of the network adapter is not used. It is recommended that you accept the unicast default settings. Click Next to continue. Now we will see the Node1 status from the NLB console, and it is in converged state, means Node1 is ready to do the cluster services and accept the directing request from client.
6 So the Node1 is successfully added in cluster. Let s add our second node Node2.abhi.local to cluster. To add more hosts to the cluster, right click the new cluster nlbcluster.abhi.local and then click Add Host To Cluster. Configure the host parameters (including host priority and dedicated IP address) for the Node2 following the same instructions that we used to configure Node1.abhi.local. Because we are adding hosts to an already configured cluster, all the cluster-wide parameters remain the same. Once this done, verify the status of Node2 from NLB manager console, as shown below: Ok, so our NLB cluster has been configured with two nodes Node1 and Node2, having Node1 as a high host priority 1 and Node2 host priority as 2. Now we will discuss Port Rules of network load balancing cluster. To do so right click newly configured cluster nlbluster.abhi.local and click Cluster properties. And go the Port Rules tab to view the port rule settings:
7 Currently the port rules defined the settings to accept request on all ports for the added nodes in cluster. Since in this lab, we have installed IIS on both the nodes to accept the directing web site request. So in this scenario, for a Web Services we need to enable port 80 for HTTP traffic. So we have to configure this port rule so that the new rule applies only to HTTP traffic. If you are using some other services for example terminal services you have to enable port 3389 to 3389 rule that applies only to RDP traffic. To enable port rule for web services, we need to do following: On the Port Rule page, click Edit to modify the default port rules and type 80 to 80. In the Protocols area, select TCP, as the specific TCP/IP protocol the port rule should cover. In the Filtering mode, select Multiple Host if you want multiple hosts in the cluster to handle network traffic for the port rule. Choose Single Host if you want a single host to handle the network traffic for the port rule. In this lab both of the nodes are configured to query for website request so I have selected Multiple Host. In Affinity (which applies only for the Multiple host filtering mode), I selected None since we want multiple connections from the same client IP address to be handled by different clusters hosts. Once done, click Ok to finish the port rule configuration, as shown in below figure.
8 CREATING A FAILOVER CLUSTER Creating a failover cluster is a multistep process. The first step is to configure the physical hardware for the cluster. Then, you need to install the Failover Clustering feature and run the Failover Cluster Validation tool, which ensures that hardware and software prerequisites are met for cluster. One of the first things you have to do before creating a cluster is to add storage that s because two or more node of will access the resource on same shared storage. For a two-node failover cluster. The storage contain at least two separate volumes (luns), configured at hard-ware level. The first volume will function as the witness disk, a volume that holds a copy of cluster configuration database. Witness disks, known as Quorum disks in Server 2003 are used in many but not all cluster configurations. The second volume will contain the files that are being shared to users.
9 In this lab we will create a two node failover cluster and validate the clustering feature and properties. For storage purpose I am going to use iscsi Starwind SAN. You can download this software from Starwind web site and convert your windows machine into a SAN. Before creating a failover cluster, you have to install Failover Clustering feature in both the nodes. I have already installed this feature on both the node. I am going to use the same node and same configured server which we used during our NLB cluster configuration. Once the feature has been installed, I am going to add the storage to Node. As I told you earlier I am going to use iscsi SAN software from startwind to configure clusters storage. Fortunately we have inbuilt feature with Windows Server 2008 called iscsi Initiator. To Launch iscsi Initiator, open all programs and go to administrative tool and click iscsi Initiator. Enter the target device IP address and click Quick Connect. Select the target which you have created and clicks connect. For this lab demonstrate I have created two targets for Witness and cluster as shown in below figure. The status is shown as inactive, once you click connect it will authenticate against your san device and connect the device for you and status will become active and you will find new disk entry in your disk management console.
10 Once you click Connect your discovered target status will change to active and new disk device will add to your server.
11 Once all this done, initialize and create your new disk and name them as per your environment need. Please note that you should not use Dynamic Disk in Failover Clustering, use Basic Disk. I have made both cluster shared disk online and named as below for this lab demonstration. These two disks will be shared among the nodes in our cluster. Also it is recommended that storage partition must be formatted using NTFS. Also the network you use for iscsi cannot be used for network communication. In all clustered servers, the network adapters you use to connect iscsi storage target should be identical. It is also recommended that you use Gigabit Ethernet or higher.
12 So our storage is ready, and we already installed Failover clustering feature in both the nodes. Now it s time to create and configure failover cluster. To do so, perform following: Here the first thing we have to do is to validate the clustering configuration. To run the Validate A Configuration Wizard, First open Failover Cluster Management from administrative tools. In Failover Cluster Management, click Validate A Configuration in the management area or the actions pane as shown in below figure:
13 Add the name of servers which you want to a part of clusters and click next. In this case we have our two nodes which we will add in our cluster group.
14 Select run all test in the following page and click next. Validate your settings and click next. And cluster will start validating your configuration. Once the configuration is successfully validated we are ready to go and create a failover cluster. Please make sure that when you go for production environment this validation report should be green checked. To View more report on this you can click View report.
15 Running the Create Cluster Wizard The next step in creating a cluster is to run the Create Cluster Wizard. This will install the software foundation for the cluster, converts the attached storage into cluster disks, and creates a computer account in Active Directory for the cluster. To create this, perform following: Launch the tool Failover Cluster Management, click Create A Cluster. In the Create Cluster Wizard, simply enter the names of the cluster nodes when prompted. This will enables you to name and assign an IP address for the cluster, after which the cluster is created. In the Access Point for Administrating the Cluster page enter the name of cluster and assign an IP address. This will create a computer account in AD and a host record A in DNS server
16 Click next on the confirmation page.
17 Now the wizard will start creating cluster. This wizard will validate cluster state on both the nodes.
18 Now the Cluster creation wizard completes, we need to configure the services or applications for which we need to provide failover. To perform this, we have to run the High Availability wizard. The High Availability wizard configures failover service for a particular service or application. To launch the High Availability wizard, in Failover Cluster Management, click Configure a Service or Application as shown below: On the Select Service Or Application page, select the service or application for which you want to provide failover service (high availability), and then click Next. To demonstrate this I choose File server to make a file server cluster in my lab network. (Make sure you have enabled file services role on both the node in order to create a file server failover cluster)
19 On the Client Access Point page, enter the name of cluster and IP address. Please note that IP address information that is not automatically supplied by your DHCP settings and it s a static IPv4 unique address for this clustered file server. In this lab I enter the name of my file server cluster as LabClusterFS with an IP address of upon completion of all this wizard you will see a new computer account named LabClusterFS in Active Directory and IP address record in DNS.
20 On the Select Storage page, select any of the available cluster disks where you want to assign this service or application. As you remember for this lab demonstration I have created two clusters LUN and so I have two storage options for this page and I choose disk Cluster Data. On the Confirmation page click Next and wizard will start the process for creating a file server cluster based on the given configuration. After the wizard runs and the Summary page appears, to view a report of the tasks the wizard performed, click View Report. To close the Wizard clicks Finish.
21 So we have successfully completed our File server failover cluster in our lab network. You will now have this service and application in Failover cluster management tool and the owner of this cluster is Node1.abhi.local. Now lets explore some more features and properties of Failover Cluster Manager tool before creating a shared resource on our file server cluster. Select the newly created cluster LabClusterFs and you can see the summary of this cluster in result pane window as shown in below figure. You can check the status of the cluster, the IP address its configured, the storage volume where our cluster application assigned, its preferred owner and available resource shared folder. Currently we have the default admin shared folder available for our File server cluster, once we configure more shared resource it will be available on this window.
22 On the Nodes menu we can see the total available node for our cluster and if we want to add more nodes in our cluster, simply we do by click Add Node in Action pane. On the Storage menu page, we can see total available cluster disks and the usage of cluster disk. We can see our cluster disk usage report here and which disk are in use and status of our cluster disk volume.
23 On the Networks menu we can view and check the status of our network adapters configured in our clustering. We can also check our cluster quorum network settings as shown in below figure:
24 Ok so we have explored the features and option of failover cluster. Now it s time to create a shared resource in our newly created File server cluster LabClusterFS. To do so perform following steps: Right click the service and application LabClusterFS and click Add a shared Folder. On Shared Folder Location page enter the path of your shared location and click Provision Storage, as shown below:
25 If you want to change the NTFS permission for this shared resource click Yes otherwise leave the default settings and click Next. Leave the default settings on Share Protocols page and click next. If you want to change it to NFS instead of SMB you can change here.
26 Check your settings how your shared folder is to user by client over SMB settings, then click next. On the SMB Permissions if you want to change the permission for shared folder change it otherwise leave it default and click next.
27 If you have DFS namespace in your network publish this in DFS namespace otherwise click Next. Review your configuration settings and if all is well for your network click Create to start the process.
28 You will get a confirmation with green check and your shared folder is successfully created for your file server cluster. Click Close. Now this newly created shared folder is available in services and application console window. VALIDATING FAILOVER CLUSTER Ok, so we have created our shared resource on file server cluster and its available for client use over SMP protocol. It s time to check our failover cluster server in case of any disaster happens. To demonstrate this I am going to move the shared resource on Node1.abhi.local to check the failover functional. Once we verified that our failover is functioning properly again I will move back the resource to Node2.abhi.local, and will shutdown this server and will check and verify the cluster service status. To do so, perform the following steps: Right click the clustered service, click Move This Service or Application To Another Node, and move the cluster service to Node1.abhi.local from Node2.abhi.local.
29 You can observer the status changes in the center pane of snap-in as the cluster services instance is moving. If the service moves successfully, the failover is function. So at this stage we verified that our failover cluster is working properly. The resource is moved to Node1.abhi.local. now lets check one more time. This time I am going to shutdown one node and will see the status of our cluster service. To demonstrate this I moved the resource back to Node2.abhi.local.so my resource is available on Node2. And I am going to shutdown the Node2.abhi.local. Ok I moved the resource and shutdown the machine. Now observer d the status changes in Failover Cluster Manager tool. You will see that status is in pending state and it automatically moving the resource to other available node.
30 Within moments you will see the resource has been successfully moved to other available node partner. In this lab it is Node1.abhi.local. So we have checked and verified our cluster settings are functional and ready to serve in case of any disaster failure. We also see when one server fails; another server takes over the failed server. In this article we have seen the demo about Network Load balancing Cluster and Failover Clustering features of Windows Server 2008.
Network Load Balancing Step by Step installation of Network Load Balancing in Windows Server 2008 R2. Prerequisite for NLB Cluster 1. Log on to NODE1 Windows Server 2008 R2 system with a domain account
Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide Microsoft Corporation Published: May 2010 Abstract This guide describes the steps for configuring Remote Desktop Connection
#1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installing & Configuring a SQL Server 2012 Failover JANUARY 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the StarWind
Configuring a Microsoft Windows Server 2012/R2 Failover Cluster with Storage Center Dell Compellent Solution Guide Kris Piepho, Microsoft Product Specialist October, 2013 Revisions Date Description 1/4/2013
Owner of the content within this article is www.isaserver.org Written by Marc Grote www.it-training-grote.de Microsoft Forefront TMG Webserver Load Balancing Abstract In this article I will show you how
StarWind iscsi SAN: Configuring HA File Server for SMB NAS February 2012 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software logos are trademarks of StarWind Software which
Configuring Network Load Balancing with Cerberus FTP Server May 2016 Version 1.0 1 Introduction Purpose This guide will discuss how to install and configure Network Load Balancing on Windows Server 2012
Building a Scale-Out SQL Server 2008 Reporting Services Farm This white paper discusses the steps to configure a scale-out SQL Server 2008 R2 Reporting Services farm environment running on Windows Server
Getting Started with Hyper-V and the Scale Computing Cluster Scale Computing 5225 Exploration Drive Indianapolis, IN, 46241 Contents Contents CHAPTER 1 Introduction to Hyper-V: BEFORE YOU START. vii Revision
Installing and Configuring a SQL Server 2012 Failover Cluster Edwin M Sarmiento Applies to: SQL Server 2012 SQL Server 2014 P a g e 1 Copyright This document is provided as-is. Information and views expressed
StarWind iscsi SAN & NAS: Configuring HA File Server on Windows Server 2012 for SMB NAS January 2013 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software logos are trademarks
Quick Brief This How To guide will take you through configuring Network Load Balancing and deploying MOSS 2007 in SharePoint Farm. This document will serve as prerequisite for Enterprise Portal deployment
Dell Compellent Storage Center How to Setup a Microsoft Windows Server 2012 Failover Cluster Reference Guide Dell Compellent Technical Solutions Group January 2013 THIS BEST PRACTICES GUIDE IS FOR INFORMATIONAL
istorage Server: High-Availability iscsi SAN for Windows Server 2008 & Hyper-V Clustering Tuesday, Feb 21 st, 2012 KernSafe Technologies, Inc. www.kernsafe.com Copyright KernSafe Technologies 2006-2012.
Implementing Moodle on a Windows High Availability Environment Implementing Moodle 1.9 on 2 Microsoft Load Balanced Web Front End Server and a Microsoft SQL Server 2008 R2 Cluster environment Written by:
StarWind iscsi SAN & NAS: Configuring HA Shared Storage for Scale- Out File Servers in Windows Server 2012 January 2013 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software
CREATING AN IKE IPSEC TUNNEL BETWEEN AN INTERNET SECURITY ROUTER AND A WINDOWS 2000/XP PC 1 Introduction Release date: 11/12/2003 This application note details the steps for creating an IKE IPSec VPN tunnel
StarWind iscsi SAN & NAS: Configuring HA Storage for Hyper-V October 2012 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software logos are trademarks of StarWind Software which
Multipathing I/O (MPIO) enables the use of multiple iscsi ports on a Drobo SAN to provide fault tolerance. MPIO can also boost performance of an application by load balancing traffic across multiple ports.
#1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with MARCH 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the
Load Balancing Exchange 2007 Client Access Servers using Windows Network Load- Balancing Technology In this article I will show you how you can load-balance Exchange 2007 Client Access Servers (CAS) using
Microsoft Windows Storage Server 2003 R2 Getting Started Guide Abstract This guide documents the various features available in Microsoft Windows Storage Server 2003 R2. Rev 1. 2005 Microsoft Corporation.
Improving Application Performance, Scalability, and Availability using Microsoft Windows Server 2008 and NLB with Sanbolic Melio FS and SAN Storage (A step-by-step guide) www.sanbolic.com Software to Simplify
JWCL031_appB_467-475.indd Page 467 5/12/08 11:02:46 PM user-s158 Appendix B Lab Setup Guide The Windows Server 2008 Applications Infrastructure Configuration title of the Microsoft Official Academic Course
1 How to Scale out SharePoint Server 2007 from a single server farm to a 3 server farm with Microsoft Network Load Balancing on the Web servers. Back to Basics Series By Steve Smith, MVP SharePoint Server,
Load Balancing Exchange 2007 SP1 Hub Transport Servers using Windows Network Load Balancing Technology Introduction Exchange Server 2007 (RTM and SP1) Hub Transport servers are resilient by default. This
Aqua Connect Load Balancer User Manual (Mac) Table of Contents About Aqua Connect Load Balancer... 3 System Requirements... 4 Hardware... 4 Software... 4 Installing the Load Balancer... 5 Configuration...
Updating your Network Infrastructure Technology Skills to Windows Server 2008 (Beta 3) Course 6415A: Three days; Instructor-Led Introduction This 3 day instructor-led course provides students with an understanding
Getting Started Guide Microsoft Corporation Published: December 2005 Table of Contents Getting Started Guide...1 Table of Contents...2 Get Started with Windows Server 2003 R2...4 Windows Storage Server
Step by step guide for installing highly available System Centre 2012 Virtual Machine Manager Management server: Here are the pre-requisites for a HA VMM server installation: 1. Failover clustering feature
Parallels Deploying Microsoft Clusters in Parallels Virtuozzo-Based Systems Copyright 1999-2008 Parallels, Inc. ISBN: N/A Parallels Holdings, Ltd. c/o Parallels Software, Inc. 13755 Sunrise Valley Drive
Clustering ExtremeZ-IP 4.1 Installing and Configuring ExtremeZ-IP 4.x on a Cluster Version: 1.3 Date: 10/11/05 Product Version: 4.1 Introduction This document provides instructions and background information
Attachment Save for Exchange Administrator s Guide document version 1.8 MAPILab, December 2015 Table of contents Intro... 3 1. Product Overview... 4 2. Product Architecture and Basic Concepts... 4 3. System
V Series Rapid Deployment Version 7.5 Table of Contents Module 1: First Boot Module 2: Configure P1 and N interfaces Module 3: Websense Software installation (Reporting Server) Module 4: Post installation
MOC 6435A Designing a Windows Server 2008 Network Infrastructure Course Number: 6435A Course Length: 5 Days Certification Exam This course will help you prepare for the following Microsoft exam: Exam 70647:
Introduction to Hyper-V High- Availability with Failover Clustering Lab Guide This lab is for anyone who wants to learn about Windows Server 2012 R2 Failover Clustering, focusing on configuration for Hyper-V
Installing and Using the vnios Trial The vnios Trial is a software package designed for efficient evaluation of the Infoblox vnios appliance platform. Providing the complete suite of DNS, DHCP and IPAM
Test Report Microsoft Windows 2003 Server Network Load Balancer Setup for SuperGIS Server 3 Published by: SuperGeo Technologies Inc. RD Team 2010-11-04 Content 1 Summary... 3 2 Limitations. 3 3 Software
Microsoft Office Web Apps Server 2013 Integration with SharePoint 2013 Setting up Load Balanced Office Web Apps Farm with SSL (HTTPS) December 25 th, 2015 V.1.0 Prepared by: Manoj Karunarathne MCT, MCSA,
Installation of MicroSoft Active Directory Before you start following this article you must be aware this is simply a lab setup and you need to assign relevant ip address, hostnames & domain names which
Configuring Security Features of Session Recording Summary This article provides information about the security features of Citrix Session Recording and outlines the process of configuring Session Recording
How to configure Failover Clustering for Hyper-V hosts on HP ProLiant c-class server blades with All-in-One SB600c storage blade Executive summary... 2 System requirements... 2 Hardware requirements...
Installing Windows Rights Management Services with Service Pack 2 Step-by- Step Guide Microsoft Corporation Published: October 2006 Author: Brian Lich Editor: Carolyn Eller Abstract This step-by-step guide
istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster Tuesday, December 26, 2013 KernSafe Technologies, Inc www.kernsafe.com Copyright KernSafe Technologies 2006-2013.All right reserved.
Building a Microsoft SQL Server Failover Cluster on the Interoute Virtual Data Centre User Guide cloudstore.interoute.com Introduction & Scope This document is intended as an illustration of how a Microsoft
How To - Configure Virtual Host using FQDN How To Configure Virtual Host using FQDN Applicable Version: 10.6.2 onwards Overview Virtual host implementation is based on the Destination NAT concept. Virtual
Introduction EASYLABEL 6 has several new features for saving the history of label formats. This history can include information about when label formats were edited and printed. In order to save this history,
Implementing Microsoft Windows Server Failover Clustering (WSFC) and SQL Server 2012 AlwaysOn Availability Groups in the AWS Cloud David Pae, Ulf Schoo June 2013 (Please consult http://aws.amazon.com/windows/
User Manual Onsight Management Suite Version 5.1 Another Innovation by Librestream Doc #: 400075-06 May 2012 Information in this document is subject to change without notice. Reproduction in any manner
Network Configuration Settings Many small businesses already have an existing firewall device for their local network when they purchase Microsoft Windows Small Business Server 2003. Often, these devices
StarWind iscsi SAN Software: Using StarWind with VMware ESX Server www.starwindsoftware.com Copyright 2008-2010. All rights reserved. COPYRIGHT Copyright 2008-2010. All rights reserved. No part of this
Deploying System Center 2012 R2 Configuration Manager This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Using SMI-S for Management Automation of StarWind iscsi SAN V8 beta in System Center Virtual Machine Manager 2012 R2 September 2013 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind
Course: WIN310 Student Lab Setup Guide Microsoft Windows Server 2003 Network Infrastructure (70-291) ISBN: 0-470-06887-6 STUDENT COMPUTER SETUP Hardware Requirements All hardware must be on the Microsoft
24_0672329565_ch18.qxd 9/7/07 8:37 AM Page 647 CHAPTER 18 Administering and Managing Failover Clustering Failover clustering is one of four SQL Server 2005 highavailability alternatives. Other SQL Server
Server Installation Manual 4.4.1 1. Product Information Product: BackupAgent Server Version: 4.4.1 2. Introduction BackupAgent Server has several features. The application is a web application and offers:
NSi Mobile Installation Guide Version 6.2 Revision History Version Date 1.0 October 2, 2012 2.0 September 18, 2013 2 CONTENTS TABLE OF CONTENTS PREFACE... 5 Purpose of this Document... 5 Version Compatibility...
Implementing and Managing Windows Server 2008 Clustering Course Number: 6423A Course Length: 3 Days Course Overview This instructor-led course explores Windows Server 2008 clustering and provides students
Microsoft SQL Server 2014 Installation Guide Notices 2015 XMPie Inc. All rights reserved. U.S. Patents 6948115, 7406194, 7548338, 7757169 and pending patents. JP Patent 4406364B and pending patents. Microsoft
Setting Up SSL on IIS6 for MEGA Advisor Revised: July 5, 2012 Created: February 1, 2008 Author: Melinda BODROGI CONTENTS Contents... 2 Principle... 3 Requirements... 4 Install the certification authority
StarWind iscsi SAN Software: Using StarWind with MS Cluster on Windows Server 2003 www.starwindsoftware.com Copyright 2008-2011. All rights reserved. COPYRIGHT Copyright 2008-2011. All rights reserved.
ECE/CS 4984: Wireless Networks and Mobile Systems Pre-lab and In-class Laboratory Exercise 10 (L10) Part I Objectives and Lab Materials Objective The objectives of this lab are to: Familiarize students
Cluster to Cluster Failover Using Double-Take Cluster to Cluster Failover Using Double-Take Revision 2.2.0 published March 2004 Double-Take, GeoCluster and NSI are registered trademarks of NSI Software,
Dell High Availability Solutions Guide for Microsoft Hyper-V www.dell.com support.dell.com Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer.
Course: WIN310 Student Lab Setup Guide Summer 2010 Microsoft Windows Server 2003 Network Infrastructure (70-291) ISBN: 0-470-06887-6 Published by Wiley & Sons 1 STUDENT COMPUTER SETUP Hardware Requirements
Veritas Cluster Server Database Agent for Microsoft SQL Configuration Guide Windows 2000, Windows Server 2003 5.0 11293743 Veritas Cluster Server Database Agent for Microsoft SQL Configuration Guide Copyright
Using HP Systems Insight Manager to achieve high availability for Microsoft Team Foundation Server Executive summary... 2 Audience... 2 Architecture... 3 Prerequisite... 4 Deploying AT servers... 5 Configuring
Page 1 of 10 MSDN Home > MSDN Library > Deployment Rate this page: 10 users 4.9 out of 5 Building a Highly Available and Scalable Web Farm Duwamish Online Paul Johns and Aaron Ching Microsoft Developer
Using IIS Application Request Routing to Publish Lync Server 2013 Web Services DISCLAIMER 2014 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Hyper-V, Internet Explorer, Lync,
Use QNAP NAS for Backup BACKUP EXEC 12.5 WITH QNAP NAS Copyright 2010. QNAP Systems, Inc. All Rights Reserved. V1.0 Document revision history: Date Version Changes Apr 2010 1.0 Initial release Note: Information
Multipath I/O (MPIO) enables the use of multiple iscsi ports on a Drobo SAN to provide fault tolerance. MPIO can also boost performance of an application by load balancing traffic across multiple ports.
This excerpt is taken from book Installing and Configuring SharePoint 2010 2 nd Edition. You can download this FREE ebook from the following link: http://walisystemsinc.com/installing_and_configuring_sharepoint2010_2nd_ed.php
Install MS SQL Server 2012 Express Edition Sohodox now works with SQL Server Express Edition. Earlier versions of Sohodox created and used a MS Access based database for storing indexing data and other
Installing and Configuring a SQL Server 2014 Multi-Subnet Cluster on Windows Server 2012 R2 Edwin Sarmiento, Microsoft SQL Server MVP, Microsoft Certified Master Contents Introduction... 3 Assumptions...
En Configuring the WT-4 for ftp (Ad-hoc Mode) Windows XP Introduction This document provides basic instructions on configuring the WT-4 wireless transmitter and a Windows XP Professional SP2 ftp server
Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1 This document supports the version of each product listed and supports all subsequent
Training Name Installing and Configuring Windows Server 2012 Exam Code 70 410 At Course Completion After completing this course, students will be able to: Install and configure Windows Server 2012. Describe