You are browsing the archive for 2011 August.

Why upgrade to Windows 7?

7:38 am in Uncategorized by nsienaert


Hi there!

I would like to start the discussion.

I see a lot of customers still running Windows XP and finally the most of them are thinking to migrate to Windows 7. But is it still worth?

Here are my thoughts…

  • Support of XP is guaranteed till 2014, following my XP Gadget I have installed Knipogende emoticon still 965 days as we speak.
  • Windows 8 is expected somewhere in 2012.
  • Microsoft guarantees in their first Team Blog that each software and hardware that works with Windows 7, will work with Windows 8.

In theory a company can start today with its AppCompat Envisioning and Remediation on Windows 7 to make sure the all Applications are working properly with Windows 7 (and 8).

So once Windows 8 is out they can migrate right away.

Three constraints so far:

  • The customer is willing to be an Early Adopter.
  • A Management Tool needs to be available to administer and deploy Windows 8. (I expect SCCM 2012 will support Windows 8)
  • A tool supports the migration of user data from XP to Windows 8 (USMT?)

What are your thoughts?

Nico Sienaert



SCCM 2012 SDK Overview (CEP)

5:00 pm in Uncategorized by nsienaert


Hi there!

Today there was a CEP session about the new SDK that will be released with SCCM 2012.

A high-level overview…

Release plan:

As from MMS2011 the SDK was available for a selected audience.

The future plans are a release together with CM 2012 RTM. This version will have details of all modified classes on board.

6 months after RTM a new release will explain the new classes and will have more “How To” guides included.

SDK Architecture:


There will be a possibility to create multiple instances on the SMS Provider

1. Admin Console SDK, it will be possible to

  • Program Right Click options
  • Launch executables
  • ShowDialog
  • Group – create submenu
  • Actions can be associated with icons
  • Create Forms
  • Create Wizards
  • Create Navigation Nodes
  • Create Views
  • Create Folders (add folders beneath nodes)


  • !!report is deprecated!!



  • Programmatic access to Management Point
  • Primary used to provide a MP proxy enabling control of non-standard clients


3. SMS Provider:

  • Application automation for UI activity
  • Actions through WMI classes, properties and methods
  • 60% of the entire SDK
  • Support of all actions through SMS Admin Console

Scenarios that are not supported:

  • modify or remove core Microsoft provided
  • configmgr console elements and behaviour
  • make changes to the root console XML
  • adding new wunderbars
  • new top level nodes
  • new tabs in the ribbon



Support Areas:


New SDK Areas:


A Porting Guide will be available explaining which functions are changed compared with CM2012:


Powershell Support:

cmdlets designed around <verb>-<noun>

eg: get-CMadvert, new-CMcollection, update-CMcollection


Till next time!


Nico Sienaert


Migrate from SCCM 2007 to SCCM 2012 Part 2

8:49 am in Uncategorized by nsienaert

Hi There!

In my previous post we have talked about the migration concept and how you establish a connection between a SCCM 2007 hierarchy and a SCCM 2012 hierarchy.

In this post we will talk about the actual Migration Jobs that can be created.

The migration wizard you can start by selecting “Create Migration Job”. I will highlight the most important windows.


In the wizard you can select the different objects you want to migrate. Nice, but the option to execute Collection Migration is even nicer! Because everything what is associated with these collections (Advertisements, Packages, Task Sequences,…) can be migrated as well.

You select the collections you want:


The wizard will list the associated objects and you can select which ones you want to migrate.


A Security Scope can be set (RBAC).

Role Based Access Control, I’ll blog about that in the future.


In one of my next blogs I will talk about the new replication model that is introduced with SCCM 2012. It might be possible that the next item is not really clear right now but please be patient. Knipogende emoticon

With the new replication model collections become “Global Data” which means that collections will be replicated all over the hierarchy, so it might be possible that the collection scope will increase. To avoid this, the migration tool will inform you and you will be able to limit the particular collections to another collection.

In this example I don’t have such a collection as this is a single server installation. But in a scenario where you have Central – Primary relations this will be common. For instance a collection created on a child primary site will now be migrated and replicated all over the hierarchy so the scope might increase.

