v8.3.0

• Changes to xPSDesiredStateConfiguration
  • README.md: Fixed typo.
    Steve Banik (@stevebanik-ndsc)
  • Adding a Branches section to the README.md with Codecov badges for both
    master and dev branch
    (issue #416).
• Changes to xWindowsProcess
  • Integration tests for this resource should no longer fail randomly. A
    timing issue made the tests fail in certain scenarios
    (issue #420).
• Changes to xDSCWebService
  • Added the option to use a certificate based on it's subject and template
    name instead of it's thumbprint. Resolves
    issue #205.
  • xDSCWebService: Fixed an issue where Test-WebConfigModulesSetting would
    return $true when web.config contains a module and the desired state was
    for it to be absent. Resolves
    issue #418.
• Updated the main DSCPullServerSetup readme to read easier, then updates the
  PowerShell comment based help for each function to follow normal help
  standards. James Pogran (@jpogran)
• xRemoteFile: Remove progress bar for file download. This resolves issues
  #165
  and
  #383
  Claudio Spizzi (@claudiospizzi)

v8.2.0

• xDSCWebService: Disable installing
  Microsoft.Powershell.Desiredstateconfiguration.Service.Resources.dll as a
  temporary workaround since the binary is missing on the latest Windows
  builds.

v8.1.0

• xDSCWebService: Enable SQL provider configuration

v8.0.0

• xDSCWebService
  • BREAKING CHANGE: The Pull Server will now run in a 64 bit IIS process by
    default. Enable32BitAppOnWin64 needs to be set to TRUE for the Pull
    Server to run in a 32 bit process.

v7.0.0

• xService
  • BREAKING CHANGE: The service will now return as compliant if the service
    is not installed and the StartupType is set to Disabled regardless of the
    value of the Ensure property.
• Fixed misnamed certificate thumbprint variable in example
  Sample_xDscWebServiceRegistrationWithSecurityBestPractices

v6.4.0

• xGroup:
  • Added updates from PSDscResources:
    • Added support for domain based group members on Nano server

v6.3.0

• xDSCWebService
  • Fixed an issue where all 64bit IIS application pools stop working after
    installing DSC Pull Server, because IISSelfSignedCertModule(32bit) module
    was registered without bitness32 precondition.

v6.2.0

• xMsiPackage:
  • Created high quality MSI package manager resource
• xArchive:
  • Fixed a minor bug in the unit tests where sometimes the incorrect
    DateTime format was used.
• xWindowsFeatureSet:
  • Had the wrong parameter name in one test case.

v6.1.0

• Moved DSC pull server setup tests to DSCPullServerSetup folder for new common
  tests.
• xArchive:
  • Updated the resource to be a high quality resource
  • Transferred the existing "unit" tests to integration tests
  • Added unit and end-to-end tests
  • Updated documentation and examples
• xUser
  • Fixed error handling in xUser
• xRegistry
  • Fixed bug where an error was thrown when running Get-DscConfiguration if
    the registry key already existed
• Updated Test-IsNanoServer cmdlet to properly test for a Nano server rather
  than the core version of PowerShell

v6.0.0

• xEnvironment
  • Updated resource to follow HQRM guidelines.
  • Added examples.
  • Added unit and end-to-end tests.
  • Significantly cleaned the resource.
  • Minor Breaking Change where the resource will now throw an error if no
    value is provided, Ensure is set to present, and the variable does not
    exist, whereas before it would create an empty registry key on the
    machine in this case (if this is the desired outcome then use the
    Registry resource).
  • Added a new Write property 'Target', which specifies whether the user
    wants to set the machine variable, the process variable, or both
    (previously it was setting both in most cases).
• xGroup:
  • Group members in the "NT Authority", "BuiltIn" and "NT Service" scopes
    should now be resolved without an error. If you were seeing the errors
    "Exception calling ".ctor" with "4" argument(s): "Server names cannot
    contain a space character."" or "Exception calling ".ctor" with "2"
    argument(s): "Server names cannot contain a space character."", this fix
    should resolve those errors. If you are still seeing one of the errors,
    there is probably another local scope we need to add. Please let us know.
  • The resource will no longer attempt to resolve group members if Members,
    MembersToInclude, and MembersToExclude are not specified.