dsccommunity / xRemoteDesktopSessionHost

This module contains DSC resources for the management and configuration of Microsoft Remote Desktop Session Host (RDSH).

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Missing xRDServer resource?

figueroadavid opened this issue · comments

Is this resource actually missing from the module? It is in the readme, but when I check it is not there?

PS C:\> Get-DscResource -Module xremotedesktopsessionhost

ImplementedAs   Name                      ModuleName                     Version    Properties
-------------   ----                      ----------                     -------    ----------
PowerShell      xRDRemoteApp              xRemoteDesktopSessionHost      1.6.0.0    {Alias, CollectionName, DisplayN...
PowerShell      xRDSessionCollection      xRemoteDesktopSessionHost      1.6.0.0    {CollectionName, SessionHost, Co...
PowerShell      xRDSessionCollectionCo... xRemoteDesktopSessionHost      1.6.0.0    {CollectionName, ActiveSessionLi...
PowerShell      xRDSessionDeployment      xRemoteDesktopSessionHost      1.6.0.0    {ConnectionBroker, SessionHost, ...

I'm looking to use this to configure my hosts that won't be part of an RDS Deployment..

Thanks,

David F.

For some reason, the edit on my post is being eaten/rejected, etc..
I am specifically looking for the xRDServer resource..

David F.

It do exist in the code https://github.com/PowerShell/xRemoteDesktopSessionHost/tree/dev/DSCResources/MSFT_xRDServer, not sure why you are not seeing it though.

Hi @figueroadavid, the xRDServer resource was just added and will be released in the next version of xRemoteDesktopSessionHost. If you want to use it right now, just clone the repository or download the zip of the dev branch, this will include xRDServer.

I was just about to say what @danielboth said ☺️ thanks Daniel!

@figueroadavid please submit a new issue, for the suggested enhancement.

Leaving this open until we release if others have the same question.

commented

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

This is released now, so closing this issue.