Attention: Downloads of SCCM 2012 SP1 done after 29. of January 2013 do not need this hotfix, it is already included in the source!
The Hotfix KB2801987 is available (http://support.microsoft.com/kb/2801987/en-us) and solves the problem with the client installation on SCCM 2012 SP1 – see article here!
Starting today, it’s not possible to install the SCCM 2012 SP1 Agent! So it’s also not possible anymore to deploy an Operating System!
The problem is the MSI named “MicrosoftPolicyPlatformSetup.msi” in the %InstallDir%\Client\x64 or x86! The file is signed with a certificate, which was valid until yesterday, 10th of January 2013! And the Agent installation checks this certificate…
The error is: Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101 ccmsetup
SCCM 2012 without SP1 (Cum Upd 1): The certificate will be available until the 1st of February 2013.
We will blog and twitter when the MS Patch is available…
Kind regards
Chris
Do you use the SoftwareShop (WebBased) integrated in SCCM 2012 RTM? If yes, take a look here before upgrading to SCCM 2012 SP1…
The Softwareshop in SCCM 2012 SP1 needs Silverlight 5.1.x to connect! If you have installed an older Version on the clients, they cannot connect anymore to the shop after an upgrade to SCCM 2012 SP1! The easiest way to solve it: Deploy the new sccm agent to the clients, this will install all prerequisites automatically – including Silverlight 5.1.10411.0!
You have several possibilities to deploy the agent: http://technet.microsoft.com/en-us/library/gg712298.aspx. My favorite is by “Automatically Upgrade the Configuration Manager Client for the Hierarchy” or “How to Upgrade Configuration Manager Clients by Using a Package and Program”.
That’s it!
Regards
Chris
I’ve upgraded the SCCM 2012 RTM installation to 2012 SP1 for a customer. After the successful upgrade, I started the console and was scared about the message –> no database connection!
After installing the new console on the server it was o.k… 
!
Don’t forget to install it… and create a new package for the console deployment!
Kind regards
Chris
Just saw a new feature in the SCCM 2012 SP1 Softwarecenter on a Client.
You can install multiple applications in ONE STEP and the icons, which you can see also in the SoftwareShop, are also available! Take a look on the screenshot (Verfügbare Software meens “Available Software”). But in the SoftwareShop (WebBased) it’s still not possible…
Regards
Chris
We received a lot of questions about “will SCCM 2007 support Windows 8 and Windows Server 2012?”. Here is the answer including WHAT is supported…
There is a Hotfix available for SCCM 2007 SP2 to support Windows 8 and Windows Server 2012 –> KB2750782.
The Hotfix will give the possibility to MANAGE Win8 and 2012 Operating Systems.
The Hotfix will NOT provide OSD (Operating System Deployment) functions. You can deploy Windows 8 and Server 2012 without any MS Support and without new features (like BitLocker PreProvisioning –> see here Bitlocker Features in SCCM 2012 SP1 Beta)!
If you need also features like APP-V 5, Cloud Distribution Point, Mobile Device Management for iPhone, Android, Windows Phone… you have to upgrade to SCCM 2012 SP1 (release should be in January 2013)!
Kind regards
Chris
There are a few new Bitlocker features for the OS Deployment in SCCM 2012 SP1 Beta related to Windows 8.
In Windows 7, the encryption ot a volume takes several hours. Working in this time is lazy… With WinPE 3.0 it’s possible to activate Bitlocker BEFORE intalling the operating system –> it’s named “pre-provisioning”.
Cumulative Settings are now possible!
In the SCCM 2012 RTM Version it was possible to create different SCEP Policies (Antimalware Policies). Unfortunately, if a client receives more than one of this policies, only the one with the higher priority (1, 2, 3, …) is applied.
In SP1 Beta it’s now cumulative!
Do you like to upgrade your LAB from SCCM 2012 RTM to SP1 Beta? Take a look in this blog to not forget the prerequisites…
Prerequisites
If all the prerequisites are achieved, go ahead with the upgrade installation.
I often had the problem, that deployed computers haven’t the right computername. Unfortunately they were named like „MININT-48ABCDE“…
Because actually we cannot install a pxe server, we’re installing the clients by USB or CD-ROM. For that, I have to create a Boot Media… so far so good…
In the SCCM Console, the wizard to create the boot medium will give you the possibility to create a „Dynamic Media“ or a „Site-based media“.
Choose “Site-based-media”, then you will not have the problem with the client name.
OR, if you need the “Dynamic media”, you have to add on the computer object in sccm the variable “osdcomputername” and as the value the needed computername…
cu
chris
