Archive for August, 2013

ConfigMgr Clients not receiving any advertisements – unapproved / blocked?

August 17, 2013

On a freshly upgraded ConfigMGr 2012 SP1 environment, a customer noticed that machines did not get any advertisements anymore.  I was called in to investigate what happened.

I noticed the following:

– The machines were listed as members of the All Systems Collection.

– An OSD Task Sequence had been deployed to the All Systems Collections, making it available to only Media and PXE (not to configmgr clients).

Still, the machines they mentioned did not pick up any advertisements when booted through PXE.

However, other machines that were part of the All Systems collection, DID get the advertisement.

It turned out that the systems that did not get the advertisements, had not been added to the domain properly. Therefore, they had not automatically been approved in ConfigMgr, and were not allowed to access the ConfigMgr Site.

The analysis

I have reconstructed this in my lab environment, to show you what this looks like.

First, i installed a Windows 7 machine, adding it to a workgroup instead of to the domain. Then installed the ConfigMgr client, using the parameters /SMSMP=<my MP name> and /SMSSITECODE=<name of my ConfigMgr site>.

After this, the machine showed up in ConfigMGr in the All Systems Collection as Windowsclient-3:


Now when you would just look at this, you would think it is a member of the All Systems collection, and therefore would get all the advertisements (or deployments) that are targeted to this collection, right?

Well, no.

Let’s add some more columns to this view; rightclick the title bar, and you get a list of columns you can add to the view:


Let’s add the Approved and Domain columns;

unapproved-3Now we can clearly see that windowsclient-3 is not a member of the domain, and therefore also not approved.

Well, not automatically anyway. This is something we configure in the Site Hierarchie Settings:

unapproved-4As you can see, by default only computers that are member of the same domain, or a trusted domain are automatically approved.

Since the windowsclient-3 machine is not in any domain, but in a workgroup, it is not approved.

With it being “Not approved”, it is also denied access to Site content, like policy and Files.

So, although the system is listed in the All Systems collection, it will not get any Deployments advertised.

If i PXE boot the client:

unapproved-5Sorry, no OSD for you 🙂

On the machine itself, we see the following in the ConfigMgr Client:



On the “Actions”, we can see by the limited number of cycles available, that only the core client is installed, and no policy has been retrieved yet.

If we look through the client log files we see that it can contact the MP (since we specified this during client installation), but it will get no policy from it.

Also, it cannot contact find information about available MPs from Active Directory, since it is not a domain member.

So, the only thing it can do now, is to keep contacting its MP, and hope for Approval 🙂

Now, let’s Approve the client in the ConfigMgr Console, and see what happens.

Rightclick the machine and select “Approve”


Are we sure? :p


Now, a reboot of the client to speed things up, and a Machine Policy Retrieval later, the clients starts working, and then:

unapproved-10Well this looks better 🙂

And there we get the policy assigned to the collections:

unapproved-11See the “Software changes are required” balloon pop up in the corner?

Yes, this is one happy client now 🙂



Powershell for ConfigMgr 2012 – part 1 (introduction)

August 9, 2013

ConfigMgr 2012 comes with a lot of powershell cmdlets to make your life easier.

Since SP1, a whopping 471 of them even!

But how do we access them? There is no shortcut called “PowerShell for ConfigMgr” placed on your desktop after installation of ConfigMgr, we have to do some work for that ourselves.

How to:

First, start the x86 version of Powershell (run as admin).


Since the ConfigMgr Console is 32-bit still, and the powershell cmdlets come with the console, they are also 32-bits.

Then in powershell type: cd “C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin” to get to the proper folder where the ConfigMgr Powershell module is located.


Then we type Import-Module .\ConfigurationManager.psd1 to load the powershell module for Configuration Manager, making all the CmdLets available to us.


Now we can start running the cmdlets. But which are they, and what can we do with them?

For that, let’s first update the help files. Make sure your machine has internet connectivity, so the updated help files can be downloaded from Microsoft;

Type Update-Help

After the help-updates have been downloaded, let’s see which cmdlets we have now for Configuration Manager.

Type get-command -module ConfigurationManager | out-gridview

This will show a nice list of all available ConfigMgr Cmdlets


For a complete list of all the CmdLets, including a brief description of their function click here

You can get more info for each CmdLet by typing get-help <cmdlet>

For instance: get-help Add-CmDeploymentType

Now, we can also launch the PowerShell CmdLets from the ConfigMgr Admin Console!

However, it is very will hidden in my opinion.  Ever seen the little blue arrow on the top-left of the console?



Whoomp, there it is. A x86 Powershell session, started as admin.

Type Y to allow the execution of the script, and off you go.


In the next post, i will discuss some common useful Cmdlets, to create collections and such.


Office 2010 activation fails after SP2 with error 0x80070190

August 3, 2013

After installing SP2 for Office 2010, i was unable to activate the office installation. Although i entered the correct key, it wouldn’t activate, throwing the error “0x80070190” office couldn’t be activated.

Turned out that the solution was to start any of the office programs as admin (run as administrator) and then start the activation. Worked flawless then…