Error trying to open the ConfigMgr Console

Last week I had some problems with opening the ConfigMgr Console. The weird part was that the error only appeared for one user. This was the error I got: MMC cannot open the file <driver>:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\bin\adminconsole.msc. This may be because the file does not excist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient rights to the file. Then I figured that, because the ConfigMgr Console is a MMC snap-in, it creates a version in the user profile. Because I use Windows 7 and Windows Server 2008 R2 it is located at: <Drive>:\Users\<Username>\AppData\Roaming\Microsoft\MMC\adminconsole.msc. So after deleting the version from the profile and restarting the ConfigMgr Console it …

Read moreError trying to open the ConfigMgr Console

ConfigMgr 2007 and Binary Differential Replication

In a previous post I already mentioned Binary Differential Replication (BDR). In this post I will also show how to configure it. ConfigMgr 2007 can use BDR to update package source files with a minimum of additional network traffic. When ConfigMgr 2007 updates the source files for a package, and uses BDR, it sends the parts of the package that have changed since the last time the package was sent. So BDR will work after the source files have already been distributed. This minimizes the network traffic, especially when the package is large and the changes are small. A file is considered to be changed if it has been renamed, moved, or its contents have changed. BDR will work as long as a site has …

Read moreConfigMgr 2007 and Binary Differential Replication

ConfigMgr Client failed to download policy

Sometimes it happens that a client cannot get its policies and the only errors you can find are that the Download of policy [PolicyID, PolicySource, PolicyVersion] failed (PolicyAgent.log) and that the DTSJob is in state ‘Error’ (DataTransferService.log). The weird part in here is that the client can connect to the Management Point (MP). By looking at it with BitsAdmin it shows that not all the policies can be downloaded. The errors that it shows, look like there are problems with WMI. Now that the problem is located it is easy to solve. The only thing that has to happen is to repair WMI and to re-register the WMI Services. How to repair and re-register WMI Stop the WMI Service (winmgmt), Remove the folder Repository in %systemroot%\system32\wbem, …

Read moreConfigMgr Client failed to download policy

ConfigMgr 2007 SP2 is now officially released!

I can be really short about this… … …ConfigMgr 2007 SP2 is now officially released! For a download and a overview take a look here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140

Compatibility of different types of Distribution Points

I noticed that it can be handy to know which types of Distribution Points are compatible with each other. For example, if you want to setup Multicast you can NOT use a Server Share. There is documentation about this, but for me it was hard to find. This is why I posted the most important part of this article (the compatibility table) in this post.   Server Server Share Branch Standard BITS-Enabled Protected Mobile Device Support Internet Based Clients Streaming Multicast Server N/A No Yes Yes Yes Yes Yes Yes Yes Yes Server Share No N/A No No Yes Yes Yes No Yes No Branch Yes No N/A No No Yes No No Yes No Standard Yes No No N/A Yes Yes Yes Yes Yes …

Read moreCompatibility of different types of Distribution Points

Distribution Point Groups in ConfigMgr 2007

This time I want to devote a post to Distribution Point Groups in ConfigMgr 2007. The most important thing to understand is that Distribution Point Groups are NOT meant to balance the load. Distribution Point Groups are meant to facilitate the processes of copying packages to Distribution Points (DP). Packages can then be sent to a Group of DP’s rather than to a single DP. One important thing to remember is that if you add a DP to an existing Group of DP’s, the new DP does not automatically receive packages that are previously copied to that Group. Create a Distribution Point Group by following the next steps: Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Site …

Read moreDistribution Point Groups in ConfigMgr 2007

ConfigMgr 2007, USMT 4.0 and using Hard-Links

One of the coolest new functions of USMT 4.0 is the new hard-link migration store (only for computer-refresh scenarios). These migration stores are stored locally on the computer that is being refreshed and can migrate user accounts, files and settings. This way it will save time and space during a computer-refresh (and you do not need a State Migration Point!). When you create a default Task Sequence it will create the steps Request User State Storage and Release User State Storage. These steps are needed to interact with the State Migration Point (SMP) to get available space and to tell that the action completed successfully. So these steps are not needed anymore when you are using hard-links! This is why these steps are grayed out …

Read moreConfigMgr 2007, USMT 4.0 and using Hard-Links

Copy logs from a failed Task Sequence in ConfigMgr 2007

I like to do multiple things at a time… So I don’t like to wait on my Task Sequence, after I made a a few changes, to see if it doesn’t fail. This is why I searched for some sort of error catching in a Task Sequence. During this search I found this great article of Steve Raichu: http://blogs.msdn.com/steverac/archive/2008/07/15/capturing-logs-during-failed-task-sequence-execution.aspx In this article he explains the following important steps that are needed for an automatic error catching: Use a top group in a Task Sequence that is set to Continue on error. The rest of your functioning Task Sequence has to be added under this group. In this way the Task Sequence will continue to the following group if a part of the Task Sequence has …

Read moreCopy logs from a failed Task Sequence in ConfigMgr 2007

Remote Distribution Points in ConfigMgr 2007

This post will be a short follow-up on a previous post about How a client chooses a Distribution Point. In that post I tried to explain how a client picks a (Remote) Distribution Point (DP). In this post I will try to take away some more confusion about Remote DP’s. Let’s start with when a DP is considered a Remote DP. ConfigMgr looks at this from the clients perspective. If a client is within a Fast Network Boundary, then the DP(‘s) that is in the same Boundary will be marked as a Local DP. All the other DP’s are marked as Remote DP’s. The important part here is that a client has to be within the correct Boundary and that you are the only one who …

Read moreRemote Distribution Points in ConfigMgr 2007

How to create a Capture Only Task Sequence with ConfigMgr 2007

Some things are a lot easier then you might think. One of these things is creating a Capture Only Task Sequence. As you all know there is the option within ConfigMgr 2007 to create a Build and Capture Task Sequence, well creating a Capture Only Task Sequence is nothing more then taking the Capture part of the default Build and Capture Task Sequence. So I use in my Capture Only Task Sequence the following steps: Join Workgroup (this step is only necessary when the Reference Machine is joined to a domain) Prepare ConfigMgr Client Prepare OS Capture the Reference Machine The first steps all need to run in Full OS, which means that you can’t start this Task Sequence by booting in WinPE. I just …

Read moreHow to create a Capture Only Task Sequence with ConfigMgr 2007