The PowerShell proivder MSFT_RoleResource does not contain the corresponding MOF file

Doing some work on getting a very basic DSC example ready for my PowerShell class this week. Funny thing is, I did this entire demonstration on a flight last week and was just trying to polish it up. While doing it again, this bug pops out of no where. I found out on PowerShell.org a post by Dave Wyatt with a response by Don Jones to in install KB2883200. Since I was testing in isolated VMs, I just downloaded the MSU from Microsoft and pasted it onto the Source VMs desktop and installed it. Well, that one was already installed. But it was not installed on the target server. After installing it on both servers in this test, still no go. I then installed KB3037315 and then KB2894179. That did the trick!!!

KB3037315 I understand. It contains an update to DSC. KB2894179 however is concerned with the OOBE Wizard in Windows 8.1. No idea why that third update worked, but I wanted to put it out on the net in case someone bumps into this. My test VMs are not completely up to date so had they been, chances are I would not have bumped into this issue.

Thank you Dave and Don for the hints that I needed!

Comments

Eric Barb said…

This post was a life saver. Only needed KB3037315 myself, but I appreciate the tip. First DSC push complete!

April 17, 2015 at 9:49 PM

RKaucher said…

A life saver in deed! Thank you!

July 28, 2015 at 3:34 PM

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog