The Quick and Cheap Steps to Perform a Lab Installation of Configuration Manager 2007 Beta 2


The below instructions assume that you have two machines (virtual or physical).  One of the machines will act as the domain controller and SCCM client.  HW requirements for the domain controller should meet or exceed the following criteria:

-          P-III @ 1Ghz or better

-          256 MB RAM or better

-          Adequate free disk space (SMS client will take around 10-25MB when installed and collecting inventory information.  You also may want additional free space if you plan to  test out security patch or software deployment to this server)

The other machines will act as the SCCM site server.  HW requirements for this server should meet or exceed the following criteria:

-          P-III @ 2 Ghz or better (HT/Dual Core/multi-proc even better!)

-          4GB RAM or better (yes, I said 4GB - Combination of beta code and running everything on one box will use every bit of this!)

-          30GB of contiguous free disk space (especially if you will be doing OS captures and deployments)

It is assumed that both machines are on a standard routed IP network with no filters or firewalls separating the two machines.  The network itself can be ‘real’ or ‘virtual’ as long as the servers themselves recognize it.  Internet access for at least the machine that is to be the SCCM site server is highly recommended as the Software Update component is much easier to deploy with Internet access.

Before getting started with the below instructions, both of these machines should be running Windows Server 2003 w/SP1 either Standard or Enterprise with the latest patches installed. 

Finally, all steps below assume that you utilize the default Administrator account within the domain that has complete administrative access to the entire forest.

Pre-Install Tasks:

-          Run DCPROMO on one of the servers to create an AD Forest.  You can name the domain anything you like but we will refer to the domain name as ‘SCCMDOM.LOCAL’ and the domain controller as ‘SCCMDC’.

-          Join the other Windows Server to the newly created Domain.  This server will be your SCCM Primary Site Server.  We will refer to this server in this document as ‘SCCMServer’.

-          Create the following user accounts in the SCCMDOM.LOCAL domain using ADU&C

·       zSCCMClientInstall

§  Add this user to the Domain Admins Group

·       zSCCMSoftInstall

§  Add this user to the Domains Admins Group

-           In the SCCMDOM.LOCAL domain, modify the permissions on the ‘System’ Container using ADU&C:

·       Open the ADU&C on SCCMDC.

·       You may need to Select View => Advanced Features in order to make the ‘System’ container visible within ADU&C

·       Right-Click the System Container and choose Properties

·       Click the Security tab

·       Click Add… to add a new object

·       Click Object Types… and check ‘Computers’ and click OK

·       Type ‘SCCMServer$’ and click Check Names and click OK

·       With the SCCMServer account highlighted, check the ‘Allow’ checkbox for ‘Full Control’

·       Click the Advanced button

·       Select the SCCMServer account and click the ‘Edit…’ button

·       Select ‘This object and all child objects’ in the ‘Apply onto:’ dialog box and click OK

·       Click OK two more times to confirm the changes

-          On SCCMServer, add the following Windows components by going to Control Panel => Add/Remove Programs => Add/Remove Windows Components:

·       Add ASP.NET under the Application Server Component – this will automatically add some dependent components which are also needed

·       Add ‘Background Intelligent Transfer Service (BITS) Server Extensions’ under the Application Server => Internet Information Services (IIS) sub-component

·       Click OK and Next to Install the components that have been added – note that you may need to tell the wizard where to find your W03 i386 bits.

-          On SCCMServer, set the WebDAV extensions to ‘Allow’:

·       Open the IIS Manager MMC

·       In the Web Services Extension folder, highlight WebDav and click the Allow button

·       Close the IIS Manager MMC

-          Download all of the installation code from

·       SCCM Beta 2 Registration and Download Site:

·       SQL 2005 Eval:

·       SQL 2005 SP2: 

·       WSUS 3.0:

Installation Tasks:

-          Install SQL 2005 Evaluation Edition on SCCMServer (~10 – 20 minutes)

·       Run Setup.exe from the Servers folder on the SQL 2005 Evaluation DVD that you downloaded

·       Check to Accept the EULA and click Next

·       Click Install to install the .NET Framework, SQL Client, and Support Files

·       Click Next when complete

·       Click Next Again

·       Confirm that the Configuration Checks have all Passed and click Next

·       Enter Name and Company Information and click Next

·       On the Components screen check only ‘SQL Server Database Services’

·       Optional:  Add Management Tools:

§  Click The Advanced button

§  Under the Client Components feature Select Install for the Management Tools component and click Next

·       Leave the default of ‘Default Instance’ and click Next

·       On the Service Account page, select ‘Use the built-in System account’ and choose ‘Local system in the dialog and click Next

·       Choose Windows Authentication Mode and click Next

·       Accept the default SQL collation and click Next

·       Optionally select to send error reports or feature usage to MSFT (this is NOT required) and click Next

·       Review your choices and click Install

·       SQL 2005 will now install.  Click Next then Finish when prompted

·       Apply SQL 2005 SP1 or SP2. 

·       Run Windows Updates to apply any remaining Windows or SQL security updates


-          Install SCCM 2007 Beta 2  (~10-15 minutes)

·       Run extadsch.exe from SCCM 2007 Beta 2 source to extend the AD schema

§  Check c:\extadsch.log to verify schema extension success.

·       Install WSUS 3.0

§  Place WSUS DB on SQL 2005 instance…

§  Other default values are fine…

§  Don’t configure – we will do this later in ConfigMgr…

·       Install all Required ConfigMgr Hotfixes (these can be found in the ‘Prereqs’ folder within the SCCM 2007 Beta 2 Source):

§  913538

§  932303

§  925335 (only need fix for SQL, SupportTools, and SQLTools)

§  897667

§  Reboot after all hotfixes installed

·       Install ConfigMgr 2007 Beta 2

§  Custom Install

§  Select Primary Site

§  Select Mixed Mode Security


-          Configure SCCM 2007 Beta 2

·       Enable AD publishing (Advanced Tab in Site properties…)

·       Configure at least one site boundary

§  Recommend using the default AD site boundary for testing

·       Configure the Client Push Account you created above

·       Configure the Advanced Client Network Access Account you created above

·       Configure the Site System Roles

§  Enable BITS for the DP

§  Add these roles to the Server:

·       State Migration Point

·       Reporting Point

·       Software Update Point

o   Choose Defaults for now (Sync with MU, Default Update categories and products, etc.)

o   Be sure to remove all languages but English!!!

·       Configure Client Agents

§  Most default settings are fine – may want to configure:

·       Set the Adv. Client Network Access Account in Computer Client Agent Settings

·       Set Remote Tools for XP or later to ‘Full Control’ and change Notification to NOT “play a sound repeatedly”

·       Set and manage Remote Assistance settings and set to Full Control

·       Configure Discovery Methods

§  Set System Discovery at minimum for the AD Forest

§  Push Client to the site server – confirm success

§  Push Client to all available clients in the lab


-          You are done!  You should now have one SCCM Primary Site Server and one SCCM client ready to rock and roll!

Comments (2)

  1. Anonymous says:

    The Quick and Cheap Steps to Perform a Lab Installation of Configuration Manager 2007 Beta 2 Pre-Requisites

  2. Anonymous says:

    So, wow, you would have thought I had fallen off the planet since apparently I have not blogged in like

Skip to main content