Configuration Manager 2012 Detection Methods

Another day, another new ConfigMgr feature. Today I’ve been playing around with Detection Methods. This is a great new feature which gets us out of a variety of app deployment problem scenarios we have currently. In brief, consider the following scenario:

I wish to deploy a new application “Tobermory” to my clients. Tobermory depends on dotnet 3.5 and another application “Bulgaria”. These apps may already be installed on my machines, the installation may have been carried out manually or via Configuration Manager. Under the current Configuration Manager release we can set a program to depend on the installation of another program thus:

image
A totally flawed flowchart.

The problem with this stems from ConfigMgr’s ability to determine if the required application is already installed. Essentially it has no skills unless the app was installed by ConfigMgr in the first instance.

So, how does ConfigMgr 2012 improve this? With Detection Methods of course! Detection Methods enable a system to determine whether or not an application is already present on the system (think WSUS IsInstalled type functionality). The method for identifying if an app is installed (in Beta 1) covers MSI interrogation and script based detection. I’m hoping that Beta 2 will allow for basic registry and file scanning.

So, as you can doubtless see, this is a major improvement over the current detection mentod outlined above.

As a brief aside, once we have a detection method defined we can “upgrade” these to “Global Conditions” which we can then re-use for any deployments. Out of the box we get a few (if you’re familiar with Group Policy Preferences you may recognise some of this):

•Machine AD Site

•CPU speed

•Mobile device type

•Free disk space

•Total Physical Memory

•Mobile input type

•Machine AD Organizational Unit

•Number of processors

•Machine Operating System and Architecture

•Machine Operating System Language

•Screen resolution

•ConfigMgr Assigned Site

These conditions can be leveraged for all deployment jobs allowing us as administrators to exploit these out of the box properties and define our own as we see fit.

About these ads

1 comment so far

  1. [...] Creating App-V Deployments in ConfigMgr 2012 VIDEO: Creating Deployment Types in ConfigMgr 2012 ConfigMgr 2012 Detection Methods About User Device [...]


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: