RemoteDesktopServicesDsc

4.1.0-preview0001

Module with DSC Resources for Remote Desktop Services

Minimum PowerShell version

5.0

This is a prerelease version of RemoteDesktopServicesDsc.

There is a newer prerelease version of this module available.
See the version list below for details.

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name RemoteDesktopServicesDsc -RequiredVersion 4.1.0-preview0001 -AllowPrerelease

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name RemoteDesktopServicesDsc -Version 4.1.0-preview0001 -Prerelease

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

dsccommunity

Copyright

Package Details

Author(s)

DSC Community

DSCResources

RDCertificateConfiguration RDConnectionBrokerHAMode RDGatewayConfiguration RDLicenseConfiguration RDRemoteApp RDServer RDSessionCollection RDSessionCollectionConfiguration RDSessionDeployment

Dependencies

This module has no dependencies.

Release Notes

## [4.1.0-preview0001] - 2026-03-20

### 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](https://github.com/dsccommunity/RemoteDesktopServicesDsc/issues/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](https://github.com/dsccommunity/RemoteDesktopServicesDsc/issues/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](https://github.com/dsccommunity/RemoteDesktopServicesDsc/issues/136)).
- Removed the now-redundant inline RDMS service start block from
`DSC_RDSessionDeployment` `Get-TargetResource`
([issue #136](https://github.com/dsccommunity/RemoteDesktopServicesDsc/issues/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](https://github.com/dsccommunity/RemoteDesktopServicesDsc/issues/138).

FileList

Version History

Version	Downloads	Last updated
4.2.0-previe...	2	4/10/2026
4.2.0-previe...	2	4/2/2026
4.1.0	619	3/23/2026
4.1.0-previe... (current version)	5	3/20/2026
4.0.1-previe...	2	3/19/2026
4.0.0	2,267	1/21/2026
3.1.0-previe...	3	1/21/2026
3.1.0-previe...	3	1/21/2026