Powershell Create Windows 2008 R2 Cluster

Teched 2010 Berlin #TEE10 #Teched

For Demo and learning Sites you need often thing that takes only a minute but when you play with it it takes more time than you want.So with this in my mind I created 3 powershell scripts that you can use for building a cluster , NLB Cluster and a MSTDC cluster resource.So If you want to create a Cluster you can do this in the GUI or with a Powershell Script.

So make sure the disk are formatted and that Your network is ok. and if you running this script in a environment with a Windows 2003 DC with DNS. You may have to set extra security to get things working.

You can find the Scripts Here : Powershell Scripts

Powershell Create Cluster Teched 2010 Berlin #TEE10 #Teched

This Cluster creation script creates a two node cluster with a witness disk at your choice. First we do the import of the modules and add the feature for failover clusters this section you have to do this on every node. You can do this remote if you want. Or run the script on the other node and abort it on the input section.


#Importing Microsoft`s PowerShell-modules
Write-Host "Install System Modules" -ForegroundColor yellow
Write-Host "Add Failover Clustering" -ForegroundColor yellow
Add-WindowsFeature Failover-Clustering
#Importing Microsoft`s PowerShell-module for administering NLB Clusters
Write-Host "Install ServerManager Modules" -ForegroundColor yellow
Import-Module ServerManager

Here we put the cluster names , netbios, clustername, IP etc.

#Variables for creating the new cluster
Write-Host "Cluster Properties Hostname / Node Names" -ForegroundColor yellow
$Clusternode1 = Read-Host "Enter ClusterNode 1 for the new cluster"
$Clusternode2 = Read-Host "Enter ClusterNode 2 for the new cluster"
$ClusterFqdn = Read-Host "Enter Cluster for the new cluster"
$ClusterIP = Read-Host "Enter cluster primary IP"
#Clear old Cluster info
Write-Host "Old Cluster Configuration Will Be ereased just to make sure" -ForegroundColor yellow
Clear-ClusterNode $Clusternode1 -force
Clear-ClusterNode $Clusternode2 -force

#Validating new cluster
Write-Host "Validate Windows 2008 R2 Cluster…" -ForegroundColor yellow
Test-Cluster $Clusternode1 -ignore network,inventory,storage

#Creating new cluster
Write-Host "Create Windows 2008 R2 Cluster…" -ForegroundColor yellow
New-Cluster -Node "$Clusternode1" -Name $ClusterFqdn -NoStorage -StaticAddress "$ClusterIP"

If you have multiple disks and you don’t know what is cluster disk 4 or 6 or what disk should be used for the Quorum disk ? Well I did make a selection that shows only the smallest disk that are available

#Show Cluster Disk Available
Write-Host "Show Cluster Disk Available…" -ForegroundColor yellow
#Show Wittness Disk Capable
Write-Host "Show Wittness disk for Cluster Available…" -ForegroundColor yellow
Get-ClusterAvailableDisk | ?{ $_.Size -lt 1573741824}

Sure You can change this for not to put in “cluster disk 1” but use only the disk number.

# Place the Wittness disk
Write-Host "Choose a Wittness disk for the Windows 2008 R2 Cluster… Must be "Cluster Disk # "" -ForegroundColor yellow
$ClusterQuorumdisk = Read-Host "Enter Wittness disk Cluster Disk number"

# Add disks to the Cluster
Write-Host "Add disks to Windows 2008 R2 Cluster…" -ForegroundColor yellow
Get-ClusterAvailableDisk | Add-ClusterDisk

Here Is the mounting off the cluster disk and I put a sleep in it this way I make sure the disk is online

#Show Wittness Disk Capable
Write-Host "Show Wittness disk for Cluster Available…" -ForegroundColor yellow
Get-ClusterAvailableDisk | ?{ $_.Size -lt 1573741824}
Start-Sleep -Seconds 5
# Change the quorum model
Write-Host "Change the Quorum model Windows 2008 R2 Cluster…" -ForegroundColor yellow
Set-ClusterQuorum -NodeAndDiskMajority $ClusterQuorumdisk

The Second node is added If you have a four node cluster just add them here

Add-Clusternode $Clusternode2 ,$Clusternode3 , $Clusternode4

But you must also use the input section above

$Clusternode3 = Read-Host "Enter ClusterNode 3 for the new cluster"

$Clusternode4 = Read-Host "Enter ClusterNode 4 for the new cluster"



