• A web based management tool that makes it possible to manage all thin clients, whether they are PCs converted to thin clients or specialized thin clients, in the network -- from anywhere in the network. Multiframe manages:
  a. which terminal servers the client devices can access, and
  b. local and network hardware peripherals the devices can connect to.
• Thin client distributions according to the customer's needs.
• A method to deploy new thin clients in minutes and to reconfigure existing clients in seconds.
• Fast, optimized, stable and secure thin client distributions that run on even modest hardware with low specifications.
• The thin client distributions have built-in unique features that meet many hard-to-handle security measures.

What does Multiframe distribute to the devices?
Multiframe distributes a thin client software image. This image contains a small and very efficient tailor-made operating system that runs on the client device. The Multiframe thin client can run entirely in memory and as such does not necessarily need to be installed locally on the hard disk.

The Multframe thin client eliminates the need to locally install, maintain, upgrade, or update third party operating systems, thin client programs, internet browsers, terminal emulators and applications for desktop security and management.

Does "thin client" really mean that there is no software on the client device?
It is correct that there is NO need to install and maintain:

• a local operating system from a third party such as Windows, Unix or Linux;
• any type of terminal emulation software, thin client software or web browser on the client device;
• any type of security, control or management application on the client device.

However, it is true that the Multiframe thin client is a separate operating system that runs on the client device. Any thin client needs an operating system and terminal server connectors, the Multiframe thin clients being no exception. In the case of MultiFrame, however, any and all distribution, installation and upgrading of the thin client operating system is handled automatically.

• ICA protocol is used to connect to Citrix Multiframe running on the MS Windows Terminal Server Edition.
• Remote Desktop Protocol (RDP) is Microsoft's connection protocol to their Windows 2000 and 2003 Terminal Server Editions.
• X11 protocol is used to connect to UNIX/Linux terminal servers. Multiframe also supports the NX protocol, which is based on the X11 protocol and provides compression and encryption that improves response times performance by up to 20 times.
• IBM 3270 terminal emulation protocol is usually used to connect to IBM or IBM compatible mainframes.
• IBM 5250 terminal emulation protocol is usually used to connect to IBM AS/400 series.
• Secure Shell (SSH) is used to connect safely to servers at command shell. SSH is the safe encrypted version of Telnet. SSH and SSL are encryption technologies used in most Internet money transfer applications.
• WWW is a local web browser, which uses the Mozilla Firefox, that can be used directly for web applications.
• VNC protocol is normally used by IT Staff to remotely "take over an end-user's desktop" to guide him/her through the applications or to test application problems.

What kind of compuing devices does Multiframe control?

The purpose of Multiframe is to improve the management of fixed network connected devices by eliminating the need to install, maintain and administer any kind of local software on the client device. Devices such as laptops or PDAs that are not connected permanently to a network and need local applications and data in order to work off-line are not suitable for management by Multiframe. Also permanently connected devices that must have, for technical reasons, local software installed are not appropriate for management by Multiframe.

How does Multiframe know which computer devices to control?

MultiFrame detects automatically all network attached devices that use Pre Boot Execution Environment (PXE) when these network connected devices boot up on the network. Most PCs or PC-compatible devices from about 1998 until today have support for PXE. In case of incompatibility we advise customers to use the Intel or 3COM PXE Managed Cards.
The MultiFrame will not by default control any devices. The administrator has to select which devices the MultiFrame will control. The MultiFrame can be set to automatically control all devices, but we do not recommend this to be changed as the default option as there are normally some devices that will not require management by MultiFrame or are not suitable for control by MultiFrame.

What is the method of identification is used by MSS to determine which devices it is to control and does it maintain an inventory?

The identification is done through the unique identifier in the device\u2019s MAC Address. In addition Multiframe reads out automatically all client device information and stores it in its database. It creates an inventory of the following information:
Current IP Address, which changes all the time when using DHCP,
Hardware vendor information,
What devices are on the PCI buses,
RAM size,
Disks (vendor, type and size),
USB ports,
LPT and COM ports.
All devices can be edited as names following customer's own naming convention. Multiframe obtains all this information automatically which is logged into the Multiframe database as a hardware inventory.

How are the Thin Client profiles created with Multiframe?

The system for handling the Thin Client profiles is built into the Multiframe Management Software. The system is designed for maximum flexibility and should fit most network environments.
The minimum client profile fits into a 32MB storage space (flash memory or disk) and is highly optimised so it needs only 32MB RAM to run.
The profiles are generic and cover all types of PC compatible devices and many standardized dedicated thin clients. This generic profile covers most terminal servers, a web browser (Firefox) and some other features, for instance Secure Shell (SSH).
The Multiframe Thin Client profiles are built based on a read-only file system that prevents the user to store data locally and prevents viruses on the Thin Client.
There may be more than one client profile. The profiles will be loaded to the client devices according to what the system administrator has decided for the Thin Clients from the web interface in the MultiFrame. In this way it is possible to optimise profiles for different hardware and/or the right features that the individual user needs.
In addition, each profile can be configured with different features adjusted to the user's needs.

How does Multiframe fit into a distributed environment?

