Installing System Center 2012 Configuration Manager and System Center 2012 Endpoint Protection Release Candidates

On October 26, 2011 Microsoft released System Center 2012 Configuration Manager and System Center 2012 Endpoint Protection Release Candidates.  I was anxious to get this installed in my Hyper-V lab so I downloaded the bits found at http://www.microsoft.com/download/en/details.aspx?id=27841#overview . 

 

MAKE SURE YOU READ THE SYSTEM REQUIREMENTS!

The OS is standard stuff but it’s the SQL requirements that you need to pay attention to.  DO NOT use SQL 2008 R2 !  Make sure it’s SQL 2008 SP2 with CU6.  You can use SQL 2008 R2 SP1 and CU3 only on secondary sites.  Please refer to the link at the top of this page.

 

What I did before starting System Center 2012 Configuration Manager:

1. Installed Windows 2008 R2 server.
2. Patched the server with all MS updates.
3. Installed SQL 2008.
4. Installed SQL 2008 SP2
5. Installed KB2582285

 

Now let’s get to the fun stuff:

1. Time to start the install
   
2. What to do what to do?  Before installing anything I recommend letting ConfigMgr assess the server. 
   
3. As you can see there are some things that need to be done as with pervious versions of ConfigMgr.
   
4. Schema extensions.  Let’s run SMSSETUP\BIN\X64\EXTADSCH.EXE to extend the schema. Done and the results are below.
   
5. WSUS SDK on site server.  Since this is a lab environment I’m going to install the WSUS role on the ConfigMgr server via Server Manager. 
   
   
   
   
   
   
   
   

   
   
   
   

6. Microsoft Remote Differential Compression (RDC) library registered.  Let’s fix it by adding that feature using Server Manager.
   
   
   
7. Site server has permissions to publish to Active Directory.  Done.
8. Minimum .NET Framework version.  Installed .NET 4 Framework.
   
9. SQL Server memory is limited.  It’s a VM so no big deal.  I’ll add some more on my next shutdown.
10. BITS installed.  I’m going to install the BITS feature on the ConfigMgr server via Server Manager along with the IIS WMI compatibility component.  .
    
11. All clear now.  Now let’s get the ConfigMgr updates.

    

12. Make sure your path exists or else it will bark at you.
    
13. And here come the updates.
    
14. Once the updates have been downloaded the two windows will just disappear.
15. Now comes the fun part.
    
16. Next.
    
17. I’m going to install a configuration manager primary site.  I will not use typical installation options so all screens will show up.  Next.
    
18. I accept the license terms and Next(Product key removed for blog).  Next.
    
19. I already downloaded the latest updates so no need to download them again.  I’m pointing the setup wizard to my location I saved them at. Next.
    
20. Yes it will verify them.
    
21. Server language is english.  Next.
    
22. Client Language is english.  Next.
    
23. Site code, site name, and I’ll stick with the default installation folder.  It sure is nice not to install in the Program Files (x86) folder anymore!  Yes install the Configuration Manager console. Next.
    
24. Since this is the first site it will be the primary.  Next.
    
25. Yes I know that but thanks for telling me.  Yes.
    
26. Everything looks good.  It’s the correct server name, no named instance, the DB name is find, and SSB cool.  Next.
    
27. Everything will be on the same server so this is good.  Next.
    
28. The default is only HTTPS.  Since this is a lab I’m going to configure the communication method on each site system role.  Next.
    
29. I changed both Client connections from HTTPS to HTTP.  Next.
    
30. LOL, nice.  For RC you can’t opt out of CEIPC.  Next.
    
31. It looks good to me(minus the Product Key)so let’s click next.
    
    
    
    
32. Looks good to start the install and have some fun (if fun is watching something install).
    
    
    
33. And here you have it in all it’s glory.