How to - System Centre Configuration Manager - Part 2 (Installation)
by, 26th January 2012 at 11:16 PM (11759 Views)
Welcome to Part 2 of my System Centre Configuration Manager (SCCM) series – desigined to show you how to get a basic setup up and running in a day not a week!
So, Im guessing you’ve gone through Part 1 – and are now ready to get on with the actual install.
You will be needing those two AD accounts - SCCMAdmin and SCCMClient – so make sure you have them ready.
Starting the Install
STOP – SCCM needs to extend the AD Schema. If you have not installed SCCM before, you will need to do this. Checklist….
1. Where is your Schema Master role (it will be one of your Domain Controllers)
2. You can only update the Schema if you are a Schema Admin. Give the user account membership of that group via AD Users and Computers
3. Remote Desktop to that server, and access the SCCM Install CD from that server (you need to share it – then you can use \\SERVERNAME\DRIVE)
4. Open an elevated Command Prompt, and run extADSch.exe method and located it on the SCCM 2007 DVD (..\SMSSETUP\BIN\I386)
Install "Take 2"
Back to our install….
On your SCCM server, run the Setup file, and then on the splash screen, select Install. Now, lets walk through the setup and its options…
First we will get the usual “Welcome screen”, which you can click through. Next up – what to do! Choose the first option, Install a Configuration Manager site server.
Now time to review the licence – go on, read it if you must! Of course, we always do. Next we get to choose the type of installation, choose Custom, so that it is set up as we want.
Next up – choosing a site type. As you are reading this article – im guessing you are new to SCCM – so it will always be “Primary site”. You would use “Secondary” in branch scenarios, or in some upgrades.
Time to choose whether you want to be in the improvement programme; enter your license key, and then an install directory.
Lets get more serious
The “Site Code” section is where things start to get interesting. Choose something sensible – like a short version of your domain name etc; and give a description. You then need to choose a mode. Everyone will tell you to use “Native mode” – and yes, this is more secure – but it will also take you longer to set up. Ive run both, and have always found “Mixed mode” to be more stable. So – choose “Mixed”.
The next screen asks about the agents you want to use – this is why we chose “Custom” setup.
Add Hardware Inventory, Software Inventory, Advertised Programs, Remote Tools. You can add others if you want, but these are the ones we are going to deal with.
We are nearly there now – most important step, where is your database. Yes, you can use clustered SQL here too. Point the setup at your SQL instance. You can also choose your DB Name. Next you need the specify the “Provider” – and as the dialog says, on clustered SQL, this cannot be on the SQL. I tend to use the SCCM box itself.
The SMS Provider is used by the Configuration Manager console, Resource Explorer, tools and custom scripts used by Configuration Manager Admins to access site information stored in the site database.
The Management Point is your next choice – again, I tend to use the full name (dotted domain – ie FQDN) of the SCCM Server. TCPIP Ports are up next, don’t mess with this unless you need to. There’s just no need!
You are then going to do a quick net connection to grab the latest SCCM components. You can download these in advance if you want to though.
A pre-requisite check will then be done – all should be good to go. So sit back, whilst it installs – and it can take quite a while!
Now – Ive changed my mind a bit on how to complete this blog series. Part 3 is going to deal with your initial configuration, and Part 4 will deal with doing a build and capture of and OS – and push it out. Part 5 will deal with what to do with Applications. Part 6 will bring Part 4 and Part 5 together and show you how I run SCCM live now, to build any machine and do automatic software deployments based on AD groups.
Total Trackbacks 0