-
Notifications
You must be signed in to change notification settings - Fork 1
Description
The code snippets in the Broker Filtering page (and, some other pages, such as Post-Installation Configuration) blend into the surrounding text:
Some cmdlets operate on large quantities of data and, to reduce the overhead of sending all of that data over the network, many of the Get- cmdlets support server-side filtering of the results.
The conventional way of filtering results in PowerShell is to pipeline them into Where-Object, Select-Object, and Sort-Object, for example:
Get- | Where { $_.Size = 'Small' } | Sort 'Date' | Select -First 10
However, for most XenDesktop cmdlets the data is stored remotely and it would be slow and inefficient to retrieve large amounts of data over the network and then discard most of it. Instead, many of the Get- cmdlets provide filtering parameters that allow results to be processed on the server, returning only the required results.
Please consider calling out code with a monospaced font, both inline, and in blocks:
Some cmdlets operate on large quantities of data and, to reduce the overhead of sending all of that data over the network, many of the
Get-cmdlets support server-side filtering of the results.The conventional way of filtering results in PowerShell is to pipeline them into
Where-Object,Select-Object, andSort-Object, for example:Get-<Noun> | Where { \$_.Size = 'Small' } | Sort 'Date' | Select -First 10However, for most XenDesktop cmdlets the data is stored remotely and it would be slow and inefficient to retrieve large amounts of data over the network and then discard most of it. Instead, many of the
Get-cmdlets provide filtering parameters that allow results to be processed on the server, returning only the required results.
XenDesktop also needs to be updates to CVAD :-)