After a nice summer break, enjoying the Lifestyle of Bern and Swimming in the river Aare (Here is a sample Picture of what happens here during summer http://v2.suedostschweiz.ch/var/upload/news/image/151730_640.jpg), I would like to write a small blog post about the superseding Feature in System Center 2012 Configuration Manager. Continue reading
With System Center 2012 Configuration Manager, we all know it, the new Application model was released. As long as you deploy MSI, the detection method, is very easy to define. But what, if you want to check a registry key, as needed with .Net installations? No Problem. What, if you want to check if the Installation was successfull with a VB-Script? It’s that easy (Look at this very good Blog Post about the Topic to deploy the App-V 5 Client: http://scug.be/sccm/category/detection-methods). And with a Powershell script? Uhm… Yes surprisingly, the block of scripts also applied to the detection method, and honestly, in my home environment, there is absolutely no doubt to decrease this behaviour below AllSigned, my home is my Castle 😉 I need to code-sign the script! Continue reading
In System Center Configuration Manager 2007, there was sometimes a challenge to find to correct Installation properties, most of the problem came with the patch files. But in 2012 we don’t have to install msp-files yet. But even then, a friend of mine considered a problem with the new apllication model in SCCM 2012. When you use apllications, and create deployments on collections, there isn’t an option to tell “Run from Distribution Point”, as it is still on Deployments of the 2007 style Packages. So if your SCCM Application Deployment Type which should run on the client, is larger than the default SCCM Client cache size of 5120MB, the download and installation will fail.
So I use for my client installation the following Installation properties (Client Push):
SMSSITECODE=H05 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=FQDN-MP FSP=FQDN-FSP Continue reading
In an environment with Hyper-V Servers, you will recognize, that System Center 2012 Configuration Manager doesn’t make a difference between the standalone Hyper-V Server R2 and a version like 2008 R2. So if you need to use a requirement Hyper-V Server Core, you have to create a Global Condition. In this Blog, I will show you how to achieve this. Click in the wunderbar on “Software Library” and open Application Management, right click on Global Condition and choose “Create Global Condition: