Remove desktop groups from the system or remove them from a Remote PC catalog.
Remove-BrokerDesktopGroup [-InputObject] <DesktopGroup> [-Force] [-RemotePCCatalog <Catalog>] [-LoggingId <Guid>] [-AdminClientIP <String>] [-AdminAddress <String>] [-BearerToken <String>] [-TraceParent <String>] [-TraceState <String>] [-VirtualSiteId <String>] [<CommonParameters>]<br><br>Remove-BrokerDesktopGroup [-Name] <String> [-Force] [-RemotePCCatalog <Catalog>] [-LoggingId <Guid>] [-AdminClientIP <String>] [-AdminAddress <String>] [-BearerToken <String>] [-TraceParent <String>] [-TraceState <String>] [-VirtualSiteId <String>] [<CommonParameters>]
This cmdlet has 2 functions:
- Remove desktop groups from the system.
- Break Remote PC associations between desktop groups and a catalog.
The Remote PC relationships are used by Remote PC automation to determine which desktop groups a machine in a particular Remote PC catalog can be published to. The assignment policy rules belonging to those desktop groups also determines the set of users that are allowed to be assigned to machines from the catalog.
|Name||Description||Required?||Pipeline Input||Default Value|
|InputObject||Specifies the desktop groups to remove.||true||true (ByValue)||null|
|Name||Specifies the name of the desktop group to remove.||true||true (ByPropertyName)||null|
|Force||Remove desktop groups even if there are active sessions.||false||false||false|
|RemotePCCatalog||When this parameter is specified, Remote PC desktop groups are removed from the specified Remote PC catalog.||false||true (ByValue)||null|
|LoggingId||Specifies the identifier of the high level operation that this cmdlet call forms a part of. Desktop Studio and Desktop Director typically create High Level Operations. PowerShell scripts can also wrap a series of cmdlet calls in a High Level Operation by way of the Start-LogHighLevelOperation and Stop-LogHighLevelOperation cmdlets.||false||false|
|AdminClientIP||Internal use only.||false||false|
|AdminAddress||Specifies the address of a XenDesktop controller that the PowerShell snapin will connect to. This can be provided as a host name or an IP address.||false||false||Localhost. Once a value is provided by any cmdlet, this value will become the default.|
|BearerToken||Specifies the bearer token assigned to the calling user||false||false|
|TraceParent||Specifies the trace parent assigned for internal diagnostic tracing use||false||false|
|TraceState||Specifies the trace state assigned for internal diagnostic tracing use||false||false|
|VirtualSiteId||Specifies the virtual site the PowerShell snap-in will connect to.||false||false|
You can pipe desktop groups to Remove-BrokerDesktopGroup.
If a desktop group contains desktops when it is removed, these desktops are also removed (but the underlying broker machine remains).
A desktop group that still has active sessions cannot be removed unless the -Force switch is used.
C:\PS> Remove-BrokerDesktopGroup EMEA\*
Remove all desktop groups with names starting with "EMEA".
C:\PS> Get-BrokerDesktopGroup -Enabled $false | Remove-BrokerDesktopGroup -Force
Remove all desktops that are currently disabled even if there are active sessions.
C:\PS> Get-BrokerDesktopGroup -RemotePCCatalogUid 42 | Remove-BrokerDesktopGroup -RemotePCCatalog 42
Remove all the Remote PC desktop groups that are associated with catalog 42. Note that this only breaks the Remote PC relationships and does not delete the desktop groups.