Citrix Daas SDK

New-BrokerRemotePCAccount

Create a new RemotePCAccount.

Syntax

New-BrokerRemotePCAccount
   [-AllowSubfolderMatches <Boolean>]
   -CatalogUid <Int32>
   [-MachinesExcluded <String[]>]
   [-MachinesIncluded <String[]>]
   -OU <String>
   [-LoggingId <Guid>]
   [<CitrixCommonParameters>]
   [<CommonParameters>]
<!--NeedCopy-->

Description

Create a new RemotePCAccount. A RemotePCAccount defines machine filters to support Remote PC automation adding unconfigured machines to catalogs.

Examples

EXAMPLE 1

Create a RemotePCAccount that adds unconfigured machines with computer objects in MyOU, into catalog 42.

New-BrokerRemotePCAccount -OU 'ou=MyOU,dc=MyDomain,dc=com' -CatalogUid 42
<!--NeedCopy-->

EXAMPLE 2

Create a RemotePCAccount matching unconfigured machines from DOMAIN1, except those with hostnames containing JOHNDOE, and add them to catalog 42.

New-BrokerRemotePCAccount -OU 'any' -CatalogUid 42 -MachinesIncluded @('DOMAIN1\*') -MachinesExcluded @('DOMAIN1\*JOHNDOE*')
<!--NeedCopy-->

EXAMPLE 3

Create a RemotePCAccount that matches any unconfigured machine, causing automation to add matching machines to catalog 42.

New-BrokerRemotePCAccount -OU 'any' -CatalogUid 42
<!--NeedCopy-->

Parameters

-CatalogUid

Specifies the catalog which Remote PC automation adds an unconfigured machine to if it matches this RemotePCAccount.

Type: Int32
Position: Named
Default value: None
Required: True
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False

-OU

Specifies the DN of an AD container, or has the special value ‘any’.

When an AD container is specified a machine may only match with the RemotePCAccount when the AD computer object is located relative to the OU.

When ‘any’ is specified the location of the AD computer object is ignored for purposes of matching this RemotePCAccount. The machine must still meet the MachinesIncluded and MachinesExcluded filters for a match to occur.

In the event that a machine matches with multiple RemotePCAccounts then the RemotePCAccount OU with the longest canonical name takes precedence. The special ‘any’ OU is treated as lowest priority.

Note that the OU value of every RemotePCAccount must be unique, and this includes only one ‘any’ entry being permitted.

Type: String
Position: Named
Default value: Null
Required: True
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: True

-AllowSubfolderMatches

When true a machine matches this RemotePCAccount if the AD computer object exists within the container specified by the OU property, or within a child container of the OU.

When false the AD computer object only matches if it exists directly in the AD container specified by the OU property.

This property is not meaningful when OU has the special value ‘any’.

Type: Boolean
Position: Named
Default value: False
Required: False
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False

-MachinesExcluded

MachinesExcluded specifies a set of strings that can include asterisk wildcards. If a machine name matches any entries in MachinesExcluded then it cannot match with this RemotePCAccount regardless of whether there is a MachinesIncluded match.

Matches are performed against the domain name joined with the machine name by a backslash (DOMAIN\MACHINE), e.g.:

DOMAIN1\M*

DOMAIN*\M*

*\M*

Type: String[]
Position: Named
Default value: @()
Required: False
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False

-MachinesIncluded

MachinesIncluded specifies a set of strings that can include asterisk wildcards. A machine may only match with this RemotePCAccount if it matches a MachinesIncluded entry and does not match any MachinesExcluded entries.

Matches are performed against the domain name joined with the machine name by a backslash (DOMAIN\MACHINE), e.g.:

DOMAIN1\M*

DOMAIN*\M*

*\M*

Type: String[]
Position: Named
Default value: @(‘*’)
Required: False
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False

-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.

Type: Guid
Position: Named
Default value: None
Required: False
Accept pipeline input: False
Accept wildcard characters: False

CitrixCommonParameters

This cmdlet supports the common Citrix parameters: -AdminAddress, -AdminClientIP, -BearerToken, -TraceParent, -TraceState and -VirtualSiteId. For more information, see about_CitrixCommonParameters.

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

Inputs

None

You cannot pipe input into this cmdlet.

Outputs

Citrix.Broker.Admin.SDK.RemotePCAccount

The newly created RemotePCAccount.

New-BrokerRemotePCAccount