Windows PowerShell Home
PSv4 DSC WindowsFeature / Role Resource should use the DISM cmdlets on Client OSes
9/3/2013 3:48:44 PM
User(s) can reproduce this bug
The WindowsFeature or Role Resource built in to Desired State Configuration is available on all OSes with WMF 4.0 but the provider uses the ServerManager module and its *-WindowsFeature cmdlets in its implementation meaning that it does not work on Client OSes (ie Windows 7 and 8.1).
How often does this happen?
Have you seen this problem before in this product?
Yes, this happens in all previous versions
1. Define a Configuration with Node "localhost" and a WindowsFeature resource with Ensure=Present.
2. Compile the configuration to a MOF file.
3. Use Start-DscConfiguration to apply the MOF to a Windows Server 2012 R2 computer. The nominated feature is installed if absent.
4. Use Start-DscConfiguration to apply the MOF to a Windows 8.1 computer. The configuration fails with the error "... is only supported on Server SKUs"
In step 4, when the client OS is detected, instead of throwing an error, the Resource provider should first try the DISM module's *-WindowsOptionalFeature cmdlets instead and then, only if the DISM module is absent, should it throw an error suggesting to download the DISM module for the client OS.
to post a comment.
Please enter a comment.
on 4/22/2014 at 2:42 PM
Our developers use Client SKUs and have environments running locally during dev. We would like to use the same scripts for setting up and maintaining developer machines and test servers
on 2/26/2014 at 6:35 PM
Very disappointed that this only works on servers. I need desired state on client machines also for my developers, testers, QA, etc
on 10/30/2013 at 4:44 PM
Like pretty much every developer anywhere, I have a copy of our web stack running on a client OS for dev purposes. Scripting both our dev stacks and server stacks is essential.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft