Fortinet Document Library

Version:


Table of Contents

2.5.0
Download PDF
Copy Link

Customized Image Cannot Finish Cloning

Find out root cause:
  1. Login as admin. Only the admin account can do this.
  2. Go to Virtual Machine > VM Images and change all other VM types' clone # to 0, and the failed one (customized image) to 1.
  3. Click Apply. This triggers the cloning.
  4. Click the VM Screenshot button on this page. In the dialog box, keep clicking the VM Screenshot button of the failed VM.
  5. Then click the PNG Link image icon to show the screenshot. The image tells you why the clone failed.
Typical reasons for the failure:
  1. Customized image is too big that system does not have enough memory. In 2.5.0 and up, a warning message displays and block the large clone number.
  • Reduce its size with Windows Disk Defragmentation tool.
  • Reduce clone number. Try 1 first.
  • Send it to Fortinet Support for assistance.
  • The customized image is not activated.
  • You did not create a correct tracer hookup.
  • You have a non-English edition, such as Japanese, or non-supported edition, such as Windows Server 2003 64bit, so tracer fails to install.
  • Customized Image Cannot Finish Cloning

    Find out root cause:
    1. Login as admin. Only the admin account can do this.
    2. Go to Virtual Machine > VM Images and change all other VM types' clone # to 0, and the failed one (customized image) to 1.
    3. Click Apply. This triggers the cloning.
    4. Click the VM Screenshot button on this page. In the dialog box, keep clicking the VM Screenshot button of the failed VM.
    5. Then click the PNG Link image icon to show the screenshot. The image tells you why the clone failed.
    Typical reasons for the failure:
    1. Customized image is too big that system does not have enough memory. In 2.5.0 and up, a warning message displays and block the large clone number.
    • Reduce its size with Windows Disk Defragmentation tool.
    • Reduce clone number. Try 1 first.
    • Send it to Fortinet Support for assistance.
  • The customized image is not activated.
  • You did not create a correct tracer hookup.
  • You have a non-English edition, such as Japanese, or non-supported edition, such as Windows Server 2003 64bit, so tracer fails to install.