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.
When you attempt to install the RTM version of “Remote Server Administration Tools for Windows 10” (KB2693643) using the downloaded MSU*, an error message may appear:
Windows Update Standalone Installer
Installer encountered an error: 0x80070422
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Ensure that the Windows Update (wuauserv) service is not set to Disabled in order to proceed. Be aware that this is valid for running any MSU package for that matter where the former supersedes the MSI counterpart for software installation, including the application of hotfixes and patches in newer Windows versions.
Note that with the recent release 1.10 (19 Nov 2015) of RSAT, it now supports a number of languages besides US-English (en-US)
de-DE, es-ES, fr-FR, it-IT, ja-JP, ko-KR, pt-BR, ru-RU, tr-TR, zh-CN, and zh-TW
Installation of a supported language pack listed above is mandatory if the base Windows 10 OS UI does not match any of the listed languages.
* Microsoft Update Standalone Package
Kurs: Windows Server 2012 R2 Basics (IS36.15.51)
Wo: EB Zuerich
Start: Mo. 09. Nov 2015 x 6
Zeit: 1800 – 2130 Uhr
Ob Einsteiger, Quersteiger oder Developer, fangen wir von Null mit der Grundlage von Windows Server Administration an.
Mehr Information und Anmeldung hier.
#PowerShell #ITPros #Events #Training @ebzuerich
Follow me for all the buzz -> @_leedesmond (Twitter)!
The Desired State Configuration, DSC (as well as CIM cmdlets) feature introduced in PowerShell 4.0, relies on properly configured and functional WinRM listeners. By virtue of creating a WinRM listener, PS remoting* is enabled automatically (this is the case since Windows Server 2012 out-of-the-box). DSC does not depend on the latter nor need to run off from machines joined to an Active Directory environment to operate.
In a Workgroup environment, you may encounter challenges pushing out the resulting MOF to the desired nodes via Start-DSCConfiguration despite running with elevated administrative privileges:
VERBOSE: Perform operation ‘Invoke CimMethod’ with following parameters, ”methodName’ = SendConfigurationApply, ‘className’ = MSFT_DSCLocalConfigurationManager,’namespaceName’ =
The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config.
+ CategoryInfo : NotEnabled: (root/Microsoft/…gurationManager:String) , CimException
+ FullyQualifiedErrorId : HRESULT 0x803380e4
+ PSComputerName : SERVER01
You verified that … Read more “TIP 1516 (PowerShell DSC): Access Denied in Workgroup Environment”