Introduction

The xDismFeature module is a part of the Windows PowerShell Desired State Configuration (DSC) Resource Kit, which is a collection of DSC Resources produced by the PowerShell Team. This module enables or disables Windows optional features that specifically need to be handled by DISM.exe. The xDismFeature module contains a single resource, xDismFeature.

All of the resources in the DSC Resource Kit are provided AS IS, and are not supported through any Microsoft standard support program or service. The ""x" in xDismFeature stands for experimental , which means that these resources will be fix forward and monitored by the module owner(s).

Please leave comments, feature requests, and bug reports in the Q & A tab for this module.

If you would like to modify xDismFeature module, feel free. When modifying, please update the module name, resource friendly name, and MOF class name (instructions below). As specified in the license, you may copy or modify this resource as long as they are used on the Windows Platform.

For more information about Windows PowerShell Desired State Configuration, check out the blog posts on the PowerShell Blog ( this is a good starting point). There are also great community resources, such as PowerShell.org, or PowerShell Magazine. For more information on the DSC Resource Kit, check out this blog post.

Installation

To install the xDismFeature module

To confirm installation:

Requirements

This module requires the latest version of PowerShell (v4.0, which ships in Windows 8.1 or Windows Server 2012R2). To easily use PowerShell 4.0 on older operating systems, install WMF 4.0. Please read the installation instructions that are present on both the download page and the release notes for WMF 4.0.

Description

The xDismFeature module contains the xDismFeature DSC Resource. This DSC module enables the install and uninstall of features that require the use of DISM.EXE

xDismFeatureConsoleSetup has the following properties:

Renaming Requirements

When making changes to these resources, we suggest the following practice:

  1. Update the following names by replacing MSFT with your company/community name and replacing the "x" with "c" (short for "Community") or another prefix of your choice:
    • Module name (ex: xDismFeature becomes cDismFeature)
    • Resource folder (ex: MSFT_xDismFeature becomes Contoso_cDismFeature)
    • Resource Name (ex: MSFT_xDismFeature becomes Contoso_cDismFeature)
    • Resource Friendly Name (ex: xDismFeature becomes cDismFeature)
    • MOF class name (ex: MSFT_xDismFeature becomes Contoso_cDismFeature)
    • Filename for the <resource>.schema.mof (ex: MSFT_xDismFeature.schema.mof becomes Contoso_cDismFeature.schema.mof)
  2. Update module and metadata information in the module manifest
  3. Update any configuration that use these resources

We reserve resource and module names without prefixes ("x" or "c") for future use (e.g. "MSFT_DismFeature" or "DismFeature"). If the next version of Windows Server ships with "MSFT_DismFeature" resources, we don't want to break any configurations that use any community modifications. Please keep a prefix such as "c" on all community modifications.

Versions

1.0.0

Example: Enable the Single Instance Storage feature on Windows Server

PowerShell
Edit|Remove
    Configuration SIS-Limited 
    { 
    Import-DscResource -Module xDismFeature 
 
    Node 'NodeName' 
    { 
    Ensure = 'Present' 
    Name = 'SIS-Limited' 
    } 
    }
 

Example: Disable the Single Instance Storage feature on Windows Server.

PowerShell
Edit|Remove
    Configuration SIS-Limited 
    { 
    Import-DscResource -Module xDismFeature 
 
    Node 'NodeName' 
    { 
    Ensure = 'Absent' 
    Name = 'SIS-Limited' 
    } 
    }