How to install the Configuration Manager client using Software Update Point based client installation

~ Bindusar Kushwaha

Hi everyone, Bindusar here again. Image may be NSFW.
Clik here to view.Are you planning to install the System Center 2012 Configuration Manager (ConfigMgr 2012) client using a Software Update Point but running into issues? Below are the things you may want to check.

- The computer should be joined to the domain.
- Group Policy should be working properly.
- The Software Update Point should be installed and working properly.
- Configuration Manager should be published in Active Directory (AD).
- The Windows Update agent on client machines should be working properly.
- Client Push installation should not be configured.

When installing the client using a Software Update Point, we need to make sure a few things are configured:

- Configure the WSUS server location using Group Policy so that client machines can get ccmsetup as an update patch.
- From the Configuration Manager console, client installation should be configured using the Software Update Point.

That’s it!

You can find more information on this in the following articles:

How to Install Configuration Manager Clients Using Software Update Point Based Installation: http://technet.microsoft.com/en-us/library/bb633194.aspx

Top 3 ConfigMgr 2012 Client Installation Methods: http://blogs.technet.com/b/smartinez/archive/2013/09/27/top-3-configmgr-2012-client-installation-methods.aspx

Putting it all together

Configure Group Policy to locate the WSUS server by configuring the policy item named “Specify intranet Microsoft Update service location” and provide the WSUS server name (e.g. http://WsusServerName>:Port).

Image may be NSFW.
Clik here to view.

Then just run Gpupdate /force on the client and make sure it’s getting that policy (this can be checked using RSOP.msc).

Image may be NSFW.
Clik here to view.

At this point the client computer is now ready to get all the updates needed from WSUS server location.

Now it’s time to configure Configuration Manager to distribute the Client Installer package.

Image may be NSFW.
Clik here to view.

NOTE The “Published version” will be blank if it was NOT configured (published) earlier.

In WCM.log we can see the following lines:

Attempting connection to WSUS server: BinPri1.Contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 5/28/2014 4:07:24 AM 4404 (0x1134)

Successfully connected to server: BinPri1.Contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 5/28/2014 4:07:24 AM 4404 (0x1134)

Found published client Configuration Manager Client (5.00.7958.1000) (id=8427071a-da80-48c3-97de-c9c528f73a2d, version=5.00.7958.1000) SMS_WSUS_CONFIGURATION_MANAGER 5/28/2014 4:07:24 AM 4404 (0x1134)

Successful published and approved package 8427071A-DA80-48C3-97DE-C9C528F73A2D for Install to All Computers, Deadline UTC time=5/26/2014 9:53:43 PM SMS_WSUS_CONFIGURATION_MANAGER 5/28/2014 4:07:24 AM 4404 (0x1134)

completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 5/28/2014 4:07:24 AM 4404 (0x1134)

Waiting for changes for 60 minutes SMS_WSUS_CONFIGURATION_MANAGER 5/28/2014 4:07:24 AM 4404 (0x1134)

As we can see, the update is not only published but it’s approved with a deadline automatically! Once we are able to see this line in WCM.log we are done from the server side.

Connect to SUSDB and you should be able to see the following now available:

If you are connecting to WSUS on Server 2008 R2 use \\.\pipe\mssql$microsoft##ssee\sql\query
If you are connecting to WSUS on Server 2012, use \\.\pipe\MICROSOFT##WID\tsql\query

Image may be NSFW.
Clik here to view.

Now we need to wait and watch on the client machine for it to start the update scan cycle. Alternatively, you can manually trigger it from Control Panel with the Check for Updates option.

2014-05-2703:40:01:788 936 438 Agent * Added update {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1 to search result

2014-05-2703:40:01:788 936 438 Agent * Found 1 updates and 72 categories in search; evaluated appl. rules of 265 out of 519 deployed entities

…

2014-05-2703:40:01:804 936 e78 AU >>## RESUMED ## AU: Search for updates [CallId = {A7DDCEFB-825C-4B67-949F-D92645D11D82}]

2014-05-2703:40:01:804 936 e78 AU # 1 updates detected

…

2014-05-2703:40:01:804 936 e78 AU Auto-approving update for download, updateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1, ForUx=0, IsOwnerUx=0, HasDeadline=1, IsMinor=0

2014-05-2703:40:01:804 936 e78 AU Auto-approved 1 update(s) for download (NOT for Ux)

2014-05-2703:40:01:804 936 e78 AU ## START ## AU: Download updates

2014-05-2703:40:01:804 936 e78 AU # Approved updates = 1

2014-05-2703:40:01:866 936 e78 AU AU initiated download, updateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1, callId = {9057EBE8-6221-4213-AA08-4EA1E0820662}

2014-05-2703:40:01:866 936 e78 AU Setting AU scheduled install time to 2014-05-27 21:30:00

2014-05-2703:40:01:866 936 e78 AU AU setting pending client directive to 'Download Progress'

2014-05-2703:40:01:866 936 e78 AU # Pending download calls = 1

2014-05-2703:40:01:866 936 e78 AU <<## SUBMITTED ## AU: Download updates

…

2014-05-2703:40:01:991 936 438 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]

2014-05-2703:40:01:991 936 438 DnldMgr * Call ID = {9057EBE8-6221-4213-AA08-4EA1E0820662}

2014-05-2703:40:01:991 936 438 DnldMgr * Priority = 3, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}

2014-05-2703:40:01:991 936 438 DnldMgr * Updates to download = 1

