- When integrating Awingu with a Remote Desktop Services (RDS) broker, applications in an RDS Session Collection do not work.
- The end user sees an "error 410" message when trying to launch an application.
Some scenarios cause a mismatch between the RDS Session Collection name used in Microsoft Windows and the settings configured in Awingu.
- Session collection was renamed (and the new name is shown in the GUI); while Microsoft Windows Server still uses the original name in the background.
- Session collection names must be truncated to 15 characters (NETBIOS limit).
- Spaces are converted to underscores in the internal name of a Session Collection..
- Dots are stripped from the internal name of a Session Collection.
In the following situations, a mismatch between the Session Collection name as shown in the Microsoft Windows Server GUI and the value specified in the Awingu label can occur:
1. Changing the Session Collection name
In an RDS farm with broker, when changing the name of an existing Session Collection (and changing rdscollection labels accordingly in Awingu), applications via Awingu don't work anymore.
When the name is changed, it seems that Microsoft Windows only updates it in the GUI and still uses the original name in the background (for example when downloading an RDP file via RDWeb).
Check the following to learn the original name of the Session Collection when it was created:
Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\<CollectionName>
File Path: C:\Windows\RemotePackages\CPubFarms\<CollectionName>
It is this name that must be used as an rdscollection: label in Awingu for the applications to work using the RDS Broker. For example, when initially creating Session Collection 'CollectionA' and renaming it to 'CollectionB', use the following label for the broker/application in Awingu: rdscollection:CollectionA .
2. Long Session Collection Names
Session collection names with more than 15 characters will get truncated to 15 characters because of the NETBIOS character limit. This will result in a mismatch between the collection name shown in the GUI and the actual collection name as stored in the Microsoft Windows registry. In that case, the value for the collection name in the Awingu label should also be truncated to 15 characters in order to match the collection name in the Microsoft Windows registry.
3. Session Collection names containing spaces
If the Session Collection name contains spaces, those spaces will be automatically converted to underscores. So, the actual Session Collection name that is stored in the Microsoft Windows registry will contain underscores. Please make sure that the value for the Session Collection name in the Awingu label also contains underscores instead of spaces.
4. Dots will be removed
When creating a Session Collection name with dots in it, these dots will be removed. So 'Session.Col' will become 'SessionCol'
Was this article helpful?
Tell us how we can improve it.