Network Audit and Documentation, CENTREL Solutions Blog

Whilst working on our Citrix Documentation tool we've noticed some more inconsistency between the Citrix PowerShell commands. When you're looking to find the objects that are referenced by a scope you have to run several commands (for some reason there is no Get-ScopedObject cmdlet). Get-BrokerScopedObject Get-AcctScopedObject Get-HypScopedObject Get-ProvScopedObject The issue is that the Get-BrokerScopedObject returns the ObjectID as the UID an integer in string format of the object whereas the other command return the UUID (in GUID format). The UID is unique only within the object type whereas the UUID is universally unique to any object within the site and therefore more useful. The solution to this is to read the "ObjectType" enum value and then obtain the UUID using another command If the ObjectType is DesktopGroup then run the command Get-BrokerDesktopGroup =UID ObjectId If the ObjectType is Catalog then run the command Get-BrokerCatalog =U

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"