Both Remote Desktop application types (Predefined and User Defined) do not require import of TSPUB file. All necessary RDP parameters are automatically generated by the Microsoft Forefront UAG Terminal Services RDP Data service.
Publishing a Remote Desktop, UAG Management Console reads an RDP parameters template file at the moment a new Remote Desktop application is added to the portal. All parameters specified in this file will be added to the RDP data the UAG automatically generates for particular Remote Desktop application unless these parameters are controlled in the RDP data generation. Such parameters will be always overwritten whatever their customization is.
The template file is not reread in the moment of RDP data generation, configuration activation or whatsoever. Its content is read at the moment the application is added to the portal, and its content in this very moment is stored internally within the UAG application data. Thus the template can be modified before addition of each new Remote Desktop application, and these applications will use different sets of additional RDP parameters. Unfortunately, this set cannot be edited or reviewed later. Therefore a Remote Desktop application should be removed and added again if modification of the customized RDP parameters is necessary (the new template file will be read upon application addition).
The default RDP data template file is located as
It is a plain ASCII text file expected to hold RDP parameters in the same way RDP files do this. Currently, the default template file contains a single parameter for illustrative purposes only (it has no actual effect since it is always overwritten during RDP data generation). It is urgently recommended not to modify this file directly but create a custom file according to the current UAG conventions:
The template’s file content is validated for being a syntactically correct RDP file but RDP parameters themselves are not validated for existence, correctness of values, etc.