2014-05-2703:40:01:991 936 438 Agent * Title = Configuration Manager Client (5.00.7958.1000)

2014-05-2703:40:01:991 936 438 Agent * UpdateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1

2014-05-2703:40:02:038 936 438 DnldMgr *********** DnldMgr: New download job [UpdateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1] ***********

2014-05-2703:40:02:585 936 438 DnldMgr * BITS job initialized, JobId = {06E96DA6-6051-4A9D-B2EE-F58462B647F1}

2014-05-2703:40:02:741 936 438 DnldMgr * Downloading from http://binpri1:8530/Content/E4/28F170F0C414D9474A43A4CAEB2577F2F8C86CE4.cab to C:\Windows\SoftwareDistribution\Download\222661f20b633750ff74f33b134f79d9\28f170f0c414d9474a43a4caeb2577f2f8c86ce4 (full file).

2014-05-2703:40:02:913 936 e78 AU AU checked download status and it changed: Downloading is paused

2014-05-2703:40:02:975 936 e78 AU AU checked download status and it changed: Downloading is not paused

2014-05-2703:40:02:975 936 e78 AU AU setting pending client directive to 'Download Progress'

2014-05-2703:40:03:288 936 7f8 DnldMgr BITS job {06E96DA6-6051-4A9D-B2EE-F58462B647F1} completed successfully

2014-05-2703:40:03:397 936 7f8 Misc Validating signature for C:\Windows\SoftwareDistribution\Download\222661f20b633750ff74f33b134f79d9\28f170f0c414d9474a43a4caeb2577f2f8c86ce4:

2014-05-2703:40:03:413 936 7f8 Misc Microsoft signed: Yes

2014-05-2703:40:03:429 936 7f8 DnldMgr Download job bytes total = 611893, bytes transferred = 611893

2014-05-2703:40:03:491 936 7f8 DnldMgr *********** DnldMgr: New download job [UpdateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1] ***********

2014-05-2703:40:03:491 936 7f8 DnldMgr * All files for update were already downloaded and are valid.

2014-05-2703:40:03:632 936 e78 AU >>## RESUMED ## AU: Download update [UpdateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}, succeeded]

2014-05-2703:40:03:632 936 e78 AU ## END ## AU: Download updates

…

2014-05-2703:40:03:632 936 e78 AU AU setting pending client directive to 'Install Approval'

2014-05-2703:40:03:647 936 b04 AU Forced install timer expired for deadline install

2014-05-2703:40:03:647 936 b04 AU UpdateDownloadProperties: 0 download(s) are still in progress.

2014-05-2703:40:03:647 936 b04 AU #############

2014-05-2703:40:03:647 936 b04 AU ## START ## AU: Install updates

2014-05-2703:40:03:647 936 b04 AU #########

2014-05-2703:40:03:647 936 b04 AU # Initiating deadline install

2014-05-2703:40:03:647 936 b04 AU # Approved updates = 1

2014-05-2703:40:03:647 936 b04 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {08F360A4-EBDB-4097-BE41-1FDC1C683F65}]

2014-05-2703:40:03:647 936 9f0 AU Getting featured update notifications. fIncludeDismissed = true

2014-05-2703:40:03:647 936 9f0 AU No featured updates available.

2014-05-2703:40:03:647 936 854 Agent *************

2014-05-2703:40:03:647 936 854 Agent ** START ** Agent: Installing updates [CallerId = AutomaticUpdates]

2014-05-2703:40:03:647 936 854 Agent *********

2014-05-2703:40:03:647 936 854 Agent * Updates to install = 1

2014-05-2703:40:03:663 936 854 Agent * Title = Configuration Manager Client (5.00.7958.1000)

2014-05-2703:40:03:663 936 854 Agent * UpdateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1

2014-05-2703:40:03:679 936 854 Agent WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point

2014-05-2703:40:03:725 936 9f0 AU Getting featured update notifications. fIncludeDismissed = true

2014-05-2703:40:03:725 936 9f0 AU No featured updates available.

2014-05-2703:40:18:241 936 854 DnldMgr Preparing update for install, updateId = {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1.

Now let’s take a look at CCMsetup.log on the client computer:

Launch from folder C:\Windows\SoftwareDistribution\Download\Install\ ccmsetup 6/2/2014 3:00:54 AM 3060 (0x0BF4)

CcmSetup version: 5.0.7958.1000 ccmsetup 6/2/2014 3:00:54 AM 3060 (0x0BF4)

Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 6/2/2014 3:01:01 AM 3060 (0x0BF4)

Ccmsetup command line: "C:\Windows\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 6/2/2014 3:01:02 AM 3060 (0x0BF4)

Local Machine is joined to an AD domain ccmsetup 6/2/2014 3:01:02 AM 3060 (0x0BF4)

Current AD forest name is Contoso.com, domain name is Contoso.com ccmsetup 6/2/2014 3:01:02 AM 3060 (0x0BF4)

Domain joined client is in Intranet ccmsetup 6/2/2014 3:01:02 AM 3060 (0x0BF4)

…

MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 6/2/2014 3:01:09 AM 3060 (0x0BF4)

MSI properties: SMSSITECODE="PR1" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 6/2/2014 3:01:09 AM 3060 (0x0BF4)

As we can clearly see, CCMSetup is not calling any additional parameters with it. This simply means that all of the default parameters will be passed. Site and MP information will be fetched from Active Directory.

Bindusar Kushwaha | Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Image may be NSFW.
Clik here to view.