sql for configmgr - · pdf filesql for configmgr santos martinez sqlforconfigmgr_ebook 1...

Santos Martinez 3/6/2013

SQL FOR CONFIGMGR Cluster Configuration in Windows Server 2012 and SQL Server 2012 Version 1.0

SQL FOR CONFIGMGR SANTOS MARTINEZ

SQLforConfigMgr_Ebook

About the Author

Santos Martinez was born in Caguas, Puerto Rico in 1982. Santos have over 12 years of experience in the IT Industry,

joined Microsoft in January 2011 as Premier Field Engineer for ConfigMgr and Databases in the Central Region.

Santos has been married for 12 Years now to his Wife Karla (Pastry Chef), has a son Bryan of 11th Years old and a

Daughter Naomy of 9th. Santos is a 4th Degree Black belt in Martial Arts, like playing chess and enjoy vacations with

the family. Santos is the author of Mastering System Center 2012 Configuration Manager and Author of System

Center 2012 Configuration Manager Pocket Consultant.

Contents BUILDING WINDOWS SERVER 2012 FAIL OVER ....................................................................... 3

INSTALLING AND CONFIGURING SQL SERVER 2012 IN WINDOWS SERVER 2012 CLUSTER ................... 38

STEP UPDATING THE SQL CLUSTER NODES. ......................................................................... 75

INSTALL AND CONFIGURE SYSTEM CENTER 2012 CONFIGURATION MANAGER ON CAS. ..................... 82

CONFIGURING A GOOD MAINTENANCE PLAN. .................................................................... 148

Building Windows Server 2012 Fail Over

First lest outline how my lab setup will be, all this virtual machines are going to be hosted on my Windows 8 Hype V.

On this virtual machine after installing the Windows Server 2012, I configure it as Domain Controller. Once I finish

configuring the OS the next step is to create a new Volume of 500GB.

On the Volume H, we are going to host the VHD Files that we are going to use on the rest of our virtual machines.

To do this you need the role of iSCSI added to the Windows Server 2012, once this role is added you should be able

to create this drives.

Follow the wizard, click on new iSCSI Virtual Disk to repeat the steps. Remember to add the volumes to the same

Target, on this case I named my target as CMSQL.

The next Virtual Machines are going to be the SQL Cluster Virtual machines, this machines will be very similar to

avoid any conflict.

Machine Name: CMSQL1 and CMSQL 2

Memory: 2048, since I don’t have much memory on my lab machine all my virtual machines will have 2048.

However I recommend you using 8GB of ram minimum for each of this SQL Cluster Machines or 16GB for optimal

performance.

Disk: 100GB IDE

Network: 1 Internal & 1 Heartbeat.

OS: Windows Server 2012

Once the computer is joined we will add the volumes to the server so we can configure it, before we finish

configuring this server we have to make sure both node servers are ready for the clustering configuration.

On this Virtual Machine we have to click on iSCSI Initiator, in order to connect to the volumes.

When you click on the iSCSI initiator the following message, will be displayed. Then Click Yes to start the service.

When the iSCSI launch enter the ip address of the target, in this case is 192.168.5.1 and click Quick Connect.

If the screen don’t show the Connected status like this screen you will need to go to the CMDC and check the

initiator there.

Click on the CMSQL Target and click on Initiators, click ADD to add the initiator of the CMSQL1 and repeat the

same step for CMSQL2

Once the initiator is configured, go back to the CMSQL1 and click Quick Connect. Now you should be able to see

the target, once you perform this step click on Volumes and Devices. Click on Auto Configure and you will now be

able to see the LUN Volumes on the Volume List:

Perform this steps as needed, depending on the amount of nodes you will be using for your lab cluster. On my case is

only 2.

Now that our iSCSI Initiators are Configured, lets configure the servers for clustering. On this process we must click

on Failover Clustering, on the Add roles and features wizard.

Once the role is added, Launch Failover Cluster Manager. One of the first thing we must do is validate the cluster

nodes are ready and compatible to support this new Cluster.

Click on Validate Configuration.

Let’s validate Configuration. Enter both Node servers and Click Next

Run all test to ensure the nodes are good.

This process may take some time, depending on how much resources you have.

The results are ready and the cluster is ready to be build.

Let’s create the Cluster, on this screen click Next to begin.

Enter the Name of the cluster, CMSQL and the IP address for each network card that will be in the cluster.

Now that we are ready lest click Next

Cluster has been successfully completed. Click Finish to close the Wizard.

The next step is to configure the Disk, for this process you must create the volumes on the CMSQL. Format and

assign drive letters to them, once you do this process just Add them to the Cluster Manager and rename them as

needed.

Here are some examples of the volume creation, to complete this step.

On the Server Manager, click on Disk. Select the volume you want to create and right click New Volume.

The new Volume Wizard will launch, and will guide you through the steps needed.

Make sure to select Cluster Available Storage and select the Disk.

Follow the Wizard.

Now that our Disk is created, repeat this step as needed. Depending on how many drives you will assign to your

cluster.

Here is a sample of my final Disk Configuration.

Configure the server Quorum.

In a side note I have a small problem with the Network on the Cluster Name, was not able to update DNS or PTR.

“Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the

following reason: The handle is invalid.”

To ensure that your cluster is ready and will not have any problems on the future, I suggest to update the cluster.

Launch Failover Cluster Manager and click on Cluster Aware updating.

