This release includes updates to 12 DSC resource modules. In the past 6 weeks, 128 pull requests have been merged and 90 issues have been closed, all thanks to our amazing community!
The modules updated in this release are:
ComputerManagementDsc
SecurityPolicyDsc
SharePointDsc
SqlServerDsc
xActiveDirectory
xDhcpServer
xDscResourceDesigner
xExchange
xPowerShellExecutionPolicy (now deprecated since now in ComputerManagementDsc)
xPSDesiredStateConfiguration
xRemoteDesktopSessionHost
xWebAdministration
For a detailed list of the resource modules and fixes in this release, see the Included in this Release section below.
Our last community call for the DSC Resource Kit was on July 18. A recording of our updates will be available on YouTube soon. Join us for the next call at 12PM (Pacific time) on August 29 to ask questions and give feedback about your experience with the DSC Resource Kit.
We strongly encourage you to update to the newest version of all modules using the PowerShell Gallery, and don’t forget to give us your feedback in the comments below, on GitHub, or on Twitter (@PowerShell_Team)!
Please see our documentation here for information on the support of these resource modules.
Included in this Release
You can see a detailed summary of all changes included in this release in the table below. For past release notes, go to the README.md or CHANGELOG.md file on the GitHub repository page for a specific module (see the How to Find DSC Resource Modules on GitHub section below for details on finding the GitHub page for a specific module).
Module Name
Version
Release Notes
ComputerManagementDsc
5.2.0.0
PowershellExecutionPolicy:
Updated to meet HQRM guidelines.
Migrated the xPowershellExecutionPolicy from xPowershellExecutionPolicy and renamed to PowershellExecutionPolicy.
Moved strings to localization file.
Changed the scope from Global to Script in MSFT_ScheduledTask.Integration.Tests.ps1
Changed the scope from Global to Script ComputerManagementDsc.Common.Tests.ps1
ScheduledTask:
Added support for event based triggers, implemented using the ScheduleType OnEvent fixes Issue 167
SecurityPolicyDsc
2.4.0.0
Added additional error handling to ConvertTo-Sid helper function.
SharePointDsc
2.4.0.0
SPCacheAccounts
Fixed issue where the Test method would fail if SetWebAppPolicy was set to false.
SPDistributedCacheService
Updated resource to allow updating the cache size
SPFarm
Implemented ability to deploy Central Administration site to a server at a later point in time
SPInfoPathFormsServiceConfig
Fixed issue with trying to set the MaxSizeOfUserFormState parameter
SPProductUpdate
Fixed an issue where the resource failed when the search was already paused
SPProjectServerLicense
Fixed issue with incorrect detection of the license
SPSearchContentSource
Fixed issue where the Get method returned a conversion error when the content source contained just one address
Fixed issue 840 where the parameter StartHour was never taken into account
SPSearchServiceApp
Fixed issue where the service account was not set correctly when the service application was first created
Fixed issue where the Get method throws an error when the service app wasn’t created properly
SPSearchTopology
Fixed issue where Get method threw an error when the specified service application didn’t exist yet.
SPServiceAppSecurity
Fixed issue where error was thrown when no permissions were set on the service application
SPShellAdmins
Updated documentation to specify required permissions for successfully using this resource
SPTrustedIdentityTokenIssuerProviderRealms
Fixed code styling issues
SPUserProfileServiceApp
Fixed code styling issues
SqlServerDsc
11.4.0.0
Changes to SqlServerDsc
Updated helper function Restart-SqlService to have to new optional parameters SkipClusterCheck and SkipWaitForOnline. This was to support more aspects of the resource SqlServerNetwork.
Updated helper function Import-SQLPSModule
To only import module if the module does not exist in the session.
To always import the latest version of “SqlServer” or “SQLPS” module, if more than one version exist on the target node. It will still prefer to use “SqlServer” module.
Updated all the examples and integration tests to not use PSDscAllowPlainTextPassword, so examples using credentials or passwords by default are secure.
Changes to SqlAlwaysOnService
Integration tests was updated to handle new IPv6 addresses on the AppVeyor build worker (issue 1155).
Changes to SqlServerNetwork
Refactor SqlServerNetwork to not load assembly from GAC (issue 1151).
The resource now supports restarting the SQL Server service when both enabling and disabling the protocol.
Added integration tests for this resource (issue 751).
Changes to SqlAG
Removed excess Import-SQLPSModule call.
Changes to SqlSetup
Now after a successful install the “SQL PowerShell module” is reevaluated and forced to be reimported into the session. This is to support that a never version of SQL Server was installed side-by-side so that SQLPS module should be used instead.
Update most Test-TargetResource functions to output all invalid settings, instead of just the first detected invalid setting
xPowerShellExecutionPolicy
3.1.0.0
Deprecated this module. This resource module will no longer be released. Please use the PowerShellExecutionPolicy resource in ComputerManagementDsc instead.
xPSDesiredStateConfiguration
8.4.0.0
Changes to xPSDesiredStateConfiguration
Opt-in for the common tests validate module files and script files.
All files change to encoding UTF-8 (without byte order mark).
Opt-in for the common test for example validation.
Added Visual Studio Code workspace settings that helps with formatting against the style guideline.
Update all examples for them to be able pass the common test validation.
Added WebApplicationHandler resource for creating and modifying IIS Web Handlers. Fixes 337
Added WebApplicationHandler integration tests
Added WebApplicationHandler unit tests
Deprecated xIISHandler resource. This resource will be removed in future release
How to Find Released DSC Resource 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 enter a module’s name in the search box in the upper right corner of the PowerShell Gallery to find a specific module.
Of course, you can also always use PowerShellGet (available starting in WMF 5.0) to find modules with DSC Resources:
# To list all modules that tagged as DSCResourceKitFind-Module-TagDSCResourceKit# To list all DSC resources from all sources Find-DscResource
Please note only those modules released by the PowerShell Team are currently considered part of the ‘DSC Resource Kit’ regardless of the presence of the ‘DSC Resource Kit’ tag in the PowerShell Gallery.
How to Install DSC Resource Modules From the PowerShell Gallery
We recommend that you use PowerShellGet to install DSC resource modules:
Install-Module-Name<module name >
For example:
Install-Module-Name xWebAdministration
To update all previously installed modules at once, open an elevated PowerShell prompt and use this command:
Update-Module
After installing modules, you can discover all DSC resources available to your local system with this command:
Get-DscResource
How to Find DSC Resource Modules on GitHub
All resource modules in the DSC Resource Kit are available open-source on GitHub.
You can see the most recent state of a resource module by visiting its GitHub page at:
https://github.com/PowerShell/< module name >
For example, for the CertificateDsc module, go to:
https://github.com/PowerShell/CertificateDsc.
You are more than welcome to contribute to the development of the DSC Resource Kit! There are several different ways you can help. You can create new DSC resources or modules, add test automation, improve documentation, fix existing issues, or open new ones.
See our contributing guide for more info on how to become a DSC Resource Kit contributor.
Your help in developing the DSC Resource Kit is invaluable to us!
Questions, comments?
If you’re looking into using PowerShell DSC, have questions or issues with a current resource, or would like a new resource, let us know in the comments below, on Twitter (@PowerShell_Team), or by creating an issue on GitHub.
0 comments