Parameters
-Name<String>
Specifies the administrative name of the new application rule. Each rule in the site's entitlement policy must have a unique name (irrespective of whether they are desktop or application rules).
Required? |
true |
Default Value |
|
Accept Pipeline Input? |
true (ByPropertyName) |
-DesktopGroupUid<Int32>
Specifies the unique ID of the desktop group to which the new application rule applies.
Required? |
true |
Default Value |
|
Accept Pipeline Input? |
true (ByPropertyName) |
-Description<String>
Specifies an optional description of the new application rule. The text is purely informational for the administrator, it is never visible to the end user.
Required? |
false |
Default Value |
null |
Accept Pipeline Input? |
true (ByPropertyName) |
-Enabled<Boolean>
Specifies whether the new application rule is initially enabled. A disabled rule is ignored when evaluating the site's entitlement policy.
Required? |
false |
Default Value |
true |
Accept Pipeline Input? |
true (ByPropertyName) |
-ExcludedUserFilterEnabled<Boolean>
Specifies whether the excluded users filter is initially enabled. If the filter is disabled then any user entries in the filter are ignored when entitlement policy rules are evaluated.
Required? |
false |
Default Value |
false |
Accept Pipeline Input? |
true (ByPropertyName) |
-ExcludedUsers<User[]>
Specifies the excluded users filter of the application rule, that is, the users and groups who are explicitly denied entitlements to published applications from the desktop group.
This can be used to exclude users or groups who would otherwise gain access by groups specified in the included users filter.
Required? |
false |
Default Value |
(empty list) |
Accept Pipeline Input? |
true (ByPropertyName) |
-IncludedUserFilterEnabled<Boolean>
Specifies whether the included users filter is initially enabled. If the filter is disabled then any user who satisfies the requirements of the access policy is implicitly granted an entitlement to an application session by the new rule.
Users who would be implicitly granted access when the filter is disabled can still be explicitly denied access using the excluded users filter.
Required? |
false |
Default Value |
true |
Accept Pipeline Input? |
true (ByPropertyName) |
-IncludedUsers<User[]>
Specifies the included users filter of the application rule, that is, the users and groups who are granted an entitlement to an application session by the new rule.
If a user appears explicitly in the excluded users filter of the rule or is a member of a group that appears in the excluded users filter, no entitlement is granted whether or not the user appears in the included users filter.
Required? |
false |
Default Value |
(empty list) |
Accept Pipeline Input? |
true (ByPropertyName) |
-LoggingId<Guid>
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.
Required? |
false |
Default Value |
|
Accept Pipeline Input? |
false |
-AdminAddress<String>
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.
Required? |
false |
Default Value |
Localhost. Once a value is provided by any cmdlet, this value will become the default. |
Accept Pipeline Input? |
false |