Thursday, October 4, 2012

SCCM 2012 - Best management ever!

First words.. I think we now have the best management tool created so far. This New 2012 takes deployment, configuring, managing systems and users into a new level. Handling up to  400.000 Clients :) 

Hands on - First experience.
I have now installed the new Configmgr on a handfull of customers, and I can confirm Microsoft have done a great job. Setup is easyer, managing and configuring is easyer but also gives you more advanced options that I love.
And yes it have much more Speed and stability.
It also gives you more visual controll.
I'll write more about this i next article.

First things first, we install on 2008 R2, or someday soon on a Server 2012. Anyway with sufficient hardware or Virtual hardware for that matter. (now remember in Virtual environments its easy to get tricked by not actually having enough physical resources available.)

In most cases I would Co-locate the SQL and SCCM on the same server to different disk drives though.
You will need a fast Server. 4 x CPUs, 32GB Memory (20GB dedicated for the SQL)
Have a look at the link below for more examples:

Now, dont make the mistake and give it to little resources.

Lets Go!

Preparing the Windows 2008 R2 Server

Asuming Your setting up a Standalone Primary Site that will be Distribution Point, Software Update Point, Application Web...   

Download and Install the .Net 4 Runtime:

(( Important to install the .Net 4 Before you have done the IIS installing/configuring ))

Installing Features and Roles With Powershell commands.

Now you can install the Feature and Roles manually or run the Powershell I've created.

This script is for 2008 R2 Server, running on 2012 requires modifications.
Paste this into the Powershell window:
Import-Module Servermanager
Add-WindowsFeature Web-Windows-Auth
Add-WindowsFeature Web-ISAPI-Ext
Add-WindowsFeature Web-Metabase
Add-WindowsFeature Web-WMI
Add-WindowsFeature BITS
Add-WindowsFeature RDC
Add-WindowsFeature NET-Framework
Add-WindowsFeature Web-Asp-Net
Add-WindowsFeature NET-HTTP-Activation
Add-WindowsFeature Web-Scripting-Tools

Add-WindowsFeature Web-Dyn-Compression

Cool, right :)

Install SQL 2008 R2 and Service Pack 2.
Collation setting: SQL_Latin1_General_CP1_CI_AS

And I would place the Instance folder path to a seperate Drive, for performance resons.
And performance messuring and troubleshooting.

SQL requires minimum 8GB memory.
SCCM and SQL located on same Server: Dedicate 50% to SQL with the amount of 8GB.
SQL located on dedicated Server: Set SQL Memory Usage to 80% of total memory.

After installation an important step is to set the Recovery model for ReportServer database to Simple!
Otherwise it will log enourmous amout of data and fill the disks.

ok, so next step. Extend AD Schema if it has not been allready With SCCM 2007.
Now, its wise to check the health of the Active Directory first. So that the DC's are replicating fine and are working. Start with a DCdiag.

If all looks well, go ahead running this with a Domain admins account that had Schema Admin access also.

There is a log normally at the Root of the Server you run this at. Se example below.

And we need to create the System Management container in System in Active Directory if its not there.
And set the approriate permissions, jump to three pictures down then.
The first steps will show you how I create the container using ADSI edit.

Then the SCCM 2012 setup!

Remember the Site Code, has to be uniqe and never used before.
And dont use AUX, CON, NUL or PRN as Site Code, not recommended by Microsoft.

And I would recommend having a dedicated disk drive for the Configmgr installation.

On this installation of mine its going to be a Stand-Alone Site.

And Yes, the Site Hierarchy cannot be changed after this. You Cannot add the Site to a Central Site.
But the Good news is, you can when you upgrade to Service Pack 1, that is very soon released.
So no worries there.  You can also migrate your SCCM 2012 site to another SCCM 2012 site.

Now, I choose Configure. So that I can choose this later, as most clients probably will communicate over http, and dont have a certificate ready. So, with this I can allow both communications later.
Or, if you want to support both http and htttps communication to clients, put a checkmark in the Clients will use HTTPS when...

With my settings it looks like this.
All clients communicate at unencrypted http.

And we are done with the initial setup, now the fun starts :-)

to be continued...

No comments:

Post a Comment