Hi All
Today I've noted the following when a Collection is renamed through RDS Server Manager:
- The icon folder store on all Collection Broker servers (HA) C:\Windows\RemotePackages\CPubFarms\<CollectionName> doesn't change from the original name.
- The Collection name registry keys living [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\<CollectionName> also remain with the original Collection name.
- Reboots do not force a synchronisation.
- If either the registry key or folders mentioned above are renamed manually, within approx 10 minutes RDS renames them back (or creates fresh copies) using the Collection name originally used upon Collection creation - not using the new name!
1. Is there a way to synchronise these?
2. Can PowerShell be used to rename a session Collection?
I spotted this cmdlet: Set-RDSessionCollectionConfiguration however there appears no way of entering both old and new Collection names should you wish to rename a Collection, so it implies only the properties can be modified, not its name.
3. Can a Collection and all attributes and applications be copied to another new Collection?
Custom Icons
I'm unsure how the IconPath variable is used within the cmd: Set-RDRemoteApp -CollectionName "<MyCollectionName>" -Alias "MyAppAlias" -IconPath""
-IconPath<String>
Specifies the path to a file containing the icon to display for the RemoteApp program identified by the Alias parameter. This path must not contain any environment variables. For session collections, the path must be a valid local
path on all RD Session Host servers in the collection. For virtual desktop collections, the path must be a valid local path on all virtual desktops in the collection.
The reason I'm confused is that if I point -IconPath to an icon which doesn't have the same name as the App Alias, PowerShell will copy this icon to C:\Windows\RemotePackages\CPubFarms\<CollectionName> and rename it such it does. However
Get-RDRemoteApp -alias "<MyAppAlias>" | fl shows IconPath reflecting the original icon file, not the one which RDS has created using the same name as the App's alias.
RD Web displays the icon correctly and I can confirm that the icon RDS creates using the same name as the App Alias is the one being used (not the one pointed to by IconPath) by simply renaming it and watching it disappear from RDWeb.
1. If IconPath doesn't actually match the icon RDS is now using to display, what (if any) are the consequences?
2. What's the actual purpose of IconPath?
3. To align IconPath with the actual .ico RDS is using to display (which to me sounds logical), should I simply create multiple icons from the original source named using each app alias, store here: C:\Windows\RemotePackages\CPubFarms\<CollectionName>\MyAppAlias.ico and register IconPath with C:\Windows\RemotePackages\CPubFarms\<CollectionName>\MyAppAlias.ico
4. Is IconPath used just once when the PowerShell script is run - therefore maybe has no relevance after?
Questions question I know!
Thanks for any pointers...
Lea