using SCCM 2012 beta 2 in a LAB - Part 1. Installation

[anyweb]

UPDATE: This post has been superseded, please review all the NEW Content (RTM and onwards) here

 

http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/

 

 

 

 

 

 

 

If you've been following my previous series of guides on System Center Configuration Manager 2012 Beta 1, then you'll know where this is going, we are going to install System Center Configuration Manager 2012 beta 2 from scratch and configure it, use it, test it, learn it.

 

 

 

Technet Recommended Reading:-

 

Getting Started with Configuration Manager 2012 - http://technet.micro...y/gg682144.aspx

What’s New in Configuration Manager - http://technet.micro...y/gg699359.aspx

Supported Configurations for Configuration Manager - http://technet.micro...y/gg682077.aspx

Planning for Site Systems in Configuration Manager - http://technet.micro...y/gg712282.aspx

Install Sites and Create a Hierarchy for Configuration Manager - http://technet.micro...y/gg712320.aspx

Technical Reference for Site Communications in Configuration Manager - http://technet.micro...y/gg712990.aspx

Migrating from Configuration Manager 2007 to Configuration Manager 2012 - http://technet.micro...y/gg682006.aspx

Frequently Asked Questions for Configuration Manager - http://technet.micro...y/gg682088.aspx

 

 

Site Types

 

 

Configuration Manager 2012 introduces the central administration site and some changes to primary and secondary sites. The following tables summaries these sites and how they compare to sites in Configuration Manager 2007.

 

 

Central administration site

The central administration site coordinates intersite data replication across the hierarchy by using Configuration Manager database replication. It also enables the administration of hierarchy-wide configurations for client agents, discovery, and other operations. Use this site for all administration and reporting for the hierarchy. Although this is the site at the top of the hierarchy in Configuration Manager 2012, it has the following differences from a central site in Configuration Manager 2007:

• Does not process client data.
  
• Does not accept client assignments.
  
• Does not support all site system roles.
  
• Participates in database replication
  

Primary site

 

 

 

 

 

 

Manages clients in well-connected networks.

Primary sites in Configuration Manager 2012 have the following differences from primary sites in Configuration Manager 2007:

• Additional primary sites allow the hierarchy to support more clients.
  
• Cannot be tiered below other primary sites.
  
• No longer used as a boundary for client agent settings or security.
  
• Participates in database replication.
  

Secondary site

 

 

 

 

 

 

Controls content distribution for clients in remote locations across links that have limited network bandwidth.

Secondary sites in Configuration Manager 2012 have the following differences from secondary sites in Configuration Manager 2007:

• SQL Server is required and SQL Server Express will be installed during site installation if required.
  
• A proxy management point and distribution point are automatically deployed during the site installation.
  
• Secondary sites can be tiered to support content distribution to remote locations.
  
• Participates in database replication.
  

 

 

 

 

 

 

 

Step 1. Create the Lab Environment

 

We are going to create a Standalone Primary Site in our LAB, so let's get started, and to start off with I re-used/recycled my lab from Beta 1 by applying the day 1 snapshots effectively giving me a blank AD and blank Vnext server Operating System ready for all setup and installation. This is a huge advantage of doing labs in a virtual environment.

 

The SCCM 2012 beta2 server for this lab has a C: partition (OS) and 150GB D: partition (DATA).

 

I chose to install Windows Server 2008 R2 standard as the server OS for vNext. Once done I joined it to my domain (2k8r2), verified DNS was working correctly via nslookup and was ready to begin the steps below.

 

 

Create AD users:

 

In addition I created some accounts in AD, namely:

 

* SMSadmin, a domain user,

* Testuser, a domain user,

* DomJoin, a domain user,(for joining to the domain)

* ReportsUser, a domain user for reporting services.

* ClientInstall, a domain user for installing the Vnext Client. This user will be a local administrator on computers you want to install the vNext Client.

* SCCMNAA, a domain user, (Network Access Account) used during OSD

 

 

 

Create Local Administrator accounts:

 

On the vNext server I added the vNext site server computer account (vnext$) as a member of the Local Administrators Group. In addition, add the SMSadmin user to the Local Administrators group.

 

 

 

Step 2. Download SCCM 2012 Beta 2

 

you can download it from Microsoft here.

 

System Requirements

 

* Supported Operating Systems:Windows Server 2008

 

Minimum System Requirements:

 

* Site servers and site roles require 64-bit OS (distribution points are an exception)

o Branch distribution points have been deprecated and replaced with standard distribution points that can be hosted on Configuration Manager 2012 client operating system platforms, with the exception of Windows XP Professional Service Pack 3 and Windows XP Tablet PC SP3

o Standard DPs can run on Windows Server 32-bit but will not support advanced functionality

