Hi,
Some background: We have applications that are available as a published application. However, these can also be launched directly when the user has a desktop connection to a server in the host pool. Sometimes this leads to a scenario where a user has two sessions on the same server, a desktop session and a published application session.
So the idea is that the Parallels Client on the RD server can detect if the launched application will start in its own Host Pool and if so, it will start it as a "Local Device" application without the Parallels overhead. If not, it will start a regular RemoteApp/Published Application session.
I would call this a hybrid application because it can be both, a "local desktop" application or a published application.
Some background: We have applications that are available as a published application. However, these can also be launched directly when the user has a desktop connection to a server in the host pool. Sometimes this leads to a scenario where a user has two sessions on the same server, a desktop session and a published application session.
So the idea is that the Parallels Client on the RD server can detect if the launched application will start in its own Host Pool and if so, it will start it as a "Local Device" application without the Parallels overhead. If not, it will start a regular RemoteApp/Published Application session.
I would call this a hybrid application because it can be both, a "local desktop" application or a published application.