Citrix XenDesktop PowerShell cmdlet Get-BrokerScopedObject returns Object does not exist

We're currently working on XenDesktop support for our Citrix documentation tool and came across a problem today.

When you create a new scope and don't reference any objects using the Get-BrokerScopedObject cmdlet and passing the newly created scope identifier may return an Object does not exist error.

Get-BrokerScopedObject -ScopeId "1d3cf716-d063-4ed9-8ac1-fc8415cf6862"
Get-BrokerScopedObject : Object does not exist





This seems to be inconsistent behaviour because using the scope name returns no error and simply returns no results as you would expect.
Get-BrokerScopedObject -ScopeName "Quick scope"



Comments

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Enable function lock for F1-F12 on HP ZBook mobile workstations