Specify the password for the user specified in the Username text box, here.Ĭonfirm the Password by retyping it here. The steps for assigning such privileges to a user are discussed in the Pre-requisites for monitoring the Citrix Delivery Controller 7.x. The Allow log on locally security privilege on the Delivery Controller host.In order to monitor the target Delivery Controller 7, eG requires a special user with the following privileges Refers to the port at which the specified host listens to. The IP address of the host for which this test is to be configured. Configurable parameters for the test Parameter Outputs of the test : One set of results for each delivery group that is configured with the Delivery Controller 7. Target of the test : Citrix Delivery Controller 7.xĪgent deploying the test : An internal agent Unregistered desktops, CPU-intensive desktops, disconnected desktops, and desktops available to users, which are managed by this broker, can thus be quickly and accurately isolated.
Hope you found this helpful and thanks for reading.With the help of this test, you can determine the maintenance mode of each delivery group managed by the monitored broker, and track the usage of desktops within each group. Read more information on these SDK commands here: >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_AG” -RemoveExcludedUsers “shilllabs\server2016” >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_AG” -ExcludedUserFilterEnabled $False >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_Direct” -RemoveExcludedUsers “shilllabs\server2016” >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_Direct” -ExcludedUserFilterEnabled $False The settings can be reversed with the following commands Logging into StoreFront again shows that the user no longer has access to the desktop To verify the exclusion now currently set for the AD group “Server2016”Īfter this value is set from the CLI, the GUI will display the message below since this cannot be configured via GUI at this timeĪdd the test1 user to the “Server2016” group >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_AG” -ExcludedUsers “shilllabs\server2016” >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_AG” -ExcludedUserFilterEnabled $True >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_Direct” -ExcludedUsers “shilllabs\server2016” >Set-BrokerAccessPolicyRule -name “XS Server 2016 PVS_Direct” -ExcludedUserFilterEnabled $True Set the exclusion for the AD group “Server2016” To verify the exclusion is not currently set The delivery group “XS Server 2016 PVS” is targeted for “Domain Users”Īnother view of the delivery group showing the user restrictionįrom the delivery controller, run the >Get-BrokerAccessPolicyRule -DesktopGroupName “XS Server 2016 PVS” The user “test1” is only part of the “AllUsers” and “Domain Users” groups See the examples below that illustrate how this works. This is where the “ExcludedUsers” parameter come in play. We then want to assign a new delivery group to specific user groups during the migration without having to change the legacy groups assignment, all while removing the legacy desktop icon from the groups that are migrated.
In this scenario, a legacy delivery group is assigned to “Domain Users”. To do this, we will leverage a set of commands in the XenApp and XenDesktop PowerShell SDK. I recently needed to find a way to exclude a group of users from a delivery group that was assigned to “Domain Users” without having to change who the group was targeting.
0 kommentar(er)