Multiframe has built-in features making it possible to structure large hierarchical networks and through the unique \u201cFan Out Distribution System\u201d, pushing out \u201cMultiProxies\u201d, that serve as local units for profile delivery to local clients. This system eliminates problems with low bandwidth or \u201cerror prone\u201d networks and allows for high scalability.
Large enterprises with multiple sites can deploy Multiframe in a distributed environment using the MultiFrame proxies. The proxies are distributed to remote network segments and the central Multiframe server will manage the proxies. Only the user profiles that are needed at each segment of the network are sent to the Multiframe proxy; so that, the proxies can locally control and update their Thin Client managed devices and in doing so reduce the communication burden on the wide area network.

Can you exchange start-up logo and also switch between different logos?

Only one logo can be used and has to be produced and implemented by us.

Does Multiframe support native graphics drivers on the thin clients and PCs?

Yes, the Multiframe supports all kinds of native graphics drivers on the thin clients and PCs. This is important to achieve an optimal performance of the hardware with great benefits for the end user. The speed benefit of using a native graphics driver can in some instances be in a factor of 1:2.

Will all PXE-enabled equipment be automatically detected by Multiframe when they boot up on the network?

Yes, all devices with PXE enabled and set up with network as primary boot will be automatically detected when the device is turned on or rebooted.

How can Multiframe co-exist with other PXE-based systems?

Many or most deployment solutions use PXE as deployment method. When using more than one PXE based system at the same time, there may be conflicts. There are several ways to solve this. Multiframe will do all the work concerning thin clients, so there are no need for using other deployment solutions for thin clients. When a customer also is in need to use deployment solutions for fat clients, as for example Microsoft Remote Installation Services (RIS) or Novell Zenworks, you can work it out by using for instance pre-staging in Microsoft Active Directory or similar. Another method is using scripting to make integration possible. There are unfortunately no general \u201cbest solution\u201d to this question, because it all depends on how the network is setup and maintained. Some hints are given in the Multiframe Administration Manual.

Is there a possibility to use computers without PXE based network cards?

Yes. We can provide you with a bootable CD-disc with a preinstalled ip-address to the Multiframe server that contain all components normally transmitted over PXE/TFTP.

How is the system backed up and how is it possible to monitor settings?

All configurations are stored in the database on the server. For back up purposes it is enough to take a back up of the postgres-database on the Multiframe server. This can be integrated with the existing backup solution in use.

What are the routines for software updates? How do we get the latest edition?

All customers with Maintenance and Support Agreement will receive the latest edition on CD-ROM or a download from the Multiframe website.

To be able to remotely control a session, you choose Frame and Activate. What happens next? Will a window appear at the client or is an external tool needed?

A window will appear that informs that vnc-connections to the thin client now are available. You need to start the vnc-viewer on your own to get the screen window on the user side.

How many MultiProxies are needed for my network?

In many or most cases, there is no need for MultiProxies at all. The need for multi-proxies applies only for very large global networks with several thousands of thin clients deployed in remote locations or for satelite offices with low capacity or constraints. A complete thin client system image including operating system and connection protocols is approx. 12 MB in compressed mode and is only needed to be distributed when for example upgrading of new software versions, not for normal day-to-day usage.

Some of your clients using Multiframe claim that they upgrade their complete workstation environment in just a couple of minutes? What is upgraded, software, configuration?

One of our clients upgraded 280 workstations in just four minutes. The complete software was upgraded on all the thin clients. The procedure is \u201cBoot-Installation-Configuration-Reboot-Login Screen for User\u201d, and then all is done! The network administrator only needed to change to a new version in the web interface and click on the \u201cInstall Now\u201d button for the new installation. Wait four minutes\u2026. and all workstations were upgraded!
Software configurations may be done at any time for a single, a group or all of the workstations - and requires no reboot. The whole operation is done in a matter of seconds.

Licensing- What about the Microsoft CAL licenses? Do I still need to have them?

To connect to Microsoft Terminal Servers you need to follow the Microsoft Licensing rules that implies use of CAL licenses. To connect to terminal servers not based on Microsoft you do not need them.

Will the existing operative system on the workstations be erased and replaced by Multiframe?

Yes. Multiframe erases the disk totally before a new Multiframe image is installed.

How will Multiframe synchronize with for example my Palm and other handheld devices, both with and without Microsoft Office?

This is handled the same way as with other devices as PCs. It can be done with both Microsoft and Linux/UNIX based terminal servers.

What hardware is needed for the installation of MMS?

The Multiframe Server Software can be installed on almost any server hardware (minimum Pentium 2, 200 MHz CPU, 128 MB RAM) and includes the complete software needed, including the operating system.

How does MultiFrame differ from for example a thin client with Windows and ICA?

Multiframe is using an extremely fast and optimized Linux based image on the thin clients. So what you get is the fastest and most responsive thin clients in the market. Even when converting old PCs to Multiframe thin clients it is possible to achieve performance that equals most dedicated thin clients.

How do we handle thin clients in multiple networks?

Multiframe has built-in functions to easily map and setup multiple networks that can be handled from one Multiframe central server in an enterprise. When properly setup is done, all thin clients will be managed from this only spot.