Netman Desktop Manager

The new NDM Session Broker distributes incoming sessions over existing terminal servers in accordance with your configurations. NDM Session Broker can process all connections, whether the request comes from the NetMan Client, the web front end or an alternative RDP client. You get intelligent load balancing for all your clients, even those not using the NetMan Desktop or your web interface to access NDM. In particular for thin clients that connect over the MS RDP client or an alternative RDP client, this new feature improves performance and server utilization considerably.

The new Session Broker in NDM 4.5 not only handles the distribution of incoming sessions, it also serves as a session directory. If a session is interrupted, Session Broker ensures that the user is automatically reconnected to the still-open session. Thus if the connection to the server is cut, for example due to a network problem, users can pick up right where they had left off as soon as the connection is reestablished. This feature is compatible with Windows Server 2003 Standard and later.

With NDM 4.5, you can define permissions and other user controls based on Active Directory OUs rather than your NetMan user accounts. This simplifies and speeds up rollout of individual application groups, especially in existing systems that already use AD.

The latest version of the web interface features an optimized display and expanded functionality.

• Easy switching between open TS applications
  When the Java client is running, all active TS applications are listed within the web interface window. A single mouse click is all it takes to jump to the desired application.
• Optional user selection of launch method (NetMan web client, JAVA client, rdesktop)
  NDM 4.5 can let the user decide which launch method is used in the web interface. The default method is configured in the server. If necessary—for example, if the user does not have sufficient rights to install the NetMan Client—the user can select an alternative method prior to login.
• No separate connection window
  Thanks to continuous development of the applet, the connection window that was opened by the Java client is no longer needed. The information it contained is now displayed within the web interface window.

Before launching an application, NDM 4.5 can check whether it is installed locally and, if it is, can use the local instance rather than starting an application session. This helps prevent double-licensing and profile conflicts for mobile network users who have the applications installed on their laptops.

NDM 4.5 supports notification area messages from server-based applications, and displays them in the client taskbar. Classic examples include the Envelope icon that Microsoft Outlook shows when new e-mail is detected, and the display of caller ID by certain CTI applications.

NetMan Desktop Manager 4.5 includes native support for all features in MS RDP. Installation of the corresponding RDP client on the client operating system (Windows XP, Windows Vista, Windows 7) is required. This enables full exploitation of next-generation protocols.