I am really excited to share that my latest article “Using PowerShell DSC to Deploy Update Packages” is now published online at WindowsNetworking.com (many thanks to fellow MVP Mitch Tulloch!).
By way of the Desired State Configuration feature, a standards based system management platform delivered as part of Windows PowerShell 4.0 and higher, you can deploy common update packages (.msu) – including Windows Management Framework 5 RTM which comes with PowerShell 5 – using DSC itself.
You are cordially invited to check out this article where your feedback here or via social media (@_leedesmond) is always welcome!
During the provisioning of a new Hyper-V virtual machine in Windows Server 2016 (or 2012 R2), you may encounter a rather baffling error while executing the New-VM cmdlet:
New-VM : The operation failed. User ‘Administrator’ failed to create external configuration store at ‘C:\vm\dc01’: The system cannot find the path specified.. (0x80070003) The operation failed because the file was not found.
You confirm receiving a similar message with the “New Virtual Machine Wizard” in Hyper-V Manager and that the user account has sufficient rights/permissions to create a new VM in the target directory.
This strange error could be attributed to a corrupted or missing “Virtual Machines” folder and/or content. This is located at “C:\ProgramData\Microsoft\Windows\Hyper-V” with a typical Hyper-V installation. To resolve this issue, recreate or restore the former’s contents from a working backup. Alternatively, uninstall and reinstall of the Hyper-V role may be in order. Note that this location contains .xml data setup as symbolic links (.symlink) to Hyper-V virtual machines.