If it’s not 100% clear it will hopefully be in my future post regarding the replication model. But now you know at least that the migration tool can deal with it. Knipogende emoticon


The migration tool will also evaluate all the queries on the collections. When a query is detected that is using an old Site Code you will be aware of that and you can change it on-the-fly.


The tool will track as well collections that can’t be migrated like mixed collections (users and computers). Since UDA in SCCM 2012 does not like that anymore.

Collections which are limited to muliple collections in SCCM 2007 will not be migrated as well. The tool will identify them so you are aware of these collections.


During the wizard specific info can be saved to a file for review afterwards.


You can select the required run time of the migration job, if objects can be overwritten, whether advertisements needs to be enabled,…


In the console you can see an overview of the migration jobs.


Detailled log info can be found in the Migmctrl.log.

Next time, in the last part, we talk about how the migraton tool will handle subcollections and the principal of Shared Distribution Points.

You can also watch my presentation at the Best of MMS event in Belgium:

Till next time!

Nico Sienaert


Migrate from SCCM 2007 to SCCM 2012 Part 1

10:11 am in Uncategorized by nsienaert

Hi There!

If you are running SCCM 2007 today you will probably migrate in the future to the latest SCCM release. The bad news is that you cannot upgrade in-place, the good news is that Microsoft created an excellent migration tool inside SCCM 2012 to migrate side-by-side.

Before we start:

1. A prerequiste to use the migration tool is that your SCCM 2007 servers are SP2 at least.

2. SCCM 2012 likes UNC very much, in case of Applications you HAVE to use UNC paths to browse to your data source. If you want to start following the best practices and you have packages in SCCM 2007 that are pointing to a local drive, you can use Kent Agerlund his tool to change all these local data source paths into UNC.

3. Install your new corresponding SCCM 2012 server, install all the required roles and configure SUP.

The reason why SUP needs to be configured is to make sure that update lists gets converted to Update Groups and Update Deployments are migrated to Deployments and Update Groups.

During the migration updates don’t get migrated, only the metadata. For that it’s also important that the catalog is identical.

You can use wsusutil.exe export/import for this or make sure if you sync with Microsoft Update that you select the same classifications.

So let’s look into the tool.

Active Source Hierarchy:

With this wizard we will connect the SCCM 2012 site to SCCM 2007 site.


Add the necessary credentials to get access to the SCCM 2007 site.


Start the gathering process…


In a complex hierarchy you will install your top SCCM 2012 server (CAS) and connect that one to the SCCM 2007 Central server to gather all necessary hierarchy info.

If you have multiple primary sites you will create an active Source Hierarchy for each SCCM 2007 site to the SCCM 2012 CAS to gather all objects metadata.

By default SCCM 2012 will check each 4 hours to keep the gathered data up-to-date.

Secondary sites need to uninstalled manually from the SCCM 2007 site. If you reinstall a secondary site on the SCCM 2012 consider if it’s still required –> Simplify hierarchy! Maybe a DP role is enough as we can now throttle DPs with SCCM 2012.

So what will be migrated?

Well everything, except:

  • Data Source content (see next post for more info)
  • OSD: boot images, because of the new WAIK in SCCM 2012
  • SubCollections, I talk about that in a next post.

Some things you need to know.

  • Classic Packages and Programs get migrated as-is, so no conversion to Applications. Microsoft will release later on a tool for doing the conversion to the new Application Model later on this year.
  • Clients retain execution history so they will not re-rerun advertisements if they don’t need to. You can upgrade them via your prefered deployment method (GPO, Push, OSD,…). Once upgraded a Full inventory data will be send once upgraded –> phased approach is advisable.
  • Keep Site Codes unique
  • SCCM 2007 Hardware Inventory can be imported into SCCM 2012 on Client Settings level.


  • 5 new reports are available to get more detailled info about the migration jobs.


So, we have talked about the existence of the built-in tool, how you connect sites and what things you have to take into account.

Next time, we will talk about the Migration jobs, shared SCCM 2007 DPs and many more.

You can also watch my presentation at the Best of MMS event in Belgium:

Till next Time!

Nico Sienaert