{"id":205,"date":"2012-05-04T15:10:13","date_gmt":"2012-05-04T19:10:13","guid":{"rendered":"http:\/\/rajdude.com\/blog\/?p=205"},"modified":"2012-05-11T14:48:49","modified_gmt":"2012-05-11T18:48:49","slug":"installing-sccm-2012","status":"publish","type":"post","link":"https:\/\/rajdude.com\/blog\/installing-sccm-2012\/","title":{"rendered":"Installing SCCM 2012"},"content":{"rendered":"

Here are my notes for installing\u00a0SCCM 2012:<\/p>\n

I have already been using SCCM\u00a02007 for a couple of years now. It has been working fine. Now SCCM\u00a02012 has come out so we have to upgrade. Note that my domain controllers are still Windows 2003 R2 SP2.<\/p>\n

I am following this very useful website<\/a>\u00a0which describes how to do an SCCM 2012 install.<\/p>\n

My running commentary as I go through the steps described in the web-page above.<\/p>\n

<\/p>\n

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<\/p>\n

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<\/p>\n

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.<\/p>\n

Step 4: When I right click on the System Management container I click \u00a0“Delegate control: I get this error:<\/p>\n

\"\"<\/a><\/p>\n

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.<\/p>\n

Strangely, now I was able to start the delegation of control wizard for “System Management”. VERY strange!<\/p>\n

Anyway, let’s go ahead.<\/p>\n

Step 5: I don’t\u00a0need to do this since I already had SCCM 2007 here in the domain.<\/p>\n

Step 6: I don’t need to do this…<\/p>\n

…since here we are going to use an existing SQL 2008 database server [separate from the SCCM 2012 server]<\/p>\n

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?<\/p>\n

Step 8: This is straightforward. I used the standalone installer which we have on our shared network drive.<\/p>\n

Step 9: This is straightforward again.<\/p>\n

Step 10 & 11: Since we already have a SQL Server 2008 VM\u00a0I am going to skip this step.<\/p>\n

Step 12: Ah ! finally starting to install SCCM 2012<\/p>\n

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.<\/p>\n

\"\"<\/a><\/p>\n

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<\/a> now.<\/p>\n

ok so now I have configured my remote SQL server with all the necessary settings. Lets run the prerequisite checks again….<\/p>\n

…..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 \ud83d\ude42<\/p>\n

Here it goes….<\/p>\n

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.\u00a0I will never have more than 100,000 clients so a CAS is not really \u00a0needed.<\/p>\n

I left the “use typical installation options” unchecked.<\/p>\n

When asked for Primary site installation options… I chose “Install the primary site as a stand-alone site”<\/p>\n

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:<\/p>\n

\"\"<\/a><\/p>\n

Ok…now to troubleshoot this…<\/p>\n

Name is right….dymanic ports are disabled…\u00a0lets 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.<\/p>\n

Just for the heck of it, I added the computer account of the SCCM2012\u00a0server to the local administrators group of the DB server……that also did not work. Hmmmm\u00a0lets enable “named pipes” in the protocols for SQL server config manager. No that did not do it too.<\/p>\n

! Eventually I found out that there was a typo in the server name….DUH!<\/p>\n

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!<\/p>\n

Then on the\u00a0page where it asks for HTTPS…I let it go with\u00a0HTTP. I don’t have that many security requirements here.<\/p>\n

Finally the setup runs a prerequisite check again. Mine failed on two points:<\/p>\n