Updated DSC Resource Kit available in the PowerShell Gallery

We’ve been focusing on improving the quality of DSC Resource Kit during last few weeks and are glad to announce that all the fixes are now available in the newest versions of modules on the PowerShell Gallery.

We’ve accepted 95 pull requests, fixed 29 issues and updated 20 modules! In addition to that, xWindowsUpdate module got a new resource – xMicrosoftUpdate – allowing to enable or disable Microsoft Update on your target nodes. For detailed list of changes, please scroll to the table at the bottom of this post.

We encourage you to install the newest versions from the PowerShell Gallery and start playing with them!

 

Where can I find all released DSC modules?

To see a list of all released DSC Resource Kit modules, go to the PowerShell Gallery and display all modules tagged as DSCResourceKit. You can also type a module’s name in the search box on the upper right side of the PowerShell Gallery to find specific module.

Another way is to go directly to a specific module by typing it’s URL:

http://www.powershellgallery.com/packages/<Module_Name>

e.g.:

http://www.powershellgallery.com/packages/xWebAdministration

Of course, you can always use PowerShellGet (available in WMF 5.0) as well:

Find-DscResource

 

How can I install DSC resources from the PowerShell Gallery?

We recommend that you use PowerShellGet to install DSC resource modules:

Install-Module –Name <Module_Name>

e.g.

Install-Module –Name xWebAdministration

 

If you have previous versions of modules installed, you can update them by calling (from an elevated PowerShell prompt):

Update-Module

 

If there is an issue you are particularly concerned about, watch the version number in the PowerShell Gallery for updates to that particular resource. You can also file an Issue against the module on GitHub to help get it fixed.

After installing the modules, you can discover all of the resources available to your local system by running:

Get-DscResource

As with the previous Resource Kits, all the resources are experimental. The “x” prefix in the names stands for experimental – which means these resources are provided AS IS and are not supported through any Microsoft support program or service.

 

How can I find DSC modules on GitHub?

As we mentioned in April, we have gone to open-source development of DSC resources on GitHub. You can see the most recent state of all resources by going to their GitHub pages at https://github.com/PowerShell/<Module_Name>, e.g. for xCertificate module, go to: https://github.com/PowerShell/xCertificate.

All DSC modules are also listed as submodules of the DscResources repository, so that you can see them in one place (click the xDscResources folder).

 

How can I contribute?

We welcome contributors who want to add to the development of DSC resource modules, there’s many ways to do it. You can create new DSC resources or modules, add test automation, improve documentation, fix existing issues or open new ones. Most of the information you need to get started can be found in our contributing guide.

If you are not sure what can you do, but would like to help anyway, please take a look at list of open issues for DscResources repository. You can also check issues opened for specific modules by going to https://github.com/PowerShell/<Module_Name>/issues , e.g. https://github.com/PowerShell/xPSDesiredStateConfiguration/issues.

Your help in developing DSC resources is much appreciated!

 

What has been recently released?

You can see a detailed summary of all recent changes in the table below.

If you want to see a change log for previous versions, go to the GitHub repository page for a given module (see section “How can I find DSC modules on GitHub?” for details).

 

Module name

Version

Description

xActiveDirectory

2.6.0.0

  • Removed xDscResourceDesigner tests (moved to
      common tests)

xAzure

0.2.0.0

  • Fixed encoding

xDatabase

1.3.0.0

  • Fixed mandatory attributes in schema
  • Removed parameter DefaultDatabaseName
  • Aligned *.schema.mof with *.psm1 files

xDefender

0.2.0.0

  • Integrated AppVeyor changes

xDnsServer

1.2.0.0

  • Removed UTF8 BOM from MOF schema

xExchange

1.3.0.0

  • MSFT_xExchWaitForADPrep: Removed obsolete VerbosePreference parameter from Test-TargetResource
  •  Fixed encoding

xHyper-V

3.2.0.0

  • Added data type System.String to CheckSum parameter of Get/Set/Test-TargetResource functions and aligned indentation.
  • Minor fixes

xMySql

1.1.0.0

  • Resolved attribute between *.psm1 and *.schema.mof files.
  • Fixed encoding

xNetworking

2.3.0.0

  • MSFT_xDNSServerAddress: Added support for
      setting DNS for both IPv4 and IPv6 on the same Interface
  • MSFT_xDNSServerAddress: AddressFamily
      parameter has been changed to mandatory.
  • Removed xDscResourceDesigner tests (moved to
      common tests)
  • Fixed Test-TargetResource to test against all
      provided parameters
  • Modified tests to not copy file to Program
      Files

xPSDesiredStateConfiguration

3.5.0.0

  • MSFT_xPackageResource: Added ValidateSet to
      Get/Set/Test-TargetResource to match MSFT_xPackageResource.schema.mof
  • Added StartupTimeout to xService resource
  • Removed UTF8 BOM
  • Fixed bug causing xService to throw error when
      service already exists
  • Added code for pull server removal

xRemoteDesktopAdmin

1.1.0.0

  • Updated OutputType to System.Boolean for
      Test-TargetResource and removed for Set-TargetResource.

xRemoteDesktopSessionHost

1.1.0.0

  • Fixed encoding

xSharepoint

0.5.0.0

  • Fixed bug with detection of version in create
      farm
  • Minor fixes
  • Added support for SharePoint 2016 installation
  • MSFT_xSPCreateFarm: Added
      CentraladministrationPort parameter
  • Fixed issue with PowerShell session timeouts

xStorage

2.1.0.0

  • Fixed encoding

xSystemSecurity

1.1.0.0

  • Fixed encoding

xTimeZone

1.3.0.0

  • Updated tests: now we are deploying xTimeZone
      instead of overwriting PSModulePath to make tests pass on local machine
  • Updated validation attribute of
      IsSingleInstance parameter to match *.schema.mof

xWindowsUpdate

2.2.0.0

  • Added xMicrosoftUpdate resource to enable or
      disable Microsoft Update

xWinEventLog

1.1.0.0

  • MSFT_xWinEventLog: Added LogFilePath parameter
  • Fixed tests
  • Fixed encoding

xWordPress

1.1.0.0

  • Updated schema (ValueMap)
  • Fixed encoding

 

Questions, comments?

If you’re looking into using PowerShell DSC, but have questions, are blocked by issues with current resources, or a lack of resources, let us know in the comments or create an issue on GitHub.

 

Karol Kaczmarek          

PowerShell Team