using SCCM 2012 RC in a LAB – Part 4. Configuring Client Settings and adding roles

In Part 1
of this series we got our AD and SCCM servers ready, and then we
installed System Center 2012 Configuration Manager as a standalone
Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles
necessary for the following Configuration Manager 2012 functionality,
Software Update Point (SUP) and Operating System Deployment. In Part 3
we configured the server further by Enabling some Discovery methods and
creating Boundary’s and Boundary Groups. Now we are ready to configure
Client Settings, Add roles and Distribute the Configmgr Client to our

Step 1. Add the Application Catalog Web Site Roles

Perform the following on the SCCM server as SMSadmin

In Administration, click on Servers and Site System Roles and right click on our Site Server, choose Add Site System Roles.

Attached Image: monthly_10_2011/post-1-0-77695600-1319905956.png

click next at the wizard general screen

Attached Image: monthly_10_2011/post-1-0-03966600-1319906050.png

Select both of the Application Catalog roles

Attached Image: monthly_10_2011/post-1-0-91851100-1319906151.png

confirm your Application Catalog Web service point selections

Attached Image: monthly_10_2011/post-1-0-02278300-1319907308.png

and the Application Catalog Website Point settings

Attached Image: monthly_10_2011/post-1-0-36249400-1319907402.png

enter your Organisation name and pick a Color scheme for the Application Catalog ! (New since Beta 2) !

Attached Image: monthly_10_2011/post-1-0-51614500-1319907770.png

click next through the summary and progress screens, verify everything at the completion screen.

Attached Image: monthly_10_2011/post-1-0-34265800-1319907958.png

Step 2. Configure Client Agent Settings

Perform the following on the SCCM server as SMSadmin

In the Administration section click on Client Settings in the left pane, and select the Default Client Settings listed, right click choose Properties

Attached Image: monthly_10_2011/post-1-0-97103900-1319899923.png

Click on Client Policy and we’ll set this
to every 15 minutes as it’s a LAB (the Default setting is 60 minutes),
this means that once every 15 minutes the Client will contact it’s
Management Point for any new policy.

Attached Image: monthly_10_2011/post-1-0-99185500-1319903630.png

now choose Computer Agent and configure it as follows:-

Click on Set Website for Default Application Catalog Website and set it to select the FQDN one that is listed

Attached Image: monthly_10_2011/post-1-0-92430200-1319908364.png

Set Add default Application Catalog website to Internet Explorer trusted zone to True

Set the Organization Name Displayed in Software Center to My Organization (change that to suit your organization)

so your Computer Agent settings should look like this

Attached Image: monthly_10_2011/post-1-0-75527300-1319908637.png

Set Software updates schedule from 7 days to 1 day

Attached Image: monthly_10_2011/post-1-0-97948200-1319909001.png

Select User and Device Affinity and change Allow users to define their primary device to True.

Attached Image: monthly_10_2011/post-1-0-97563800-1319908886.png

click Ok to save the Client Agent Settings.

Step 3. Deploying the Client Agent

Perform the following on the SCCM server as SMSadmin

Now that we have made changes to the Default Client settings,
we want to deploy the ConfigMgr Client to our computers in the LAB.
Before doing so we need to decide what method is appropriate for
installing the client on our computers.

The following methods are available

Client Installation Method Description

  • Client
    push installation – Automatically installs the client to assigned
    resources and manually installs the client to resources that are not
  • Software update point installation – Installs the client by using the Configuration Manager 2012 software updates feature.
  • Group Policy installation – Installs the client by using Windows Group Policy.
  • Logon script installation – Installs the client by using a logon script.
  • Manual installation – Manually installs the client software.
  • Upgrade
    installation – Upgrades clients to a newer version by using
    Configuration Manager 2012 application management. You can also use
    Configuration Manager 2007 software distribution to upgrade clients to
    Configuration Manager 2012.
  • Client Imaging – Prestages the client installation in an operating system image.

Please refer to Technet to Determine the Client Installation Method to Use in Configuration Manager 2012.

For the purposes of this LAB we will select Client Push Installation.

Note: we will use the
ClientInstall account to install the configmgr client on our computers,
make sure that this account is a local administrator on your target

In Administration, click on Site Configuration, Sites, select our site, in the ribbon above click on Settings, it will open a new menu, from that menu select Client Installation Settings and from there select Client Push Installation.

Attached Image: monthly_10_2011/post-1-0-05279800-1319909690.png

On the general screen, place a checkmark in Enable Automatic site-wide client push installation

Attached Image: monthly_10_2011/post-1-0-17523800-1319910441.png

Click on the Accounts tab, and select the yellow star, choose New Account

Attached Image: monthly_10_2011/post-1-0-46727000-1319911136.png

type in (or browse to select the AD user) the Client Push account, use our ClientInstall account which we created in Active Directory in Part 1.

Attached Image: monthly_10_2011/post-1-0-64444400-1319911346.png

Note the Verify button, this is new since
Beta 2 and allows you to verify that the credentials can connect to your
network resources, if you get your password wrong it will tell you !

Click on Verify and type in a Unc path to check.

Attached Image: monthly_10_2011/post-1-0-86923700-1319912793.png

Click Ok.

Click on Assets and Compliance and expand Devices, All Systems, you should see that our SCCM server has a client installed but our Domain Controller does not. Right click on the Domain Controller and choose Install Client.

Attached Image: monthly_10_2011/post-1-0-15855400-1319913609.png

set the Installation Options

Attached Image: monthly_10_2011/post-1-0-08983200-1319913721.png

click next through the wizard, close. Meanwhile, on the DC (AD1-Domain Controller) check task manager, and you’ll see ccmsetup starting…success

Attached Image: monthly_10_2011/post-1-0-70262000-1319913861.png

after some minutes the client is installed and you can refresh the view,
you’ll notice is says Client=Yes on both our systems in the Lab and
there are new tabs to look at since beta 2 on the bottom of the screen.
We’ll get to them in a later post.

Attached Image: monthly_10_2011/post-1-0-15614400-1319914518.png

On your AD computer you can start Software Center

Attached Image: monthly_10_2011/post-1-0-07906700-1319917406.png

click on Find applications from the application catalog

Attached Image: monthly_10_2011/post-1-0-02125300-1319917349.png

and your Application Catalog will pop up in Green !

Attached Image: monthly_10_2011/post-1-0-37178400-1319917474.png

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.