IT Consultant Everyday Notes

Just some problems/solutions storage

Tag Archives: SCCM Client

SCCM: Side-by-side migration issue with client reassignment

I was busy with an SCCM migration recently. A Customer wanted to get gradual side-by-side migration from an old SCCM 2012 R2 to a shiny SCCM CB.

The issue I faced was related to a Client re-assignment from the old to the new SCCM site.

As recommended I tried Jason Sandy’s script to reinstall the old client and configure the new one for the new site.

The Client was successfully installed, but kept connect to the old site.

I tried to re-register site assignment in WMI as described https://prajwaldesai.com/change-site-code-of-configuration-manager-client/ and restart CCMEXEC service.

In ClientLocation log I saw the new site was assigned, MP found, but after that the site immediately was re-assigned to an old one and the Client tried to connect back to the old site Sad smile

I tried  completely uninstall the client, use push etc.. without success.

Finally I noted

LSRefreshSiteCode: Group Policy Updated the assigned site code <old site code>, which is different than the existing assigned site code <new site code >. Will attempt re-assignment.

I checked GPOs and found a disabled GPO containing SCCM ADMX template with a site assignment.

The matter in fact once applied GPO tattoes its settings in the registry and they remains there even if GPO is not active anymore.

So I opened GPO template (located in ConfigMgr installation folder\Tools\ConfigMgrADMTemplates and founf the registry key in question is “hklm\SOFTWARE\Microsoft\SMS\Mobile Client”. Originally I planned to change only site code value there, but found Henrik’s article where he recommended to remove all values from the key all together.

Probably both approaches can work, so I created a simple cmd script and pushed it from the SCCM

REG delete “hklm\SOFTWARE\Microsoft\SMS\Mobile Client” /v GPRequestedSiteAssignmentCode /f
REG delete “hklm\SOFTWARE\Microsoft\SMS\Mobile Client” /v GPSiteAssignmentRetryDuration(Hour) /f
REG delete “hklm\SOFTWARE\Microsoft\SMS\Mobile Client” /v GPSiteAssignmentRetryInterval(Min) /f
cscript set-site-code.vbs

first three commands are cleaning settings hardcoded by GPO, the forth one force SCCM site code using a VBS script from here

After the script finished I restarted ccmexec and fount the client registered in the new site successfully.

Advertisements

SCCM: Install Client via startup script

Startup script for SCCM Client installation is updated: http://blog.configmgrftw.com/?page_id=349

SCCM 2012: Keep your SCCM database clean

Peter wrote a nice script to remove devices deleted from AD from SCCM database. That is what I always recommend to my clients too: keep your AD clean and use it as a primary inventory source.

SCCM 2012: SCCM 2012 SP1 Client update failed. Error: “Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

UPDATE: Microsoft published updated binaries for SCCM 2012 SP1 addressing this (and other minor) issues. You should use this new file set  for new installations. Links are here: http://blogs.technet.com/b/gladiatormsft/archive/2013/01/26/you-may-need-to-re-download-configuration-manager-2012-and-endpoint-protection-2012-sp1-binaries.aspx

 

I upgraded my Lab SCCM to 2012 and decided to try “Client autoupdate” feature introduced with SCCM 2012.

Unfortunately the attempt failed and I saw

Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

in ccmsetup.log on the Client.

Signing certificate for the msi looks like:

image

so it looks expired for me  Smile

Fortunately Microsoft published http://support.microsoft.com/kb/2801987  – Cumulative update 0 (CU0)  including an update (download)

I download the update and ran it on my SCCM

image

it did not pass from the first time, of course:

image

I should say the warning is a bit confusing – from the first sentence – Reboot is not required, from the second – I must restart the computer. Winking smile. Reboot the server and try again!

This time it looks better:

 

image

image

 

create packages:

image

and proceed with install:

image

Checking certificate again:

image

and the msi is validated successfully and the client is installed:

image

Do not forget to deploy the update to another Primary servers.

Anoop found some confusion between KB and the update wizard: http://anoopcnair.com/2013/01/14/configmgr-2012-sp1-kb-2801987-confusing-information-in-kb-article-vs-wizard/

I still think the updates is not necessary for CAS…

SCCM 2012: Automatic Client Upgrade

Just a reminder where the settings  Smile are located:

Go to Administration-Site- Configuration – Sites

Select your site and click Hierarchy Settings in ribbon

Select “Automatic Client Upgrade” tab in popup window:

 

image

SCCM: Client cannot get Policies automatically; site mode is “Unknown”

In some situations (list for SCCM 2007 is available in this article) you may found an SCCM client cannot get Policy from the server even though it is assign to the site and can see the server (site mode is displayed as “unknown” though on Client side).

Both SCCM 2007 and SCCM 2012 (RTM) is affected. The issue is promised to be fixed for SCCM 2012 with SP1 (available now).

The root cause is a Client Provisioning mode. To detect if the client is in this mode you can check:

32bit Windows OS
HKLM\SOFTWARE\Microsoft\CCM\CcmExec!ProvisioningMode

64bit client Windows OS
HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec!ProvisioningMode

Also, checking the Mobileclient.tcf file in the ccmsetup directory of a fully built machine shows SMSPROVISIONINGMODE=1 in the client install section – on a healthy client this should be
SMSPROVISIONINGMODE=0

A fixing script for SCCM 2012 is provided in that article

Linux and Unix Clients for SCCM 2012 SP1

The following UNIX and Linux versions are supported in the Beta release.

  • AIX Version 7.1 (Power)
  • AIX Version 6.1 (Power)
  • AIX Version 5.3 (Power)
  • HP-UX Version 11iv3 (IA64 & PA-RISC)
  • HP-UX Version 11iv2 (IA64 & PA-RISC)
  • RHEL Version 6 (x86 & x64)
  • RHEL Version 5 (x86 & x64)
  • RHEL Version 4 (x86 & x64)
  • Solaris Version 10 (x86 & SPARC)
  • Solaris Version 9 (SPARC)
  • SLES Version 11 (x86 & x64)
  • SLES Version 10 SP1 (x86 & x64)
  • SLES Version 9 (x86)

The Clients can be downloaded from here

This blog post describes how to install them.