IT Consultant Everyday Notes

Just some problems/solutions storage

Tag Archives: SCCM 2012 SP1

SCCM 2012: OSD Windows 7. How to get OS installed on drive C:

With SP1 Microsoft decided to stop using setup.exe for Windows 7 Install and Capture Task Sequence. As well known blind installation from install.wim file from W7 media results OS installed on drive D:.

To get OS installed directly from install.wim to drive C: Microsoft introduced a new variable OSDPreserveDriveLetter   this variable need to be set to FALSE before Apply OS step in the TAsk Sequence. Any partitions before one you use for the image deployment must be set with NO Letter.

 

more details can be found here: http://scug.be/sccm/2013/01/13/configmgr-sp1-windows-7-deployment-is-not-supported-anymore-from-the-setup-exe/

Advertisements

SCCM 2012: Boot images not updated after upgrading to SP1 in System Center 2012 Configuration Manager

In my upgrade I did not see this issue, but it looks like some people have it. To resolve it:

  • Rename the boot.wim and the default boot wims in each architecture folder of the <smsinstall>OSD\boot\ folder – both the i386 and x64 to <wim>.bak
  • Starting with the i386 folder first…Find the install folder of the ADK, which should be here if you installed with the defaults: “C:\Program Files (x86)\Windows
    Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim”. You will need to copy the winpe.wim to the <smsinstall>OSD\boot\i386 folder. Rename it to boot.wim.
  • You will also need to copy it again, but this time rename it so it matches the name of the default boot wim for the site – so it should look like boot.<packageid>.wim
  • Update default boot image. Click “Execute Method” -> input object path as SMS_BootImagePackage.PackageID=”<Image ID you see in the Console e.g. POL00001>” -> UpdateDefaultImage
  • You will need to do this for the x64 folder as well. Do not do this for any custom boot images – this is just to update the default boot wims installed during setup of the site.

as described in Clifton Hughes blog

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…