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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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.

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Jason Yoder, MCT

Search This Blog