Here are my notes for installing SCCM 2012:
I have already been using SCCM 2007 for a couple of years now. It has been working fine. Now SCCM 2012 has come out so we have to upgrade. Note that my domain controllers are still Windows 2003 R2 SP2.
I am following this very useful website which describes how to do an SCCM 2012 install.
My running commentary as I go through the steps described in the web-page above.
Step 1: I did not really create the AD users. I already have a domain admin SCCM user. I do have test users. So I think I will just go ahead to step 2
Step2: I am not sure why I would want to extract the whole DVD to my domain controller’s hard disk so I skipped this
Step 3: I looked into my AD and found that the System Management Container is already there and has my SCCM 2007 server inside it. Strangely I also had another container called “Systems Management” note the plural “systems”. I think that may be a typo from an earlier installation. I deleted it.
Step 4: When I right click on the System Management container I click “Delegate control: I get this error:
Whats up with that? Hmmm…lets research into it…. I googled but could not find a good answer. Then I noticed that the “Systems Management” container was still visible right under “System Management”. I refreshed AD Users and computers and then the second was gone.
Strangely, now I was able to start the delegation of control wizard for “System Management”. VERY strange!
Anyway, let’s go ahead.
Step 5: I don’t need to do this since I already had SCCM 2007 here in the domain.
Step 6: I don’t need to do this…
…since here we are going to use an existing SQL 2008 database server [separate from the SCCM 2012 server]
Step 7: I just followed the steps as it is. I did NOT perform this step logged in as SMSadmin, in fact I don’t have an account with that name. At this point I don’t understand what is the need for this account. Why not use a domain admin account for all these installs?
Step 8: This is straightforward. I used the standalone installer which we have on our shared network drive.
Step 9: This is straightforward again.
Step 10 & 11: Since we already have a SQL Server 2008 VM I am going to skip this step.
Step 12: Ah ! finally starting to install SCCM 2012
I’m following the procedure and after running the prerequisite checks, found out that many of the checks failed. Here is what it looks like.
After further research on the ‘net I found out that SCCM needs a lot from SQL server. More specifically it needs a very specific install of SQL server and until that it not in place the prerequisite checks will fail. I am writing a separate post for SQL server for SCCM 2012 now.
ok so now I have configured my remote SQL server with all the necessary settings. Lets run the prerequisite checks again….
…..and again it fails. I suspect it does not check for a remote SQL server and fails. Lets take a snapshot of the VM and proceed with the SCCM install. After all…this is a learning experience 🙂
Here it goes….
So right at the start in the install I decided I will “Install a configuration manager primary site”. I am NOT installing a Central administration site. I will never have more than 100,000 clients so a CAS is not really needed.
I left the “use typical installation options” unchecked.
When asked for Primary site installation options… I chose “Install the primary site as a stand-alone site”
On the “Database Information” page I typed the remote DB server name FQDN and chose a Database name. I left the instance name blank. Then I got this error:
Ok…now to troubleshoot this…
Name is right….dymanic ports are disabled… lets check the firewall again…nope…no firewall…since this is a 2003 server. I’m using my domain admin account so it does have enough rights on the DB.
Just for the heck of it, I added the computer account of the SCCM2012 server to the local administrators group of the DB server……that also did not work. Hmmmm lets enable “named pipes” in the protocols for SQL server config manager. No that did not do it too.
! Eventually I found out that there was a typo in the server name….DUH!
So I rolled back the two changes and tried to connect again. This time it gave me an error that told me that Named pipes is surely needed. Ok…lets enable that….and Viola! it connects!
Then on the page where it asks for HTTPS…I let it go with HTTP. I don’t have that many security requirements here.
Finally the setup runs a prerequisite check again. Mine failed on two points:
- Configuration Manager Setup requires that the site server computer has administrative rights on the SQL Server and management point computers.
This can be easily fixed. [I should not have rolled back my changes earlier 🙂 ] – done
- You cannot install the management point on a computer with an earlier version of the Configuration Manager client installed. Upgrade the client to the current version, remove the client, or select a different computer for the management point installation, and then try again.
ok well, lets uninstall that client here’s how
After fixing the issues, lets run the check again. Now it has passed with only 4 warnings. The important one is about SQL server memory. My SQL server VM has only 3GB. The documentation says at least 8 GB MINIMUM must be allocated. I don’t have any more RAM on the physical VMware host. I guess that will have to do. Lets see what happens. At least from an installation perspective for SCCM 2012 this is not a show stopper.
So I just hit the “Install” Button. Lets see if it will actually successfully install or error out.
Well, it ended in an error saying that it could not connect to the SQL server. VERY interesting! I suspect it is due to me increasing the RAM in the SQL server VM and the necessary reboot.
Lets try again…
Continue reading on the second attempt on installing SCCM 2012