Before you continue you must add CAU Cluster Role.

Once this process is completed you are ready to apply the updates to your cluster.

Before we do anything else on the cluster, we must ensure the cluster have all the necessary updates to install the

product without any problems.

Now that you have the cluster updated, is time to do a few basic configuration on the drives.

Create a no_sms_on_drive.sms and drop it on the C: Drive and any other drive where you don’t want ConfigMgr to

install any sort of component. Since this cluster is for SQL I suggest this file will be on almost all drives except the

drive where you want the ConfigMgr to install the Monitoring component for ConfigMgr. If you want to do this on

the Cloud check this cool video, and follow the instructions.

Install ing and Configuring SQL Server 2012 in Windows Server 2012 Cluster

For this steps we will use SQL Server 2012 Standard Edition.

Log on to CMSQL1, and Launch the SQL installer. Click on Installation and then Click New SQL Server failover

Cluster Installation.

Click OK

On the Next Screen enter your license # or choose evaluation. Click Next to go to the Next Screen. Click I Accept

the license terms and click next.

Uncheck SP1, at this moment System Center 2012 Configuration Manager don’t support SP1 of SQL Server 2012.

Please check documentation for updates or System Center Team blog. Click Next to continue.

Ensure that there are no errors on this section and click Next.

On my lab I have decide to turn off the Firewall, this to avoid any issues with my configuration. If you want to leave

Firewall On, please make sure to create some rules for port 1433 and 4022.

Select all exempt Reporting Services.

Click Next.

This must be different than the Cluster Name, Enter the desired name and click next.

Click Next. Note* Ensure that you have good space on your drives for this installation.

Note Keep count of the static IP that you are using, if you enter an invalid ip address the installation will FAIL.

That’s it for node 1 in CMSQL1, lets configure CMSQL2.

Make sure you click on Add node to a SQL Server Failover cluster.

Step Updating the SQL Cluster Nodes.

After this we are ready to Install CU 3, Download the CU from the following link

http://support.microsoft.com/kb/2723749.

Extract and execute the install on Node1 CMSQL1.

Repeat this steps on every node.

Finish Configuring SQL Server to Support ConfigMgr, let’s begin with the Maximum amount of memory to use on

SQL Server.

The Minimum for a production should be 8192, and the Maximum should be more than 8GB.

Max Server Memory

• 50%-80% of memory if SQL co-exist with site server,

• 80%-90% if SQL is dedicated

• NOTE: Max Server memory only controls the Buffer Pool Memory

Min Server Memory

• 8GB for CAS and Pri, 4GB for Sec

• SQL does not allocate Min Server Memory at start up

• Once Buffer Pool hit Min Server Memory, SQL will not release the memory

• NOTE: Min Server memory only controls the Buffer Pool Memory

Install and Configure System Center 2012 Configuration Manager on CAS.

This Machine will be named, CMCAS.

Install all the Pre-Requirements on the server, also let’s install SQL Reporting Services.

Now SQL Reporting Services is configured.

Installation of a CAS (Optional), I just document this process to show the areas where you need to configure the

Cluster Name.

Remember to Create the System Management OU and give the necessary rights.

Hope you enjoy looking at this screen shots, sorry I haven’t complete the wording of all of them. However I hope you

figure it out by now.

Configuring a Good Maintenance Plan.

Thursday, February 28, 2013 11:42 AM

1. Log in to SQL Management Studio 2. Log in the database server 3. Expand Management 4. Right click on Maintenance Plan Wizard

Click Next

Enter the name of the task. Note* Do not use spaces as this is not supported on this area Select Separate schedule for each task.

Select Check Database integrity Reorganize Index Rebuild Index Updates statics and Click next

Move as needed, however this will not make any difference on this task. Click Next

Select Databases and enter all Databases, if you have this maintenance task for just ConfigMgr Database just select the CM_XXX database or SMS_XXX, instead of all databases.

Select a schedule to perform each maintenance task.

Select All databases, click Schedule as instead of 12AM you should select another like Example 1AM.

Select All Databases and select a specific schedule, example 2AM.

Select All Databases and the schedule to3AM.

Click Next.

Do you want more information read more here: http://technet.microsoft.com/en-us/magazine/2008.08.database.aspx

sql for configmgr - · pdf filesql for configmgr santos martinez sqlforconfigmgr_ebook 1...

Documents

configuring firewall settings for configmgr

deploying windows 10 using configmgr and mdt ronni...

app-v and configmgr whitepaper final

patching servers and clients with configmgr

configmgr! intune! azure!configmgr! intune! azure!...

app-v and configmgr 2012 white paper

bof08 - powershell & configmgr – examples from the real...

settings management in configmgr 2012, not your plain old...

discover great reasons to move to configmgr 2012 sp1

[2010, bessa; cardoso; martinez; santos] introducao as redes...

configmgr 2012 r2 & intune -...

cobaej.edu.mxcobaej.edu.mx/2013_web/publicaciones/fuerahorario/beneficiarios.pdf ·...

configmgr 2012 r2 ssrs custom reporting 1 on 1

intune web console mobile devices and pcs configmgr console...

software updates management for configmgr 2012.docx

system center 2012 – configmgr design tips

Как правильно организовать...

default reports of configmgr 2012 sp1

best ofmms2013 tdk-configmgr-2012_hadr v1.0f - publish

arias feliz encarnacion sierra matos perez gonzalez...