Skip to content

Releases: dsccommunity/RemoteDesktopServicesDsc

v4.2.0-preview0003

v4.2.0-preview0003 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 22 Jun 17:04
e567916

[v4.2.0-preview0003]

Changed

  • RDSessionDeployment
    • Converted to class-based resource issue #151.
      • WebAccessServer is now NOT a required parameter, mirroring the use
        of the underlying cmdlet.
  • RDConnectionBrokerHAMode

Fixed

  • RDSessionDeployment
    • Let base class add the key properties issue #153.

v4.2.0-preview0002

v4.2.0-preview0002 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 10 Apr 15:06
b52372c

[v4.2.0-preview0002]

Changed

  • RDSessionDeployment
    • Converted to class-based resource Issue #151.
      • WebAccessServer is now NOT a required parameter, mirroring the use
        of the underlying cmdlet.

Fixed

  • RDSessionDeployment
    • Let base class add the key properties Issue #153.

v4.2.0-preview0001

v4.2.0-preview0001 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 02 Apr 15:25
f97b34e

[v4.2.0-preview0001]

Changed

  • RDSessionDeployment
    • Converted to class-based resource Issue #151.
      • WebAccessServer is now NOT a required parameter, mirroring the use
        of the underlying cmdlet.

v4.1.0

Choose a tag to compare

@dscbot dscbot released this 23 Mar 11:05
7587a76

[v4.1.0]

