Devolution RDP: Understanding Connection Options

When it comes to using Remote Desktop Protocol (RDP) with Network Layer Authentication (NLA), there are certain requirements that need to be met in order for a successful connection. One of these requirements is to use a username that contains the login pattern configured by your administrator under the PSMLoginPattern parameter.

For those who want to connect through the Point and Print Service (PSM) without providing target system details, it's possible to configure a Connection Manager to do so. On the other hand, you can also configure a Connection Manager that includes the target system details in advance.

It's important to note that connections made from an RDP client application are Remote Desktop connections, and not RemoteApp connections. This means that if your request to use the account is approved, you will be able to connect to this account using an RDP client application.

However, there are some limitations when it comes to initiating connections that require additional information from the user when the connection is established (user parameters). These types of connections cannot be initiated using an RDP client application. Additionally, qualitative control and ticketing integration are not supported in Devolution RDP.

When it comes to drives redirection settings, these settings are enforced only for the PSM-RDP connection component. This means that if you connect through PSM without providing target system details and select a connection component (other than PSM-RDP) with those settings enforced, you will not be able to connect using that connection component.

Finally, it's worth noting that settings for drives, printers, and clipboard redirection specified in the connection component level are enforced, while platform level configurations are ignored. By understanding these connection options and requirements, you can ensure a seamless experience when using Devolution RDP.

Devolution rdp