NoTouch Center : Backup and Restore

NoTouch Center : Backup and Restore


  • Access VA-admin console by clicking on "VIRTUAL APPLIANCE ADMINISTRATION" link appearing on the login page. Provide credential and login.
  • Click on BACKUP icon appearing at the top-right corner of the page.

  • Click on "Retrieve Backup" link to get backup  of NoTouch Center.

  • You can use "Restore prior backup" link on the same page to restore backup that was previously taken.
                        

Select backup file to upload and reboot NoTouch Center Virtual Appliance.






    • Related Articles

    • VERDE Backup and Restore Procedures

      Product Line:  VERDE ISSUE:  What are the steps for backing up and restoring the VERDE environment?   SOLUTION: Our recommendation is to not back up the VERDE OS (for Bare Metal installs) or the Linux OS.  Rather, one should backup key directories ...

    • LDAP Authentication (NoTouch Center)

      LDAP Authentication (NoTouch Center) NoTouch Center is a tool for system administrators to manage their endpoints. It not only maintains a list of local user accounts, but it also supports user authentication via LDAP using either Microsoft Active ...

    • NoTouch Center Appliance Install on a HyperV VM

      This article is for anyone wanting to install the NComputing NoTouch Center Appliance specifically on Microsoft HyperV 2016 Currently there are not screen shots but I will make sure and be descriptive and will reference relevant links mentioned.  ...

    • vSpace Pro registry backup file

      Windows 10 Spring Creators Update (version 1803) In the most recent Windows 10 Spring Creators Update (version 1803), if you already had vSpace Pro 11 installed, This Windows update may remove some important registry keys which will make vSpace Pro ...

    • How to RESTORE VERDE Images/User Data When Deployment is via STATIC in the Desktop Policies

      Product Line:  VERDE STATIC deployment method is not typically used, but, if there is a need, you may at some time need to recover from a server crash, a user image corruption, etc. Refer to the following.  You ARE dependent upon regular, scheduled ...