This article describes the steps on how to fix the incorrect disk size issue on the Licensing page under the Sophos iView UI. The following sections are covered:
Applies to the following Sophos products and versions Sophos iView
Default iView image or VHD file has been installed on a Hyper-V platform.
A customer may report an issue after the installation of iView that the disk size is not reflecting correctly under the licensing page on the iView web admin. However, License Size (1 TB or 4 TB or 8 TB based on purchase license) is reflecting with correct value.
System settings > Maintenance > Licensing - It shows that the Disk Size is reflecting incorrectly or 490.05 GB.
If you will check from the CLI, it will also give the same value (.i.e the incorrect disk size)
# df -kh Filesystem Size Used Available Use% Mounted on rootfs 901.5M 546.5M 354.9M 61% / /dev/root 901.5M 546.5M 354.9M 61% / none 2.9G 0 2.9G 0% /dev none 2.9G 100.0K 2.9G 0% /tmp none 2.9G 4.0K 2.9G 0% /dev/shm /dev/conf 975.9M 137.5M 822.4M 14% /conf /dev/var 490.0G 20.2G 469.8G 4% /var
License do not set disk size in the VM. License will only give the correct Licensed Storage Capacity under Device Registration Details on the Licensing page.
If a customer is using the default iView image for the various virtualization platform, then the auxiliary disk comes with a default 500 GB (soft) VHD file.
To fix the above issue and to reflect the correct disk size, the customer needs to perform a Hyper-V disk resizing. Disk resizing can be done based on the installation disk drive size along with the license capacity of iView. Please follow the article below for disk resizing:
Sophos iView: How to expand iView hard disk size
Once done, for example based on the scenario described above, disk size has been set or increased to 1 TB based on the available disk size. After updating the value and running the VM again on Hyper-V, iView UI will show the following details:
Sign up to the Sophos Support SMS Notification Service to get the latest product release information and critical issues.
If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article. This is invaluable to us to ensure that we continually strive to give our customers the best information possible.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.