Overview

After the Kerio Control reinstall, you are experiencing an issue with re-registering a previously registered Kerio Control appliance in the GFI App Manager. The App Manager behaves as if the appliance is already registered, only showing the main menu and not proceeding with the registration process.

Solution

If Kerio Control is already registered and you want to reinstall it, you will need to remove (delete) the old Kerio Control (no more in use) from the AppManager.

To re-register a Kerio Control appliance with GFI AppManager after reinstalling it:

1. Delete) the old Kerio Control entry from the AppManager.
2. Reinstall the Kerio Control appliance.
3. Add the newly installed Kerio Control to AppManager.

If you face any issues during this process, follow the steps in Resetting KerioControl’s connection to GFI AppManager article to reset the connection between Kerio Control and GFI AppManager.

Summary

When reinstalling Kerio Control, first ensure to delete the old Kerio Control entry from AppManager. After deletion, reinstall the Kerio Control appliance and then add it to the AppManager again. If problems with the registration persist, refer to the article on Resetting KerioControl’s connection to GFI AppManager.

FAQ

1. How do I re-register my Kerio Control appliance in the GFI AppManager after a reinstallation?
   To re-register, first delete the previous entry of Kerio Control from the GFI AppManager. Then, reinstall the Kerio Control appliance and add it back to the AppManager.
2. What should I do if my re-registration of Kerio Control is not proceeding as expected?
   If re-registration fails, you may need to reset the connection between Kerio Control and GFI AppManager. Follow the guidance provided in the article on Resetting KerioControl’s connection to GFI AppManager.
3. Why does GFI AppManager not allow me to re-register my Kerio Control appliance after reinstalling?
   This issue typically occurs because the AppManager still has the old registration. Removing the previous Kerio Control entry from the AppManager should resolve this problem.