Forwarding

<< Click to display Table of Contents >>

Navigation:  Virtualization & Terminalserver >

Forwarding

The Forwarding function is an additional feature for the Infoclients, which enables to redirect the display of Infos that are sent as Dynamic Channels. In case an Infoclient receives a Dynamic Channel and the Dynamic Channel initiates the display of the Info, then this Info is forwarded, not the Dynamic Channel itself.

 

Primary field of application for this function are Infoclients on Virtual Environments. When using this function, Infos that would be displayed by the Infoclient in a Virtual Environment can be forwarded for display to any other Infoclient. Additionally, the Infoclient in the Virtual Environment can be configured to be in Passive Mode, meaning that it won't display any Infos, but will forward Infos from Dynamic Channels in case forwarding is set.

 

The configuration of where to forward the Infos to is set in the item ForwardingInfosTo= in the Infoclient.ini configuration file. There are three possibilities for defining the recipient of the forwarded Info:

 

These configurations can be made via the app Configuration (Clients -> Configuration).

 

 

1.Forward to Quickuser
Define individual Quickuser to whom you want to forward the Info.
 


ForwardingInfosTo=user1;computer1;ip address1,user2;computer2;ip address2

 
It is also possible to include the domain.

 


ForwardingInfosTo=domain1;user1;computer1;ip address1,user2;computer2;ip address2

 

2.Forward to filter
Alternatively, you can specify a listing multiple filters. Please note the exact upper and lower case.

 


ForwardingInfosTo=filtername1,filtername2

 

3.Combination
It is also possible to combine both variants as desired.

 


ForwardingInfosTo=user1;computer1;ip address1,domain2;user2;computer2;ip address2,filtername1,filtername2

 

Instead of the "ForwardingInfosTo" configuration on the Infoclient, a filter, group or grouping of the type Forwarding, can also be selected directly when addressing an Info.

If you also select Forwarding-Filter-Group-GroupGroups when creating the Info, it will even without ForwardingInfosTo on the Infoclient, Dyn-channels be sent to them.

 

Forward Infos to Quickuser

 

If the forwarding is addressed to a Quickuser, the Info will be forwarded to any Infoclient that matches the Quickuser definition.

In the Quickuser syntax, it is possible to use specific wildcards for the identification of users in Virtual Environments:

 

Wildcard

Description

sessionusername

This wildcard addresses the users on the remote host which has opened the session in the Virtual Environment. In most cases, this is the logon username on the remote computer.

sessioncomputername

This wildcard is addresses the computername of the remote host, from which the remote session was opened.

username

This wildcard addresses the name of the user in the session. This name may differ from the sessionusername.

computername

This is the local name of the computer, on which the session runs, e.g. the computername of the Terminal/Cloudserver.

 

Of course the wildcards * and ? can be used as well

 

hmtoggle_arrow1Example:

 

Forward Info to a filter

 

Only Infoserver filters with the Forwarding filter type can be used. Any info client that receives a Dynamic Channel will forward the Info to the specified filter.

 

hmtoggle_arrow1Example:

 

Setting The Infoclient to passive mode

 

The passive mode is activated by setting the item Passive=true in the Infoserver.ini configuration file. When the passive mode is active, the Infoclient won't display any Infos, yet it will forward Infos activated by Dynamic Channels. Also, Infoclients in passive mode do not draw a CAL (client access licence).

 

Additional Wildcards for the Infotext

 

When sending Infos to any Infoclient in a remote session, following wildcards can be used in the Infotext:

 

Wildcard

Description

%sessionusername%

Name of the user that started the remote session

%sessioncomputername%

Name of the computer from which the remote session was opened

%sessionaddress%

ip address of the computer from which the remote session was opened

%sessionapplicationname%

Name of the application running in the session (works only in Virtual Application sessions)

%sessioninitialprogram%

Commandline that initiated the application running in the session (works only in Virtual Application sessions)