Monthly Archives: February 2012

Introducing System Center into an organization, a challenge…

This blogpost is more or less a small column based on some opinions I have based on numerous experiences in the past.

The System Center suite provides a set of tools that can make the lives of system administrators a lot easier. However, in order to use the set of tools in an organized way the organization needs company policies to use them properly. And here’s where the fun part starts.

In my opinion, the awareness that company policies are required is strongly present in System Center products. What fascinates me the most is that organizations, tend to overlook or forget the requirement to have company policies available. Of course, in most cases the requirement is not understood. Fortunately, it allows me to create this awareness and I can help them out.

To explain my thoughts let’s compare this with something in the real world. In the country that I live, The Netherlands, the government made laws for how we need to drive a car. We drive on the right side of the road, we have the steering wheel on the left and we have signs and traffic lights to organize traffic as much as possible. While some of the laws (we can consider them policies) are open for debate, the laws are there which will help drive in a correct manner.

If we would drive a car the way most organizations would introduce System Center, then everybody would drive the way they want with absolute chaos as a result. Everybody knows this is necessary in the real world, but forgets it in the world of IT.

Once the required policies are in place, then the challenge is to ‘translate’ these policies into a technological solution. I’ve built quite a number of Configuration Manager and a few Operations Manager environments myself The only way to achieve a working environment is to let the organization tell me what they want to and how they want to use it. Once they tell me what they want, I can get started to make the ‘translation’ in a System Center product.

Oh yes, having no policies at all is also a company policy, in that case a more pragmatic approach can be used…


SCCM 2007 OSD: Installing many software updates causes a machine to completely stop

Imagine yourself building a machine image or deploying one and you set up the Task Sequence to install Software Updates.

It is possible that a lot of Software Updates need to be installed.

What might happen is that the process stops completely and the Task Sequence is doing nothing anymore.

Microsoft published a hotfix which is available at

This is something to use at all times in my opinion so you don’t have to bother about the high number of updates…


CM2012 RC: application source path must be UNC all the time, but…

CM2012 likes UNC a bit more than local paths.

You must use UNC for applications all the time.

I wasn’t really aware of this feature before since I use UNC paths all the time at the predecessors of CM2012: CM2007 and SMS 2003.

Of course, the most elegant solution is to create a DFS Namespace for your application source.

And for other sources too…

Steve Thompson [MVP]

The automation specialist

Boudewijn Plomp

Cloud and related stuff...

Anything about IT

by Alex Verboon

Deployment Made Simple

Modern Workplace

Azure, Hybrid Identity & Enterprise Mobility + Security

Daan Weda

This site is all about System Center and PowerShell

IT And Management by Abheek

Microsoft certified Trainer -Abheek

Heading To The Clouds

by Marthijn van Rheenen