All about application delivery

In Med-V you can define an IIS based image repository server.  A client checks if the image on the central place changed and if yes it downloads the changes vie trimtransfer. This means, that only differences to the image are downloaded and trimtransfer will also check on block level if certain blocks are already on the target machine – this saves a lot of bandwidth.

But what will happen if the user on the virtual machine that is updated will for example change somehting in an application? This will be normally stored in his profile on the virtual machine. Or if the user accidentially saves a file to the virtual hard disk. The data would be gone! Med-V will reset the local image to its default. So if you want to use a central image management solution you have to care, that no living data is on the virtual Windows XP.  You need for example a roaming profile for the virtual machine – well better use FlexProfiles I would say but this is another story.