VHD CMS Enterprise™
Welcome to your Green, Quiet and Cool Diskless Office!VHD CMS Enterprise™ is a dramatic leap forward in diskless technology, bringing virtual hard disk technology to the workplace. Delivery of virtual hard disks is determined by authentication of the user — not by which physical computer is being used. Centralized client hard storage and delivery of personalized hard disk for each user means centralized management whilst delivering an uncompromised PC user experience.
Overview
VHD CMS Enterprise™ uses Account-Based Management to deliver an individual Menu to each user with their personalized Virtual Hard Disks. The user is authenticated by the system login and dynamically delivered his/her individual Menu — regardless of which physical client computer is used. The Menu contains Menu Items linking to the user’s personalized vhds. In addition, VHD CMS Enterprise™ authentication mechanism is fully compatible with Microsoft Active Directory service, meaning that the deployment of virtual hard disk solution is seamless and transparent to enterprise.
What is Account-Based Management?
For your understanding, we use the following architecture diagram as an example. There are three users with accounts on the system. There are three computers which can be used by any one of the users. There is an Authorized Login to the system so that the VHD Server can determine who the user is, and send them their personalized Menu. The VHD Server stores a database of User Accounts with their individual Menus and Menu Items. There are several virtual hard disks: two for OSs and three personalized vhds.
Here Bill and Michael’s Menu Items might share vhds such as ones containing OSs (e.g. 1.vhd — XP) but other vhds will be unique to each user (3.vhd 3 Bill; 4.vhd — Michael) When two users stream from the same vhd simultaneously (e.g. both use 1.vhd) they have two separate write caches. These write caches exist while the session exists and disappear when the user logs off. This write cache is volatile and is not written back to the vhd which is set to Persistent Storage. When the users access their personalized vhds (i.e. 3.vhd, 4.vhd, 5.vhd) then the write cache is persistent, and is written back to the original vhd.
All the client computers have no local-disks so all appear identical to the users. This means that Bill for example could login to the system using any computer and will be delivered his personal Menu.
Benefits
- Personalized Virtual Hard Disks
- Authorized Access
- Business Continuity
- Centralization
All users have personalized virtual hard disks that are only accessible by the specific user. These virtual hard disk for all users are store —and secured— centrally by the VHD server.
Access to the entire system (from a pre-OS environment) is controlled centrally — protecting your company's information and users' private data.
VHD uses Concurrent Pack this ensures non-stop access to the virtual hard drives in the case of I/O Server failure.
VHD separates the DCHP server from it's VHD Server so that multiple LANs can be centralized and provisioned from a single location.
Features
- Microsoft Active Directory Support
- Router Crossing Ability
- Business Continuity
- System Snapshots
- Data Snapshots
VHD software fully integrates with Microsoft Active Directory. Our client computers all appear unique – but are really streamed from a single image. A login-prompt is used to authorize user access to the system.
No longer is your diskless server restricted to a single LAN environment. VHD server can stream to client computers from any location. An organization can connect two LAN environments to a single VHD server – for improved centralized management.
Each LAN simply requires a generic DHCP server – and our VHD server can be located either locally or remotely – even across the internet!
Using Concurrent Pack implementation each client computer is serviced by several I/O servers simultaneous. In the case of a single I/O server failure, the remaining I/O servers continue to stream; ensuring business continuity – no rebooting required.
Take “Snapshots” of the current system data configuration which can be rolled back to at any time in the case of problems.
Take “Snapshots” of the current user’s data – these can be viewed by the IT administration and rolled back.
More: How to Buy | Full Benefits and Features



