Browse Prior Art Database

Data Image Merger

IP.com Disclosure Number: IPCOM000031321D
Original Publication Date: 2004-Sep-21
Included in the Prior Art Database: 2004-Sep-21
Document File: 1 page(s) / 21K

Publishing Venue

IBM

Abstract

Method to allow a common image for a multitude of common desktop blades thereby savings significant storage space (only one copy vs. multiplies) and significantly reducing patch management as only one copy of the image needs to be updated. Each users unique delta's are merged with the common image on logon, thereby creating an unique image per user off the common image. At log-off the user image is broken apart to capture the new unique settings and data for the next logon.

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

Page 1 of 1

Data Image Merger

    Today when a user logs into a desktop blade there is a unique separate image for each user. This image contains a copy of the OS which is mostly common for all users. This poses the following problems:

    1) Significant effort required when the IT admin needs to roll out updates as they have to be applied to each user image.

    2) Each user requires a large amount of storage even thought all user images are mostly the same

    3) Limits the H/W range of the blades since the OS is configured for a given hardware platform.

Our solution de-constructs the image into several parts.
1) Common OS components (unique for each blade H/W configuration)
2) User unique OS settings may include Registry entries, default settings, policy configuration,...

     3) User data. User data always stored in common sub directory (my documents) The blade storage farm has a unique common OS component image for each H/W configuration. The user logs on and is assigned a blade. The OS common image for that blade hardware configuration is copied from the storage farm into the user working image. Than the user unique OS settings are inserted on top of the common OS in the user working area image. The last step is to copy and overlay the user data files from the storage farm into the user working image.

The user now has a working user unique image.

     On log-off the process is inversely repeated. The user unique settings are saved. This can be accomplished by using the OS's built in system snapsh...