The format is based on and uses the types of changes according to Keep a Changelog, and this project adheres to Semantic Versioning.
- xRDSessionCollection
- Ignore errors from New-RDSessionCollection and instead checks the collection is created; resolves issue #105
- Always filter SessionCollection result; resolves issue #106
- xRDConnectionBrokerHAMode
- New resource to configure HA mode on a connection broker
- 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
- xRemoteDesktopSessionHost
- New examples for the resources
- xRemoteDesktopSessionHost
- Pipeline deploy task updated to use image
ubuntu-latest
. - Update pipeline files to the latest from Sampler's DSC Community template.
- Pipeline deploy task updated to use image
- xRDCertificateConfiguration
- import of RemoteDesktop module is now global; resolves issue #79
- xRDSessionCollection
- Workaround for bug in Windows Server 2019. Added a conditional match on returned
Collections from
Get-RDSessionCollection
to workaround bug scenario where multiple collections are returned instead of a single collection.
- Workaround for bug in Windows Server 2019. Added a conditional match on returned
Collections from
- xRDCertificateConfiguration
- Verbose messages now uses the correct localized strings.
- Updated filename for CHANGELOG.MD to CHANGELOG.md
- Changes to xRemoteApp
- Updating
UserGroups
parameter to allow for an array to be supplied - Updating comparison of current properties and supplied parameters by moving
to the DscResource.Common
Test-DscParameterState
cmdlet. This was necessary to allow for the change with theUserGroups
parameter to allow an array object.
- Updating
- Change to xRDGatewayConfiguration
- Updated call to
Set-RDDeploymentGatewayConfiguration
cmdlet to useErrorAction
'Stop' - Updated call to
Set-RDDeploymentGatewayConfiguration
cmdlet to use a splat for better formatting
- Updated call to
- Changes to tests
- xRDRemoteApp
- Fixed tests for error scenarios to behave correctly
- xRDGatewayConfiguration
- Fixed tests for error scenarios to behave correctly
- xRDRemoteApp
- xRemoteDesktopSessionHost
- Added automatic release with a new CI pipeline.
- Added DSC HQRM Tests
- xRDCertificateConfiguration
- New resource to configure the used certificate on a deployment
- Changes to xRDSessionCollectionConfiguration
- Fixing comparison of some RD Session Collection Configuration properties and
supplied parameters by moving to the DscResource.Common
Test-DscParameterState
cmdlet. (issue #82).
- Fixing comparison of some RD Session Collection Configuration properties and
supplied parameters by moving to the DscResource.Common
- Changes to xRDSessionDeployment
- Fixing Get-TargetResource to target the connection broker, instead of assuming localhost
- Changes to xRDServer
- Changed resouce key from Server alone to Role + Server. This allows the resource to be used multiple times for different roles on the same server. (Issue #62)
- Changes to xRemoteApp
- Fix xRDRemoteApp Test-TargetResource to not test PowerShell common parameters
- Changes to tests
- Pin tests to use Pester v4 instead of latest (v5)
- Changes to xRDRemoteApp
- Fixing typo in parameter name when calling the function ValidateCustomModeParameters (issue #50).
- Changes to xRDSessionDeployment
- When RDMS service does not exist the Get-TargetResource will no longer throw an error (issue #47).
- Rename Tests/Unit folder to use upper case on first letter.
- Update appveyor.yml to use the default template.
- Added default template files .codecov.yml, .gitattributes, and .gitignore, and .vscode folder.
- xRDSessionCollectionConfiguration:
- Changed CollectionName variable validation max length to 256
- xRDSessionCollection
- Changed CollectionName variable validation max length to 256
- xRDRemoteApp
- Changed CollectionName variable validation max length to 256
- Changes to xRDSessionDeployment
- Fixed issue where an initial deployment failed due to a convert to lowercase (issue #39).
- Added unit tests to test Get, Test and Set results in this resource.
- Change to xRDRemoteApp
- Fixed issue where this resource ignored the CollectionName provided in the parameters (issue #41).
- Changed key values in schema.mof to only Alias and CollectionName, DisplayName and FilePath are not key values.
- Added Ensure property (Absent or Present) to enable removal of RemoteApps.
- Added unit tests to test Get, Test and Set results in this resource.
- Added additional resources, copied from the Azure RDS quickstart templates.
- xRDSessionCollection:
- Fixed call to Add-RDSessionHost in Set-TargetResource by properly removing CollectionDescription from PSBoundParameters (issue #28)
- Fixed bug on Get-TargetResource that did return any collection instead of the one collection the user asked for (issue #27)
- Added unit tests to test Get, Test and Set results in this resource
- xRDSessionCollectionConfiguration: Add support to configure UserProfileDisks on Windows Server 2016
- Fix issue where DSC configuration gets into a reboot loop because sessionhost does not match (casing) and RDMS service is not started in time
- Updated CollectionName parameter to validate length between 1 and 15 characters, and added tests to verify.
- Converted appveyor.yml to install Pester from PSGallery instead of from Chocolatey.
- Fixed an issue with version checks where OS version greater than 9 would fail (Windows 10/Server 2016)
- Fixed encoding
- Initial release with the following resources
- xRDSessionDeployment
- xRDSessionCollection
- xRDSessionCollectionConfiguration
- xRDRemoteApp