Windows 10: Windows PowerShell DSC Resource Kit Release January 2017

Read more: https://blogs.msdn.microsoft.com/pow...-january-2017/

:)

 

Powershell not working

Depending on which update it was I noticed this on Spiceworks on 8/25:

Snap! Windows 10 update breaks PowerShell, Cisco patches NSA zero-days

Windows 10 update breaks PowerShell

Microsoft's latest update for Windows 10 arrived this past Tuesday and brought some unintended consequences for PowerShell users: the scripting language and command line no longer work.

According to ZDNet, "Microsoft explained that due to a missing .MOF (Management Object Format) file in the build package, the update breaks PowerShell Desired State Configuration (DSC), a feature that can be used by IT
admins to manage enterprise environments." IT admins that attempt to use DSC operations will see an "Invalid Property" error message. Microsoft also warns its latest update break the ability to import remote PowerShell sessions into a current session. "Microsoft
doesn't expect to remedy the PowerShell issues until it releases another update scheduled for August 30," ZDNet says

 

Windows 10 Upgrade from Win 7 on Virual Machine

Can you use Windows Desired State Configuration? I understand Microsoft is making Powershell Desired State Configuration available on Linux platforms too. It sounds like to me that correctly scripted DSC might be the way to monitor and make these type
of changes to a Windows 10 installation. DSC is all horribly new to me in person and I have as yet, not had time to look into the range of features. I fancy swatting up on DCS to find out. Would this be wise, or would I be wasting my effort?