Fixed

  • All DSC resources now import the RemoteDesktop CDXML module with
    Import-Module -Global instead of Assert-Module -ImportModule. The
    CDXML proxy commands were not visible inside wmiprvse.exe because
    Assert-Module imported into its own function scope. This caused every
    resource to fail with The term 'Get-RDServer' is not recognized when
    applied by the LCM on Windows Server 2022/2025
    (issue #136).
  • The RDMS service is now started before importing the RemoteDesktop module
    in every resource function. Previously, only DSC_RDSessionDeployment
    Get-TargetResource started the service, and only after the import
    attempt, causing failures after reboot when the delayed-start service had
    not yet registered its WMI namespace
    (issue #136).

Changed

  • Added shared helper function Import-RemoteDesktopModule to the
    RemoteDesktopServicesDsc.Common module to avoid duplicating the
    RDMS-start-and-import logic across all 9 DSC resources
    (issue #136).
  • Removed the now-redundant inline RDMS service start block from
    DSC_RDSessionDeployment Get-TargetResource
    (issue #136).
  • DSC_RDSessionDeployment
    • Fixed Set-TargetResource so it correctly calls New-RDSessionDeployment
      when no deployment exists. The $null check on the return value of
      Get-TargetResource was always $false because the function returns an
      empty hashtable, not $null - issue #138.

v4.1.0-preview0001

v4.1.0-preview0001 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 20 Mar 10:59
7587a76

[v4.1.0-preview0001]

Fixed

  • All DSC resources now import the RemoteDesktop CDXML module with
    Import-Module -Global instead of Assert-Module -ImportModule. The
    CDXML proxy commands were not visible inside wmiprvse.exe because
    Assert-Module imported into its own function scope. This caused every
    resource to fail with The term 'Get-RDServer' is not recognized when
    applied by the LCM on Windows Server 2022/2025
    (issue #136).
  • The RDMS service is now started before importing the RemoteDesktop module
    in every resource function. Previously, only DSC_RDSessionDeployment
    Get-TargetResource started the service, and only after the import
    attempt, causing failures after reboot when the delayed-start service had
    not yet registered its WMI namespace
    (issue #136).

Changed

  • Added shared helper function Import-RemoteDesktopModule to the
    RemoteDesktopServicesDsc.Common module to avoid duplicating the
    RDMS-start-and-import logic across all 9 DSC resources
    (issue #136).
  • Removed the now-redundant inline RDMS service start block from
    DSC_RDSessionDeployment Get-TargetResource
    (issue #136).
  • DSC_RDSessionDeployment
    • Fixed Set-TargetResource so it correctly calls New-RDSessionDeployment
      when no deployment exists. The $null check on the return value of
      Get-TargetResource was always $false because the function returns an
      empty hashtable, not $null - issue #138.

v4.0.1-preview0001

v4.0.1-preview0001 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 19 Mar 16:07
ea125f3

[v4.0.1-preview0001]

Fixed

  • DSC_RDSessionDeployment
    • Fixed Set-TargetResource so it correctly calls New-RDSessionDeployment
      when no deployment exists. The $null check on the return value of
      Get-TargetResource was always $false because the function returns an
      empty hashtable, not $null - issue #138.

v4.0.0

Choose a tag to compare

@dscbot dscbot released this 21 Jan 09:43
19eb185

[v4.0.0]

Changed

  • Renamed module to RemoteDesktopServicesDsc.
  • Remove last references to old module name.

v3.1.0-preview0002

v3.1.0-preview0002 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 21 Jan 09:34
19eb185

[v3.1.0-preview0002]

Changed

  • Renamed module to RemoteDesktopServicesDsc.
  • Remove last references to old module name.

v3.1.0-preview0001

v3.1.0-preview0001 Pre-release
Pre-release

Choose a tag to compare

@dscbot dscbot released this 21 Jan 01:17
4ec4a49

[v3.1.0-preview0001]

Changed

  • Renamed module to RemoteDesktopServicesDsc.

v3.0.0

Choose a tag to compare

@dscbot dscbot released this 12 Jan 19:53
5642b31

[v3.0.0]

Deprecated

  • The module xRemoteDesktopSessionHost will be renamed to RemoteDesktopServicesDsc
    (issue #117).
    The version v3.0.0 will be the the last release of xRemoteDesktopSessionHost.
    Version v4.0.0 will be released as RemoteDesktopServicesDsc, it will be
    released shortly after the v3.0.0 release to be able to start transition
    to the new module. The prefix 'x' will be removed from all resources in
    RemoteDesktopServicesDsc.

Fixed

  • xRDSessionCollection
    • Ignore errors from New-RDSessionCollection and instead checks the collection is created; resolves issue #105.
  • xRDSessionCollectionConfiguration
    • Updating UserGroups parameter to allow for an array to be supplied,
      resolves issue #115.
  • Always filter SessionCollection result; resolves issue #106.

Added

  • xRDConnectionBrokerHAMode
    • New resource to configure HA mode on a connection broker

Removed

  • Removed Get-LocalizedData and use version in DscResource.Common.

Changed

  • xRDSessionCollection
    • SessionHost supports array
    • Collections are now tested for SessionHosts as well, list of session hosts is amended
  • xRDSessionDeployment
    • SessionHost and WebAccessServer supports array
    • Deployments are now tested for WebAccess and SessionHosts as well
    • Resource can extend an existing deployment with more session hosts and web access servers
    • ConnectionBroker is only remaining key since the broker can only broker one deployment
  • xRDServer
    • Improve error handling in Set-TargetResource function for Add-RDServer
      cmdlet, fixes issue #111.
  • Fixed formatting in all source files, issue #113.
  • Update repo files to latest versions in Sampler. Fixes issue #118.
  • Enable DocGenerator and move docs to wiki. Fixes issue #101.
  • Renamed master branch to main. Fixes issue #116.
  • Migrated tests to Pester 5. Fixes issue #119.
  • Enable ModuleFast.
  • Use pwsh for unit tests.
  • Rename nested module to xRemoteDesktopSessionHost.Common.
  • Make xRemoteDesktopSessionHost.Common a buildable module.
  • DSCResources
    • Use Test-DscParameterState where possible.
    • Update formatting.
    • Use fully qualified types.
    • Add changes from PR #124
  • Update files from Plaster template.