# Add Cluster node
Write-Host "Add Cluster node to Windows 2008 R2 Cluster…" -ForegroundColor yellow
Add-Clusternode $Clusternode2

You can find the Scripts Here : Powershell Scripts

Powershell Create Cluster 

Teched 2010 Berlin #TEE10 #Teched

MSDTC Clustering Logfile Bug

For some enhanced settings I want to change the log file settings in the MSDTC settings.

It should been between 1 MB and 512 MB so I set my logfile setting to 512 Mb.

Invalid log file ? What ??  Why is 70 MB between 1 and 512 Mb  ?


So it turns out that 64 MB is the max logfile size for the MSDTC log.

Is it a bug ? Yes and No The error message is not clear for this You can’t set this in the GUI you can only set this in the Registery.

clip_image002 clip_image003

There is more diskspace so this can’t be the issue.

Set the LOG size above 64 MB

By default, the Maximum log file size is 64 MB. For general scenarios, one should not need more than that. But if you have a reason to increase the log file size past 64 MB, you can push this up to 512 MB provided you have a certain registry entry – MaxLogSize under MSDTC registry key.

For standalone servers, this is under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC .

For Clustered DTC, it is at HKEY_LOCAL_MACHINE\Cluster\Resources\<ResID>\MSDTCPRIVATE\MSDTC

Create a DWORD entry MaxLogSize and set it to 512 (decimal)

But What about the security settings ? IF I look I the services than I see a domain account running this services.


But On the DCOMCNFG.exe I see no service account but when I change something here the service account is reset to the Networkservice.


This is also a GUI bug If you look in the register you can see the service account is there and in the services it is also there.

So be carefull If you change something in the cluster MSDTC gui your services account will go to the default settings !

the NETWORKService

WordPress Tags: MSDTC,Logfile,want,file,Invalid,Registery,issue,Maximum,MaxLogSize,HKEY_LOCAL_MACHINE,SOFTWARE,Microsoft,Cluster,Resources,ResID,MSDTCPRIVATE,Create,DWORD,DCOMCNFG,service,Networkservice,settings,change,should,size,default,registry,entry,under,account,also

Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database


Yes there is support for SQL 2008 R2 , Soon all products are supported. But remember not all third  party’s are ready for SQL 2008 R2.

The support is divided into two phases. Phase one supports new installations of System Center Operations Manager 2007 R2. Phase two supports upgrading an existing System Center Operations Manager 2007 R2 deployment to run on a SQL Server 2008 R2 database. The existing deployment has database roles hosted on a Microsoft SQL Server 2005 Service Pack 3 (SP3) server or on a Microsoft SQL 2008 Service Pack 1 (SP1) server.


There is a great document for SQL 2008 R2 Microsoft SQL Server 2008 R2- The Best Data Platform on Windows Server 2008 R2

Microsoft sends invitations to testers for Windows 7, Server 2008 R2 SP1


You are receiving this invitation based on the quality of feedback you have provided on previous Windows programs and the Microsoft Windows release team would like you to participate in the Microsoft Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) release program, to be available shortly, as announced at the Microsoft’s TechEd conference.

Accepting this invitation will allow you to access pre-release versions of the Service Pack for the purposes of validating the release readiness. We highly value your past feedback and know we can count on you again to help us build a great new version of Windows!

The SP1 release version is not available quite yet but we need to assemble a great team of program peers early so you are ready to go when we are! If you accept this invitation you’ll be notified when the release version becomes available.

What you will get if you choose to participate

• Early access to downloadable Windows 7 SP1 and Windows Server 2008 R2 SP1 releases
• Access to private newsgroups to share information about the release with other program peers and with Microsoft staff
• The ability to report bugs and track their status
• An opportunity to help us build a better Windows by validating the release readiness

What we will ask of you if you choose to participate

• Download and install Windows 7 SP1 or Windows Server 2008 R2 SP1 on at least one PC each
• File bugs if you encounter them as well as respond to surveys as you can.
• Validation we are seeking
o Set-up and installation
o Application Experience/Compatibility
o Device Experience/Compatibility
• We ask that you actively participate in discussions on the newsgroups and share your opinions with us and others


Read more : zdnet.com

Deploying Remote Desktop Connection Broker with High Availability


This guide is intended for IT professionals, and tells how to configure Remote Desktop Connection Broker in a failover cluster. The configuration provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection

