MetaFrame and NT Thin-Client Technology

Take a look at why MetaFrame 1.0 isn't the end of the Independent Computing Architecture story.

Christa Anderson

April 30, 1999

1 Min Read
ITPro Today logo in a gray background | ITPro Today

MetaFrame 1.0 isn't the end of the Independent Computing Architecture (ICA) story. In late February 1999, Citrix released MetaFrame 1.8, which adds new features to make the thin-client experience as transparent to the end user as possible. MetaFrame's new features aren't tied to a particular version of NT technology, so you can add MetaFrame 1.8 to either Windows 2000 (Win2K) or Windows NT 4.0, Terminal Server Edition.

First among the changes to MetaFrame is the addition of Program Neighborhood, which lets administrators push access to new or updated applications to the user (currently, users must update or access applications). Extended Enterprise Management is an enhancement that lets server farms cross subnet boundaries, thus putting a larger portion of an enterprise network into one server farm. Along similar lines, the Business Recovery Client directs clients to a backup terminal server in case the main server fails. Even if your network isn't big enough to need high-end management tools, MetaFrame 1.8's improved caching algorithm, which can reduce bandwidth consumption by as much as 30 percent, can improve your network's efficiency. Support for some Linux clients and SCO UNIX is now available. MetaFrame isn't necessary for every network that needs multiuser support, but if you're looking for this kind of support, you'll be glad to know that the improvements to Terminal Server don't render MetaFrame redundant.

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like