Browse Prior Art Database

Thin Client Chassis virtualization

IP.com Disclosure Number: IPCOM000032195D
Original Publication Date: 2004-Oct-26
Included in the Prior Art Database: 2004-Oct-26
Document File: 1 page(s) / 29K

Publishing Venue

IBM

Abstract

Today when a personal computer connects to a server it is managed as a client attached to a server by popular client management software such as IBM Director, or Microsoft SMS. With a desktop blade environment the "Desktop" is separated in to two parts. the blade stored in the datacenter and a client terminal at the users desk. The management solutions available today treat this as two parts. This article describes a method to virtualize the two parts to present a whole desktop perspective to the server management tools. The advantage is you don't have to have to rewrite or create additional classes of devices for existing distributed client management tools.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Thin Client Chassis virtualization

We create a dedicated VLAN subnet between the desktop Blade chassis's and the client's desk-side device. This allows the deskside device to send critical information to the desktop blade and allows for merge of the deskside blade and deskside device critical data into a single device class completely compatible with existing clients thereby working with existing client management software tools without change. Critical data can include inventory information, health of device, software load, etc.

When the user connects with a deskside device, it becomes part of the blade center management module matrix. We create a dedicated VLAN between the desktop blade and the deskside device. VLAN allows the two parts to broadcast to each other even if they are on separate physical LAN's and most important without burdening other clients on different VLAN from having to sniff data packets. It's also possible that like clients with similar attributes can be grouped on the same VLAN. At this point the device can be managed like it is part of a blade. The thin client would take it's management data (inventory information, health of device, software load, etc.) and package it up to send a VLAN packet to allow the thin client to be merged with the desktop blade profile thereby emulating a traditional desktop from a server client management viewpoint..

1