A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service. This guide describes the steps for configuring Remote Desktop Connection Broker (RD Connection Broker) in a failover cluster, as part of a configuration that provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection. As you work with the configuration in this guide, you can also learn about failover clusters and familiarize yourself with the Failover Cluster Manager snap-in in Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter.

Deploying Remote Desktop Connection Broker with High Availability  click here: Start download

Failover of clustered RD Connection Broker






Servers providing a virtual desktop


1. The user requests a connection to a virtual desktop, either a personal virtual desktop or one from a virtual desktop pool.

2. The RD Gateway receives the request.

3. The RD Gateway sends the request to a virtual machine redirector (that is, RD Session Host running in virtual machine redirection mode). The virtual machine redirector informs RD Connection Broker, and then waits for the IP address of a virtual machine.

4. RD Connection Broker requests information about a virtual machine from the RD Virtualization Host.

5. RD Connection Broker receives information about a virtual machine and then provides that information to the virtual machine redirector.

6. The virtual machine redirector communicates through the RD Gateway, providing the client with the IP address and connection information for a virtual desktop.

7. The client connects to a virtual desktop.

8. The virtual desktop is displayed on the client.

The following illustration shows the same sequence of events occurring despite the failure of one node of the cluster. Because a second cluster node is still running, it can respond to client requests as they occur.

Figure 3   Servers providing a virtual desktop after a failure


Cluster Screen Shots




RDP Connection Options



Additional Links

