Installing Image Manager Components32 Image Manager Server ConfigurationImage Manager Server ConfigurationDisk StorageRequired on ServerThe Image Manager server must have a partition containing enoughfree space to contain all the virtual hard disks required by clients. Avirtual hard disk consists of a hard disk image file plus a CVol (Cli-ent Volume OverLay) write cache file that will contain all data writ-ten by the clients. The contents of the CVol files can be retained ordeleted when the clients reboot. The hard disk image will be the sizeof the client partition from which the image was created.The amount of disk storage needed on the Image Manager server forvirtual hard disks is dependent on the mode of operation.If the clients are using a shared image in Volatile mode, WindowsXP Pro and Office 2000 can utilize less than 2 GB. Let us assumethat the image size is 2 GB. Every CVol file would use 512 MBmaximum and they are deleted at each reboot.If the user is using their own unique virtual hard disk image inNormal mode, then the CVol files will grow in size. As theWindows file system works so that every sector will be written oneventually, the worst case would be 2 GB for the hard disk imageand 2 GB per client. If every sector was rewritten, the CVol filescould take up to the virtual hard disk image size. The average casewould be when the virtual HD image is updated regularly (once perquarter). This would be approximately 2 GB for the HD and 800 MBper client. Some Windows settings, such as virtual memory settings,have an impact on the size of CVol files.File Locations onthe ServerThe following procedure assumes you have already installed theServer components of the Neoware Image Manager using theInstallShield Wizard described earlier.1 Navigate to the directory on the server containing the installedNeoware Image Manager software.If you performed a Server or Server with Console installation,the default directory is:
