A Guide to Installing SCCM 2007 SP1 in Mixed Mode
Do you want or need to install Configuration Manager System Center 2007 SP1? Here is a guided tour:
Here is an outline of the small lab environment that was used for this SCCM install. Pay special attention to the listed components that are either prerequisites for installing SCCM or are needed later to use the different SCCM roles. (Please note that later versions of any element will work too) Here is a complete list of what roles use what components. I also found a neat installation checklist you may want to check out before getting started.
My Lab
SCCM1 – You guessed it. This is where we will install SCCM
Windows Server 2003 R2, 32bit
- .Net Framework 2.0
- Internet Information Services 6.0 (IIS)
- Active Server Pages
- Web-based Distributed Authoring and Versioning ( WebDAV)
- Background Intelligent Transfer Service 2.0 (BITS)
- Microsoft Management Console 3.0 (MMC)
- Windows Remote Management 1.1 (WinRM)
- Windows Server Update Services (WSUS) – Administrator Console Only
SQL Server 2005 SP2
- Database Services
- Workstation Components
DC1 – An active directory domain controller.
Windows Server 2003 R2, 32bit
System Center Configuration Manager Installation Steps
1. Extend the Active Directory Schema
Log on to your Domain Controller as the all powerful admin and run the schema extension tool. If you are doing this in a production environment there are some additional precautions you should take before touching the schema. You can see the suggested procedure here. But in my lab why not rush ahead and risk a catastrophe. Isn’t that half the fun? The tool is named ExtADSch.exe and can be found on the SCCM installation disc at \SMSSETUP\BIN\I386.
2. Run the Prerequisite Checker
Go to the server you want to install SCCM (SCCM1 in my case) and pop in the installation disc. Run SPLASH.HTA if it doesn’t start automatically.
Click Run the Prerequisite Checker.
This is the first installation of Configuration Manager on this network so choose the Primary site radio button. Enter the server name where your SQL Server lives in the first box. In the second box enter the server name that has WSUS SDK on it. The last box is for the name of the server that will be your management point. This time you will need the fully qualified domain name. Your environment may be different then mine so adjust accordingly. That’s it for this page. Click OK.
Now that you have told the prereq check where to look it will see what you are missing. Double click any item to get details about how to fix the problem. After you have fixed the issues run the prereq checker again to make sure they have cleared.
3. Configure the Active Directory System Container so that the SCCM site server has full control rights.
Back on the Domain Controller open up Active Directory Users and Computers. Make sure you have the advance view turned on. Right click on the System Container and go to Security tab in Properties. Click Add. Make a computers object with the name and location of your Configuration Manager machine and click OK.
In the Advanced Settings make sure your SCCM object and all its child objects have full control.
4. Install!!
Run SPLASH.HTA again and click Configuration Manger 2007 SP1 under the Install heading. Click Next on the first induction screen.
Available Setup Options: On the second screen choose Install a Confutation Manger site server. There are not very many options available if this is your first SCCM installation.
Microsoft Software License Terms: Read every last word of the license terms. You can even print it and read it over and over just for fun. When you are done, mark the checkbox that says I accept these license terms. Don’t forget your friend the Next button.
Installation Settings: Choose Custom settings and then click Next. You could just choose Simple settings, but where is the fun in that?
Site Type: The next screen is asking if this is the primary site or a secondary site. This is the first instance of SCCM on this network so of course we go with Primary site.
Customer Experience Improvement Program Configuration: Yeah! You are invited…to let Microsoft watch your every move. Just kidding. I don’t think Microsoft will get anything useful from this temporary lab so I chose No this time.
Product Key: Insert your product key and click Next.
Destination Folder: On the next screen provide a destination Folder where SCCM will be installed. Oh just leave the default and click Next.
Site Settings: Now you have to make an actual choice! It is an arbitrary one but a choice none the less. What will your Site code be? As it explains on the screen- a site code is a 3 character unique identifier for this SCCM site. You can’t change it so choose wisely! The second box is for an unofficial nickname for your site. Fill in these two boxes and…yawn…click Next.
Site Mode: As stated in the title of this article we are using Mixed Mode. Here is some more information about the scarier but more secure Native Mode.
Client Agent Selection: Next you get to choose which client agents you will be able to use. The agent names are pretty self explanatory but if you want more information here is an article on client agents by Brian Tucker. The more of them you click the more you get to play with!
Database Server: On this screen you need to provide the server location of your SQL Server. The second box is the site database name. There is a naming convention you need to be aware of. Use the letters SMS then an underscore then your site code. Even though SCCM is not longer called SMS that is still the naming convention we use here.
SMS Provider Settings: The SMS Provider should live on the same server as your SQL Server. It communicates with the database. So enter the name and then click Next.
Management Point: You have to have at least one Management Point to communication with clients so why not add it to the Configuration Manager Site System. This time you will need a fully qualified domain name.
Port Settings: just use the default unless your production environment requires different. HTTPS is grayed out because it only works with Native Mode.
Updated Prerequisite Components: Hasn’t you mama always told you to do your updates? Leave the Check for updates and download newer versions to an alternate path chosen then click Next.
Updated Prerequisite Component Path: Make a folder for your new updates and then enter its path here. The wizard will not accept a path that does not exist. After you click Next there may be some updates that download. This could take several minutes. When it is done a popup box will tell you, “Successfully downloaded all prerequisite components.” Click OK here and then it’s time for the next screen.
Settings Summary: This is a review of everything you choose throughout the wizard. If you need to change something you need to click the back button until you get back to the corresponding screen. After you click Next the Prerequisite Checker will run itself one more time.
Resolve any errors and read any warnings to make sure they aren’t deal breakers. Then click the big button that says Begin Install!
Setup Action Status Monitoring: Here you will see actions go from Not Started to In Process to Competed. Yeah!
Eventually you will get a screen that informs you that the setup completes successfully (I hope). Click Finish and you’re done!
Join me next time for a step by step guide to upgrading this install to System Center Configuration Manager 2007 R2. I will talk a little about the new features available in R2 as well.
Oh and if you want to learn more about System Center Configuration manager check out our training course that is now available.
Related Posts:
- A Guide to Upgrading to SCCM 2007 R2
- System Center Configuration Manager 2007 R2: Information, Training, Certification, and Resources
- System Center Configuration Manager 70-401 Certification Guide
- Server 2008: Installing Distributed File System (DFS)
- Installing Hyper-V Server Role in 7 Easy Steps
3 Responses to “A Guide to Installing SCCM 2007 SP1 in Mixed Mode”
Leave A Comment:
Socialize
Windows Server HQ by Train Signal.com » A Guide to Upgrading to SCCM 2007 R2 Says:
June 26th, 2009 at 10:46 am
[...] Last time I walked you through installing System Center Configuration Manager 2007 SP1. However, there are some invaluable new features in SCCM R2 that you will miss out on unless you upgrade. After a quick overview of the new features I will show you the steps for upgrading to R2. [...]
Sushant C Says:
July 23rd, 2009 at 12:02 am
Nice document i think this will help me to configure SCCM but also wanted to know is the sever on which we are installing SCCM is under domain or only the m/cs on which we have to install SCCM client should under domain?
Scott Lowe Says:
July 23rd, 2009 at 11:42 pm
Sushant,
All of the machines in all of the examples – as well as the installation example – are part of the AD domain. So, the SCCM server is a member server in the domain and separate from the domain controller.
I hope this helps!
Scott