· Remote Desktop Services (http://go.microsoft.com/fwlink/?LinkId=154440)

· What’s New in Remote Desktop Services (http://go.microsoft.com/fwlink/?LinkId=185916)

· Install the RD Session Host Role Service (http://go.microsoft.com/fwlink/?LinkId=185917)

· About Dedicated Farm Redirection and Virtual Machine Redirection (http://go.microsoft.com/fwlink/?LinkId=185918)

· Remote Desktop Connection Broker (http://go.microsoft.com/fwlink/?LinkId=185919)

· Verify Connection broker cluster configuration (http://go.microsoft.com/fwlink/?LinkId=188508)

· Remote Desktop Services Script Repository (http://go.microsoft.com/fwlink/?LinkId=190312)

Windows Server 2008 R2 – Free eBook

It is an old item but handy to have.

Fantastic new book hot off of Microsoft Press covering Windows Server 2008 R2.

Excerpt from the book:

“This book is targeted primarily at Windows server administrators who are responsible for hands-on deployment and day-to-day management of Windows-based servers for large organizations.”

Chapter breakdown is as follows:

Chapter 1, “What’s New in Windows Server R2”

Chapter 2, “Installation and Configuration: Adding R2 to Your World”

Chapter 3, “Hyper-V: Scaling and Migrating Virtual Machines”

Chapter 4, “Remote Desktop Services and VDI: Centralizing Desktop and Application Management”

Chapter 5, “Active Directory: Improving and Automating Identity and Access”

Chapter 6, “The File Services Role”

Chapter 7, “IIS 7.5: Improving the Web Application Platform”

Chapter 8, “DirectAccess and Network Policy Server”

Chapter 9, “Other Features and Enhancements”

And best of all a free electronic version is available here:

Deployment part 1

Lately I’m a bit busy with some offline project’s with large deployments and I think there is a good blog item in it but it takes some time to build it.

Deployment is easy tools are every where but what tool do I need and what to use

Not only Microsoft tools are here but also Altiris ( Symantec )

A Long time a go I build RIS images very cool and easy to use and a bit flexible

Then there was a Automated Deployment Services I did a TAP program but my test site was not complete for the TAP. Still a Cool product

Enterprise data center administrators face significant challenges as they scale their infrastructures and deploy and administer larger numbers of Windows servers in their environments. Windows Server 2003, Automated Deployment Services (ADS), is a new component of Windows Server 2003 that helps customers address those challenges. For example, ADS includes tools for deployment automation that support operating system and application installation to dozens or even hundreds of bare metal systems in a manner that supports security and auditing without administrator input.

As this white paper describes, the new set of ADS imaging tools developed by Microsoft help to offer a secure, rapid, and flexible deployment of both Windows 2000 Server and Windows Server 2003. In addition, ADS enables script-based administration of a large number of Windows servers.


Then there was BDD

Desktop Deployment for Midsize Businesses

Business Desktop Deployment (BDD), or deploying Microsoft Windows, Office, and other applications to client computers, is a vital task for organizations of all sizes. You can deploy desktops using several methods depending on the number of client systems involved, available infrastructure, and skill level of IT staff. In very small organizations, BDD often means a hands-on, CD-based installation or purchase of systems with OEM versions of the operating system and applications already installed. In larger organizations, more advanced deployment processes and technologies can simplify and automate deployment; provide for remote configuration and management; and streamline disaster recovery.

The methods and tools you choose depend on your current IT environment. Environments for BDD fall into three primary categories: limited, basic, and well-managed. Table 1 identifies components and characteristics of each environment.


Business Desktop Deployment involves several key aspects, from planning to post-deployment management. The following sections describe these aspects for each target infrastructure.

Limited Management Infrastructure

The following list describes issues and solutions for desktop deployment for organizations with limited management infrastructure.

Planning and Assessment. A successful deployment requires inventorying existing target client systems, operating systems, and applications and identifying which systems and applications will be upgraded. In smaller environments, custom Windows Management Instrumentation (WMI) scripts and scripts included in the Windows Resource Kits can be used to inventory systems and applications.

Application Compatibility. Microsoft Windows XP and Office 2003 provide full compatibility with one another, but many deployment scenarios involve additional applications and older versions. Application compatibility analysis and testing help ensure existing applications will run on the new desktops and that any compatibility issues are remediated. For limited management environments, the Windows XP Help and Support Center and Program Compatibility Wizard (included with Windows XP) and the Windows Catalog are key compatibility resources. Older Windows applications can be configured with compatibility settings to enable them to run under Windows XP through the Compatibility tab page of the application’s properties.
See the following links for additional resources and solutions:
Resolving Application Compatibility Issues with Compatibility Administrator
Program Compatibility Wizard
Windows Catalog
Windows XP Upgrade Advisor

User State Migration. Desktop deployment includes migrating user documents, files, application settings, and other data to target systems. The Files and Settings Transfer Wizard in Windows XP is a great method for limited management environments.
See the following links for additional resources and solutions:
User State Migration: Overview
User State Migration Tool

Deployment and Installation. In limited management environments, the operating system and applications are often preinstalled on purchased systems. Additional deployment is generally through manual, CD-based installation.
See the following links for additional resources and solutions:
Deploying a Simple Managed Environment
Windows Deployment and Resource Kits

Supplemental Applications. The Windows XP and Office 2003 combination form the core client tools for many organizations, but often needs to be supplemented with other applications. Manual installation is often used in limited management environments to install these supplemental applications.

Security and Patching. It’s important to keep up-to-date with operating system and application updates. The Microsoft Update Web site, which combines Windows and Office updates, and Automatic Updates help limited management environments stay current.

And Now there is : Windows Deployment Services

Applies To: Windows Server 2008, Windows Server 2008 R2

This guide contains step-by-step guidance for how to install and configure the most common scenarios for Windows® Deployment Services (sometimes called “WDS”) in Windows Server® 2008 and Windows Server 2008 R2. Note that you cannot use Windows Deployment Services with the Server Core installation option. To download the Windows Deployment Services documentation (including a step-by-step guide, deployment content, and WDSUTIL command-line syntax), see http://go.microsoft.com/fwlink/?LinkId=89381.

What is Windows Deployment Services?

Windows Deployment Services is the updated and redesigned version of Remote Installation Services (RIS). Windows Deployment Services enables you to deploy Windows operating systems over the network, which means that you do not have to install each operating system directly from a CD or DVD.

For information about what is new or included in your version of Windows Deployment Services, see Windows Deployment Services: What’s New (http://go.microsoft.com/fwlink/?LinkId=140114).

Who should use this guide?

Windows Deployment Services is intended for deployment specialists who are responsible for the deployment of Windows operating systems. This guide assumes that you have a working knowledge of common desktop deployment technologies, as well as networking components such as Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory® Domain Services (AD DS). The target audiences are:

  • Deployment specialists interested in deploying Windows images to computers.
  • IT planners, designers, or analysts evaluating Windows Server 2008 or Windows Server 2008 R2.

More here http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx

And the tools are here :

Microsoft Deployment Toolkit

Deploy Windows 7, Windows Server 2008 R2, Windows Vista, Windows XP, Windows Server 2008 and Microsoft Office products

Microsoft Deployment Toolkit 2010

Microsoft Deployment Toolkit 2010 (MDT 2010) provides a common console with the comprehensive tools and guidance needed to efficiently manage deployment of Windows 7 and Windows Server 2008 R2. Microsoft Deployment Toolkit 2010 is the recommended process and toolset to automate desktop and server deployment. Microsoft Deployment Toolkit 2010 provides detailed guidance and job aids for every organizational role involved with large-scale deployment projects.

One-click downloads for:

Looking for other free, authoritative resources to help you proactively plan, integrate and operate IT systems? Visit the Solution Accelerators Home Page.

Deployment TechCenter


This is the first in a range I will try to build a complete now days server I know there are plenty around but lots of them are 2008 and not R2  in a few day’s I hope to fix this first I have to build a sharepoint farm 😉

Help reduce the cost and complexity of compliance with the IT Compli­ance Management Series for Windows


Download the Beta releases, and take advantage of this opportunity to provide valuable feedback on these new compliance guides and resources for Win­dows® 7, Windows Server® 2008, and Windows Server 2008 R2.

Download the IT Compliance Management Series for Windows – Beta at: http://go.microsoft.com/fwlink/?linkid=56419

The Compliance Solution Accelerators team has just released valuable extensions to the IT Compliance Management Series. And with “Companies now spend(ing) about 8.5 percent of their IT budgets on compliance needs," says French Caldwell, an analyst at Gartner (CIO Magazine, Sept 2007), these couldn’t be more timely. These new offerings provide spe­cific technical guidance and resources for Windows 7, Windows Server 2008 and Windows Server 2008 R2.

The IT Compliance Management Series will help you shift the burden of your IT gov­ernance, risk, and compliance (GRC) efforts from people to IT systems and implement controls to address IT GRC requirements that apply to your organization. This series is intended for IT managers and IT professionals who must plan, implement, or configure Microsoft products and who want to ensure that IT GRC requirements are addressed efficiently and effectively.

During this Beta period, reviewers are being asked to provide feedback on guides, re­sources, and compliance baselines that provide direction on how to enable Windows 7, Windows Server 2008, and Windows Server 2008 R2 to support your organization’s key IT GRC initiatives by taking advantage of features and technology inherent in the operating systems. Successful implementation of these recommendations will allow or­ganizations to simplify the enforcement and management of their IT GRC objectives.

Looking for other Windows 7 resources from the Solution Accelerators team? Check out the Windows Desktop Solution Accelerators page.

Want more Windows Server 2008 R2 resources? Visit the Windows Server 2008 R2 So­lution Accelerators page.


Solution Accelerators for every stage of Windows Server 2008 R2 migration


Infrastructure Planning and Design (IPD) guides
Streamline the design processes for Windows Server 2008 roles and Hyper-V server virtualization.

Microsoft Assessment and Planning (MAP) Toolkit 4.0
Generate custom proposals and reporting for Windows Server 2008 R2 hardware compatibility and Hyper-V virtualization.


Microsoft Deployment Toolkit (MDT) 2010
For faster, cost effective, automated Windows Server 2008 R2 deployment.

Windows Server 2008 Security Compliance Management (SCM) Toolkit
Meet security and compliance requirements.

Operate/ Manage

Offline Virtual Machine Servicing Tool
Keep offline virtualized servers up to date, protected from security threats.

Service Level Dashboard 2.0 for System Center Operations Manager 2007 R2
Keep mission-critical applications available and running at peak performance.

Microsoft Operations Framework (MOF)
Gain a competitive advantage through increased efficiency and lower costs.

Teched 2009 Clustering new documentation migration to a R2 cluster

Just a quick recap on the cluster sheets this week, there were a lot of questions how do I solve the split brain thing.

Well make sure you have one cluster node up and do start the services with force state like below

net start clussvc /fixquorum

Or with powershell

Start-ClusterNode –FixQuorum


image image image

So just now there is new documentation discussing special cases and consideration when migration to a R2 cluster (from 2003, 2008 or R2). Additional considerations needed for DFS-Replication, DHCP, (MS)DTC, Exchange, File Server, MSMQ, Print, SQL, VMs and 3rd Party

Resources. Link: http://technet.microsoft.com/en-us/library/ee791924(WS.10).aspx Our general R2 migration guide is here: http://technet.microsoft.com/en-us/library/cc730990.aspx

Additional detailed guidance for the following migrations on a cluster is also available:

DHCP: http://technet.microsoft.com/en-us/library/ee460952(WS.10).aspx

Hyper-V: http://support.microsoft.com/kb/957256

Steps for migrating from R2 RC to R2 RTM are here: http://blogs.msdn.com/clustering/archive/2009/09/02/9890272.aspx

Tech-ed sessions


There where today alot of sessions because teched is fully booked you must come early or else your seat is gone this is a bad thing, I had this blue shirt with microsoft on it and Staf on my badge so I have been kicked out in a cluster session. this to make room for other people , Microsoft personal where not allowed –| .

So you can see clustering is getting popular and why well Hyper-V wants it for the cluster shared volumes ( CSV ) and with this you can do live migration of hyper-v VM’s . The CSV volumes are not suitable for file sharing it will not work the volumes are getting corrupted if you do !

SVR319 Multi-Site Clustering with Windows Server 2008 R2

This session is all about clustering the do’s and don’t

What if you have only one datacenter ?       Well multi-site clustering is now here          You can give the network interface a “OR” option

image  image image

If you have only one san But you need 24×7 uptime than you san needs replication but how ?

image image image

So make a choice whay do you need sync or A-sync and very important is the cluster validation tool.

 image here is a overview of the new Witness disk the old quorum disk.

CLI306 How-to: Windows 7 Deployment on a Stick!

What do you need

image image

use the MDT 2010 tool kit and make sure you use imagex ! here you can image your system and create a image for redeploying in the old days this was a riprep image you all know this was sometimes a pain in the % . now it rocks.

The POS session is also about deploying and imagex

EMB203 Using Windows Deployment Services and Microsoft System Center to Deploy and Manage a Point-of-Service (POS) System Running POSReady

at this session there where only a few people so was it not interesting ? well below are a view of the PPTX.

image image image

As you can see SCCM come across in most of the products now days time to learn SCCM the new SMS 2003 yes or no. I like the product but only for OS deployment ??? no use WDS think create build and deploy TCBD is my opinion easy to do test it in your hyper-v environment build a DC, WDS , deploy windows 7 and capture a image with imagex and put the image.wim file in the wds and redeploy it to a new machine so 4 VM’s can do this. hardware one quadcore  and 4 gb memory a basic desktop now days.

image image

there is more to come but you have to see this stuff slides are fine but the realthing is better.


And remember there will be NO 32 bit windows 2008 R2 OS !

on some slides microsoft uses the x86 but this means not always that it is x32 no it means this is a intel based machine.

I had a lot of questions of when will there be a 32 bit windows 2008 R2 server ? why do you want to have this server for testing ? but you have hyper-v for testing ?

Well suppose you have running windows 7 and want to do a virtual windows 2008 R2 then you have a problem… to
morrow a new day and fresh questions.

Annoying SQL 2008 SP1 Cluster bug

SQL 2008 Cluster The current SKU is invalid.

Invalid SKU Error when Adding a Node to a SQL 2008 Cluster

Invalid SKU Error when Adding a Node to a SQL 2008 Cluster

After setting up several SQL 2008 Clusters I ran in to this problem I think it is only on windows 2003 x64 enterprise but I’m not sure.

The issue is this: After installing the first SQL 2008 Sp1 node you want to add the second node , you do the add node to the SQL server failover cluster and follow the wizard.

Invalid SKU Error when Adding a Node to a SQL 2008 Cluster

But after checking the setup support rules , and the product key check this message pops up that “The current SKU is invalid “ What is this I did install 2 other two node clusters with no problem, is the installation source broken or need the new server a kernel restart.

SQL 2008 Sp1 setup Invalid SKU Error when Adding a Node to a SQL 2008 Cluster

No it is a BUG , yes a bug : http://support.microsoft.com/kb/957459/ I downloaded the fix (360784_intl_x64_zip.exe  178 MB)

In my case it did not work ;-( , the problem is clear the product key is not right or the check is no working. The location of the product key is in the defaultsetup.ini I fixed this ini with the SP1 location after I slipstreamed the SP1 in SQL 2008. I removed the defaultsetup.ini and run the add node setup again and I get the product key popup



And there I copied the product key from the defaultsetup.ini and the Installation worked. I know this is not nice but without the defaultsetup.ini my product key is not available in the source so no unauthorized installs can take place.



Now that I have a workaround for the installation crew I checked the microsoft site if there is a bug filed and yeb there is. 

Another Cluster issue fixed.


Clustering SQL 2008 on Windows 2008 R2 what can go wrong


Ok this post is not only on how to setup a sql 2008 cluster but more on what can go wrong and more important how to solve this.

As much as I hate an installation that goes wrong and you spent day’s on how to solve this because you can ‘t bing your problem.

Here is what I have on hardware in this case a two node cluster windows 2008 R2 RC build 7100 and the SQL 2008 DVD

I have more than enough disk space in may case I have two disk of 100 GB but I will use only one disk per instance this is not Best Practice but handy in a test lab.

So I downloaded the SQL DVD and hit the setup.

clip_image002 clip_image004 clip_image006

I love the warning but as every one I do not read it and click run program 2x , finaly there is the setup splash.

So First I do the Prereq. This is nice this way you can see if the configuration you use is ok for the job.

clip_image008 clip_image010 clip_image012

Well I have a pending reboot and a .NET security warning , mmm strange I can’t connect to the Web .  first a reboot.

Since this is not tux I rebooted the kernel.

clip_image014  clip_image016 clip_image018

ok after the Reboot I hit setup again and I click the setup failover cluster , now there is no pending reboot here and I can go further

clip_image020 clip_image022 clip_image024

Remember that You must use the same product key on your Cluster nodes !!!!

Yes I agree who reads this any way I just wanna do a fast setup my boss want the sql cluster ready today. Yes I can.


clip_image026 clip_image028 clip_image030

Yes next
next eh No MSDTC ? do I need it ? mmmm network binding error firewall error can’t the setup handle this for me ?

clip_image032 clip_image034 

Troubleshoot the install errors:


Ok it seems is will not be a next next finish I agree setup Right. and this is whay you must read the guides!! except in a demo where things must go wrong.

So first we do a MSDTC setup this is needes if You wanna do Transactions

We also need to cluster the Microsoft Distributed Transaction Coordinator resource (MSDTC). Although MS DTC is not required for Database Engine-only installation, without it being clustered, you would receive a warning message during the setup configuration checks because of the incompliance of the Cluster_IsDTCClustered rule. If you need to install SSIS, Workstation Components or use distributed transactions, then MS DTC must be clustered. In our example, the MSDTC resource is clustered in a group called "Your name MSDTC Group". This group contains the MSDTC resource, a shared Physical Disk T: to store MSDTC log files, a network name, and an IP Address. Before clustering MSDTC, network MSDTC access must be enabled on both nodes. For more information, please refer to http://support.microsoft.com/kb/817064/. The MSCS Cluster Service account will need to have public rights to SQL Server so that it can run SELECT @@servername for the IsAlive cluster checks.

Setup MSDTC :

This is the easy part Go in you FCM ( Failover Cluster Manger ) configure a service or application and select the MSDTC.

clip_image002[4] clip_image004[4] clip_image006[4]

So I give the MSDTC the IP and point it to the new disk for the log files. I use a separate disk for the MSDTC so that I can move the resource where and whan I want.

clip_image008[4] clip_image010[4] clip_image012[4]


Done I just created my MSDTC failover cluster resource !

Network binding Order : 

clip_image032 This error is easy to fix and it is new I have never seen this error ( or I did always ther right steps ) so go to your network tab eh yes but where is it. well it take me almost a minute to find it.

Go to Control Panel\Network and Internet\Network Connections

click organize and layout and check the menu bar now you can go to advanced.

clip_image016[4] clip_image018[4] Change the order and done.

Back to the SQL backup :


So Again I swing the SQL setup

clip_image036 clip_image038 clip_image040

I named the first instance and changed the default

clip_image042 clip_image044 clip_image046

clip_image048 clip_image050 clip_image052

So whay would you use DHCP ?? just give it a fixed IP

clip_image054 clip_image056 clip_image058

I use the same service account for all the services added the administrator to the sql admins.  You should create a group and put users in i. but you can do this later.

clip_image060  What is this \\?\volume{

Ok this is strange I give the SQL server disk 4 , lets see what the problem is. Oh ok this is a CSV disk CSV = cluster shared volume.

You can’t use this disk!.

So I added a fresh new iscsi target to the nodes and run the setup again.

clip_image061 clip_image063 clip_image065

No errors

clip_image067  clip_image069 clip_image071 

clip_image073 clip_image075 clip_image077

As in the settings above I filling the items and go.

clip_image079 clip_image081 clip_image083

Ok Now I have more disks to use and I do not choose a CSV volume , and no I do not wanna use DHCP

clip_image085 clip_image087 clip_image089

Same services account

clip_image091 clip_image093 clip_image095

Now as you can see I can see the disk letter this is great and almost done.

clip_image097 clip_image099 clip_image101

Yes I do believe in the error roporting this way we can make the product better.

clip_image103 clip_image105 clip_image107

No the filestream does not need an update I’m using Windows 2008 R2 RC state of the art server. I saved the config file maybe I do a command line setup later if I want to reinstall this cluster.

C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090604_212627\ConfigurationFile.ini

clip_image109 clip_image111

As you can see the ini file is easy to read and to adjust where needed.

clip_image113 clip_image115 clip_image117

What another error ;-( kerberos , Well this is a nice error bink it and you will see not much errors or resolution about this.

Did I miss something I solved all the other errors.

So what is it :


Controls whether or not the Network Name resource can be brought online without Kerberos authentication. The choices are:

RequireKerberos is set to 1. The next time this resource is brought online, clients using this resource will be authenticated using Kerberos. That is, a computer object for the Network Name resource will be created or updated before that resource comes online.

RequireKerberos is set to 0. Disables this option, that is, no computer object is created for the Network Name resource. This is the default. The Cluster service will try to detect if a computer object already exists for the Network Name resource; if a computer object is present, the resource will fail to come online. If this property were previously set to 1, setting it back to zero will disable the computer object created for this Network Name resource, if any.

Do not rename a Network Name resource and change the Kerberos authentication setting at the same time. Instead, allow time for changes to replicate after performing each action.

clip_image119 clip_image121 clip_image123

When I looked at my install I can’t see anything about a sql cluster only the network name. ah no ip settings.let me fix this.

clip_image125 clip_image127 clip_image129

Done fixed the IP and bring it online start the sql manager and go. NO  it won’t work. You know whay. YOU missed the error in the beginning.

SQL 2008 cluster this is saying USE SP1  my download came without sp1 and I can download sp1 but how to use it.

Well it is not easy, yes it is.

First copy the files from the DVD to a disk location.

use robocopy .

robocopy “sqlDVD” to “ disklocation” ( change the names !)

download the sp1 sql 2008 software details.aspx-FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19

Extract the sp1 files to the hardisk loaction

SQLServer2008SP1-KB968369-x86-ENU.exe /x:v:\SQLSERVER2008_FullSP1\PCU
SQLServer2008SP1-KB968369-x64-ENU.exe /x:v:\SQLSERVER2008_FullSP1\PCU
SQLServer2008SP1-KB968369-ia64-ENU.exe /x:v:\SQLSERVER2008_FullSP1\PCU

Change the Setup files

robocopy SQLSERVER2008_FullSP1\PCU v:\SQLSERVER2008_FullSP1 setup.rll
robocopy SQLSERVER2008_FullSP1\PCU v:\SQLSERVER2008_FullSP1 setup.exe

robocopy v:\SQLSERVER2008_FullSP1\pcu\ia64 v:\SQLSERVER2008_FullSP1\ia64 /xf  Microsoft.SQL.Chainer.PackageData.dll
robocopy v:\SQLSERVER2008_FullSP1\pcu\x64 v:\SQLSERVER2008_FullSP1\x64 /xf  Microsoft.SQL.Chainer.PackageData.dll
robocopy v:\SQLSERVER2008_FullSP1\pcu\x86 v:\SQLSERVER2008_FullSP1\x86 /xf  Microsoft.SQL.Chainer.PackageData.dll

and merge the sp1 files.

And change the installation path in the DefaultSetup.ini located in the ia64,x64,x86


So I did the complete setup again but now with SP1 and I can login in the SQL manager

SQL 2008 cluster SQL 2008 cluster SQL 2008 cluster


Watch the servername instance you can see this in de FC manager netbios name and sql name.

Now that we are installed SQL on node 2 we must install SQL2008 SP1 on node 2.

clip_image002[6] clip_image004[6] clip_image006[6]

Just add the node to the cluster and follow the guide fillin the serial

clip_image008[6] clip_image010[6] clip_image012[6]

clip_image014[10] image SQL 2008 cluster

Fill in the password and next

image SQL 2008 cluster

I hope I showed you that alot can go wrong and a setup can always be tricky if you want to to this to fast.

I will mesh this configuration so that I hopefully have
nice errors to solve.

In the next session I will add a second instance.

positive comments are welcome