Stephan Wibier

Create Cloud Distribution Point on Windows Azure with SCCM 2012 SP1 (Part 1) 2

Feb

1

2013

Tweet Cloud, everybody is talking about that. And with the new ConfigMgr 2012 SP1 fully integrating with Windows Azure it’s time to see how this works. You need to have some things in place first, so here we go: A Windows Azure subscription (duh) A working PKI Infrastructure 2 (a .cer and a .pfx) certificates ...

System Center 2012 SP1 – Evaluation VHDs

Feb

1

2013

Tweet Want to test, play or evaluate the new System Center 2012 SP1 products? Microsoft launched the public VHD’s for System Center 2012 SP1. The download consists of a single pre-configured VHD file for the System Center 2012 SP1 product. These downloads are free for everyone who wants to see what the new System Center ...

Hide Management Pack (MP) from Operations Manager Console – SCOM 2012

Jan

31

2013

Tweet So you got Operations Manager 2012 installed. The console looks fine and you can select which Management Packs (MP) you want to see and which ones you don’t. Every admin who logs in to the console will have to do this and this is fine for sealed MP’s. But what about your own, unsealed, ...

Operations Manager 2012 (SCOM) Activation 10

Jan

31

2013

Tweet When you install Operations Manager 2012 (SP1) you may notice is that there is no request for a product key when you install Operations Manager 2012. Once the install is complete and you open up the console the following is displayed: When you click Help à About à will show that you are running ...

Domain-Join Account for SCCM and MDT 8

Jan

30

2013

Tweet When working with deployment tools you need to have an account which can add Computers to a certain Organizational Unit (OU) in Active Directory. As we all know: do NOT use a ‘Domain Admin’ account for this purpose. The account used for adding computers to Active Directory will appear unencrypted in the unattend.xml! So ...

SCCM 2012 SP1 and SQL Server 4

Jan

30

2013

Tweet Here is an overview of the SQL Server configurations and requirements for supported SQL Server installations for ConfigMgr 2012. Source: http://technet.microsoft.com/en-us/library/gg682077.aspx Configurations for the SQL Server Site Database Each System Center 2012 Configuration Manager site database can be installed on either the default instance or a named instance of a SQL Server installation. The SQL Server instance can ...

SCCM 2012 SP1 Upgrade Checklist

Jan

29

2013

Tweet This information was taken from Microsoft and could come in handy: http://technet.microsoft.com/en-us/library/jj822981.aspx Use the information in the following check list to help you identify and plan for pre-upgrade configurations and additional actions that are related to upgrading your sites and hierarchy to Configuration Manager SP1. Step More Information Ensure that your computing environment meets the ...

SCCM 2012 SP1 Site Backup and Afterbackup.bat 2

Jan

29

2013

Tweet It’s always better and a preventive thought to Back-up your Daily SCCM 2012 Backup, (keeping a daily copy on the server and copying the backups to an alternate location). Because if your SCCM server falls down you still have a back-up! In the process of SCCM’s daily backup (visible in smsbkup.log), there’s an ‘AfterBackup.bat‘ file used to perform post-backup ...

SCCM 2012 SP1 binaries released for re-download

Jan

26

2013

Tweet There were some flaws in the initial download files for Config Manager 2012 SP1. Microsoft has released the new binaries according to Steve TH – MSFT. The binaries for System Center Configuration Manager 2012 and System Center Endpoint Protection 2012 have been updated to correct some minor issues. The binaries have been updated at the Download Center, ...

SCCM 2012 SP1 Client push fails with Authenticode Signature error

Jan

13

2013

Tweet There is a problem with Client Push installation in Microsoft System Center Configuration Manager 2012 SP1. One of the prerequisites, MicrosoftPolicyPlatformSetup.msi, which comes during the ccmsetup installation is digitally signed and the signature expired on 10-01-2012. Therefore Client Installation cannot be performed! Following error will appear in the ccmsetup.log: c:\windows\ccmsetup\logs\ccmsetup.log: Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode ...