1) This represents a simple association between a single user/group and
a resource that they can be assigned to. Examples of associated
resources are Desktops, Applications,
GlobalEntitlements,GlobalApplicationEntitlements,or URLRedirection
Settings. Individual users/groups and resources may be associated with
multiple user entitlements.
2) Adding Get-Help changes for Pool
3) Configuring Clone Prep and Sys Prep script parameters to pool
1) Renamed Get-HVDesktopSpec to Get-HVPoolSpec.
2) Enhancements to examples
3) Enhancements to validation for farm and pool
4) ADDomainId handling for farm and pool
1. Create JSON files that will help in creation of new pools based on
existing pools configuration.
2. Configure all the pool attributes through JSON file.
3. Validation of the attributes passed in the JSON file.
1) Added text description for all the advanced function examples
2) Wild card support(only * character support) for farm (Get-HVFarm,
Get-HVFarmSummary)
1) Enabling WhatIf functionality to Advanced Functions (All get-xxx AF
not required)
2) Cloning Added support for all AFs except instant clone pools(need to
fix a bug in server side for instant clone)
3) Get-HVDesktopSpec Converts DesktopInfo to DesktopSpec
4) Converts View API ids to human readbale names
Adding new advanced functions Get-HVMachine and Get-HVMachineSummary.
Queries and returns virtual machines information, the machines list
would be determined based on queryable fields poolName, dnsName,
machineName, state. When more than one fields are used for query the
virtual machines which satisfy all fields criteria would be returned.
Implemented below Items:
1) Formatting DesktopSummaryData/MachineNamesView
2) Example typo correction
3) Start,Stop, Enable and Disable tasks moved from Start to Set for both
(Pool/Farm)
4) Internal functions Renaming
5) Start-HVPool --> Start-HVPool + Start-HVPoolSummary
6) Start-HVFarm --> Start-HVFarm + Start-HVFarmSummary
7) Plural function names to singular
Not implemented review comment get-hvevent output to be
(get-hvevents).Events
To pipe events to CSV file via Export-Csv cmdlet, events should be
PSCutomObject/PSObject. if we return only events, it will be hard user
to export events to CSV.
I will Implement rest of comments in next pull request.