* Windows Server 2008 (64-bit)

o Distribution points can run on Windows Server 2003

* SQL Server 2008 SP1 with CU10 (64-bit)

* SQL Reporting Services is ONLY reporting solution

 

 

Supported Configurations (link to: http://download.micr...F/Configuration Manager 2012 Beta 2 Supported Configuration.pdf)

 

Perform the following on the Active Directory Domain Controller as a Domain Administrator

 

 

Step 3. Create The System ManageMent Container

 

Open ADSI Edit, click on Action, Connect To and click Ok, Double Click on Default Naming Context and the DC= that appears below it. Click on the + and scroll down to CN=System.

 

Right Click on CN=System and choose New, Object

 

 

Choose Container from the options, click Next and enter System Management as the value. Click Next and Finish. Press F5 to refresh ADSI Edit and you should now see the new System Management Container. Close ADSI Edit.

 

Step 4. Delegate Permission to the System Management Container.

 

Open Active Directory Users and Computers. Click on view, select Advanced Features.

 

Select the System Management Container, and right click it, choose All Tasks and Delegate Control.

 

 

When the Welcome to Delegation of Control Wizard appears click next, then click Add. click on Object Types, select Computers. Type in your vNext server name and click on Check Names, it should resolve.

 

 

Click Ok, then Next. Choose Create a Custom Task to Delegate, click next, make sure This folder, existing objects in this folder and creation of new objects in this folder is selected.

 

 

click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific child objects are selected then place a check mark in FULL CONTROL, and click next then Finish.

 

 

Failure to do the above will mean that the System Management Container in AD will NOT POPULATE with vNext specific info and you will see many errors in your site status.

 

Step 5. Extend the Active Directory schema for Configuration Manager

 

Note:-

 

The Active Directory schema extensions for Configuration Manager 2012 are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for Configuration Manager 2012.

 

 

 

 

Perform the below on your Active Directory server, simply browse the network to your vnext server \\vnext\d$ and locate the folder where you uncompressed vNext Beta 2 and find \SMSSetup\Bin\x64\Extadsch.exe, right click and choose Run As Administrator.

 

A command prompt window will appear briefly as the schema is extended, check in c:\ for a log file called ExtADSch.log it should look similar to this

 

<05-08-2011 12:24:21> Modifying Active Directory Schema - with SMS extensions.

<05-08-2011 12:24:21> DS Root:CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local

<05-08-2011 12:24:21> Attribute cn=MS-SMS-Site-Code already exists.

<05-08-2011 12:24:21> Attribute cn=mS-SMS-Assignment-Site-Code already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-Site-Boundaries already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-Roaming-Boundaries already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-Default-MP already exists.

<05-08-2011 12:24:21> Attribute cn=mS-SMS-Device-Management-Point already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-MP-Name already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-MP-Address already exists.

<05-08-2011 12:24:21> Attribute cn=mS-SMS-Health-State already exists.

<05-08-2011 12:24:21> Attribute cn=mS-SMS-Source-Forest already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-Ranged-IP-Low already exists.

<05-08-2011 12:24:21> Attribute cn=MS-SMS-Ranged-IP-High already exists.

<05-08-2011 12:24:21> Attribute cn=mS-SMS-Version already exists.

<05-08-2011 12:24:21> Attribute cn=mS-SMS-Capabilities already exists.

<05-08-2011 12:24:22> Class cn=MS-SMS-Management-Point already exists.

<05-08-2011 12:24:22> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local

<05-08-2011 12:24:23> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local.

<05-08-2011 12:24:23> Class cn=MS-SMS-Server-Locator-Point already exists.

<05-08-2011 12:24:23> Located LDAP://cn=MS-SMS-Server-Locator-Point,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local

<05-08-2011 12:24:23> Successfully updated class CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local.

<05-08-2011 12:24:23> Class cn=MS-SMS-Site already exists.

<05-08-2011 12:24:24> Located LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local

<05-08-2011 12:24:24> Successfully updated class LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local.

<05-08-2011 12:24:24> Class cn=MS-SMS-Roaming-Boundary-Range already exists.

<05-08-2011 12:24:24> Located LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local

<05-08-2011 12:24:24> Successfully updated class LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=2k8r2,DC=lab,DC=local.

<05-08-2011 12:24:25> Successfully extended the Active Directory schema.

 

<05-08-2011 12:24:25> Please refer to the ConfigMgr documentation for instructions on the manual

<05-08-2011 12:24:25> configuration of access rights in active directory which may still

<05-08-2011 12:24:25> need to be performed. (Although the AD schema has now be extended,

<05-08-2011 12:24:25> AD must be configured to allow each ConfigMgr Site security rights to

 

Step 6. Open TCP port 1433 and 4022 for SQL replication.

 

If you are setting up a hierarchy (CAS/Primary/etc) then on your AD server do the following, start Group Policy Management tool and create a new GPO,

 

Select Computer Configuration, Policies, Windows Settings, Windows Firewall with Advanced Security and select Inbound Rules, choose New and follow the wizard for opening up TCP port 1433 as per this guide on Technet. Once done, repeat the above for Port 4022.

 

[anyweb]

Perform the following on the vNext server as SMSadmin

 

Step 7. Install .NET 3.5.1 and WCF Activation

 

In Server Manager select Features, Add Features, Select .NET Framework 3.5.1, also select WCF Activation and when prompted answer Add Required Role Services click next and next again, and verify the following IIS components are installed in addition to the ones preselected by the wizard.

 

 

Common HTTP Features

Static Content

Default Document

Directory Browsing

HTTP Errors

HTTP Redirection

 

 

Application Development

ASP.NET

.NET Extensibility

ASP

ISAPI Extensions

ISAPI Filters

 

Health and Diagnostics

HTTP logging

Logging tools

Request Monitor

Tracing

 

Security

Basic Authentication

Windows Authentication

URL Authorization

Request Filtering

IP and Domain Restrictions

 

Performance

Static Content Compression

 

Management Tools

IIS Management Console

IIS Management Scripts and Tools

Management Service

IIS 6 Management Compatibilty

IIS 6 Metabase Compatibility

IIS 6 WMI Compatibility

IIS 6 Scripting Tools

IIS 6 Management Console

 

 

and yes to any additional prompts, then Click Next and Install and close when done.

 

 

Step 8. Download and install .NET 4

 

Download .NET 4 from here (webinstall) or here (Standalone). Double click the file.

 

 

Accept the License terms and click Install

 

 

 

After a while it will complete, Click Finish when done

 

 

restart when prompted

 

Step 9. Add BITS and Remote Differential Compression

 

Finally, in Server Manager click on Add Features, place a selection mark in BITS and RDC.

 

[anyweb]

Step 10. Download Microsoft SQL Server 2008 and associated files

 

Note:- Do not use SQL 2008 R2 in beta 2 as it's not supported.

 

Download SQL Server 2008 Standard (x86, x64) - DVD (English) from your provider (MSDN or Technet) the one I used was

 

File Name: en_sql_server_2008_standard_x86_x64_dvd_x14-89155.iso

Date Published (UTC): 8/5/2008 10:20:32 PM Last Updated (UTC): 2/4/2009 12:22:20 PM

SHA1: F868EE641DE36222668A60345FAE57446F88B070 ISO/CRC: 31968C44

 

You can download the Trial version (180 days) from here.

 

While you are at it download SQL Server 2008 SP1 from here

 

File Name: en_sql_server_2008_sp1_x64.exe

Date Published (UTC): 4/9/2009 1:40:10 PM Last Updated (UTC): 9/25/2009 11:10:14 AM

SHA1: 1F811D5FFA8A6A4FEBB3BDD8C556F27C8D5D69D3 ISO/CRC: AE4E4D68

 

Update: Cumulative Update 14 (CU14) is now available and fixes some SQL issues with SCCM 2012 beta 2. You can download it here.

 

Select the following download- SQL Server 2008 All (Global) x64 sp1 SQLServer2008_SP1_CU14_2527187_10_00_2821_x64 2008 10.00.2821.00 264620376 5/9/2011 6:48:46 PM

 

 

 

 

Step 11. Install SQL Server 2008

 

To Install SQL server follow this guide but please install SQL on D:\Program Files... and when running setup.exe right click and choose Run as Administrator.

 

 

After you install SQL Server 2008, you must install SP1 and finally install CU14.

 

So install it in this order:

 

SQL Server 2008 >> SQL Server 2008 SP1 >> SQL Server 2008 Cumulative Update 14

[anyweb]

Step 12. Install Configuration Manager 2012 beta2.

 

 

TIP: you can open C:\ConfigMgrSetup.log with trace64.exe or notepad and review the contents of the file, it will inform you of any issues during installation.

 

 

Uncompress the EXE by running it, then browse to where you uncompressed it and click on Splash.hta

 

 

when the wizard appears, click on Install

 

select Install a Configuration Manager Primary Site Server and click next

 

 

Create a folder on C:\ called SCCM2012_Beta2_Updates and then specify the path to download the updates or point it to another path where you've already got the updates.

 

Tip:

 

If you don't have internet on your SCCM server then you can download the required updates on another computer by doing like so:-

• Open a command prompt with administrative permissions
  
• Navigate to .\Configuration Manager 2012 Install source\smssetup\bin\X64
  
• Run SetupDL.exe target dir (in my example SetupDL.exe D:\CM2012DL
  
• The total download size is 192 mb and the total number of files is 14 with SQL Express and .Net Framework 4.0 being the largest files.
  

Thanks to Kent for that tip.

 

 

 

click next, the installer will download the updates neeeded

 

 

when done downloading the updates you'll get prompted to fill in some info about the installation including site code, I chose to install to D:\..

 

 

Next we choose that Primary site will be installed as a stanadlone site

 

 

leave database server as it is

 

 

enter the SMS Provider location settings

 

 

as I don't have a PKI infrastructure in place i'll choose HTTP for now

 

 

for the site system roles select HTTP from the drop down choices for both management point and distribution point roles.

 

 

click next at the CEIP screen

 

 

review the summary

 

 

and click next to start the pre requisite check

 

we have two warnings, the WSUS SDK and Firewall, we'll deal with both later and they are only warnings so click next to continue.

 

 

WSUS warning:-Configuration Manager software update points require Windows Server Update Services (WSUS) version 3.0 SP1 or later. If using a remote software update point, the WSUS administration console must be installed on the site server. For more information on WSUS installation see http://go.microsoft..../?LinkID=79477.

 

Firewall warning:-Firewall is on and does not have exceptions enabled for sql server or port 1433 and 4022 to allow cross domain access. May have problem if central\primary\secondary sites are in different domains.

 

Note, if you completed Part 6 above and allowed the Group Policies to update then you won't get the Firewall warnings, I added that part after creating this guide so safe to ignore.

 

 

click Begin and make sure Trace64 is running in the background so that you can monitor the installation log

 

 

this does take some time to complete so now's a good time to go get that coffee

 

once the installation is complete, review the log for any errors and restart your vNext server.

 

After restarting the server, start the SCCM admin console and click on About.

 

 

Congratulations, you've installed System Center Configuration Manager 2012 Beta 2.

[Boedt]

Hello,

 

this is a great guide.

 

But however, i cant get it to work

 

it says in the log file: Could not check BITSEXTS enabled or not - ConnectServer failed, error = -2147217394

 

I Installed: IIS and BITS

 

Is there anything you can do wrong?

 

I dunno if i choose all the options u listed:

 

Common HTTP Features

Static Content

Default Document

Directory Browsing

HTTP Errors

HTTP Redirection

 

 

Application Development

ASP.NET

.NET Extensibility

ASP

ISAPI Extensions

ISAPI Filters

 

Health and Diagnostics

HTTP logging

Logging tools

Request Monitor

Tracing

 

Security

Basic Authentication

Windows Authentication

URL Authorization

Request Filtering

IP and Domain Restrictions

 

Performance

Static Content Compression

 

Management Tools

IIS Management Console

IIS Management Scripts and Tools

Management Service

IIS 6 Management Compatibilty

IIS 6 Metabase Compatibility

IIS 6 WMI Compatibility

IIS 6 Scripting Tools

IIS 6 Management Console

 

Is it possible to install them afterwards?

 

Thanks in advance

[Christoffer Lydahl]

Hello,

 

this is a great guide.

 

But however, i cant get it to work

 

it says in the log file: Could not check BITSEXTS enabled or not - ConnectServer failed, error = -2147217394

 

I Installed: IIS and BITS

 

Is there anything you can do wrong?

 

I dunno if i choose all the options u listed:

 

Common HTTP Features

Static Content

Default Document

Directory Browsing

HTTP Errors

HTTP Redirection

 

 

Application Development

ASP.NET

.NET Extensibility

ASP

ISAPI Extensions

ISAPI Filters

 

Health and Diagnostics

HTTP logging

Logging tools

Request Monitor

Tracing

 

Security

Basic Authentication

Windows Authentication

URL Authorization

Request Filtering

IP and Domain Restrictions

 

Performance

Static Content Compression

 

Management Tools

IIS Management Console

IIS Management Scripts and Tools

Management Service

IIS 6 Management Compatibilty

IIS 6 Metabase Compatibility

IIS 6 WMI Compatibility

IIS 6 Scripting Tools

IIS 6 Management Console

 

Is it possible to install them afterwards?

 

Thanks in advance

 

Try installing WebDAV

[Peter van der Woude]

WebDAV is not needed anymore with ConfigMgr 2012

[Boedt]

well it seems like the installer cant find a connection to BITS, like its not enabled or the service is not started, but it is.. hm

[anyweb]

did you install the BITS feature ? did you try rebooting the server ? where are you getting the failure exactly ?

[Boedt]

I Installed the BITS Feature, the BITS Service is running, i restarted the Server

 

The error is showing in the Log Files, and i am getting it at the prerequest check, says BITS not installed BITS not enabled