Please enter search query.
 
              Search <book_title>...
            
 
          Veritas Flex Appliance Getting Started and Administration Guide
                Last Published: 
				2021-03-05
                
              
              
                Product(s): 
				Appliances (2.0)
                 
              
              
                Platform: Flex Appliance OS
              
            - Product overview
- Getting started
- Managing network settings
- Managing users- Overview of the Flex Appliance default users
- Changing the password policy
- Managing Flex Appliance Console users and tenants- Adding a tenant
- Editing a tenant
- Removing a tenant
- Adding a local user to the Flex Appliance Console
- Connecting an Active Directory domain to the Flex Appliance Console
- Importing an Active Directory user or user group to the Flex Appliance Console
- Editing an Active Directory domain in the Flex Appliance Console
- Changing a user password in the Flex Appliance Console
- Expiring a user password in the Flex Appliance Console
- Removing a user from the Flex Appliance Console
 
- Changing the hostadmin user password in the Flex Appliance Shell
- Changing the sysadmin user password in the Veritas Remote Management Interface
 
- Using Flex Appliance- Managing the repository
- Creating application instances
- Managing application instances from Flex Appliance and NetBackup
- Managing application instances from Flex Appliance
- Upgrading application instances
- About Flex Appliance upgrades and updates
 
- Appliance security
- Monitoring the appliance
- Reconfiguring the appliance
- Troubleshooting guidelines
Supported upgrade paths to this release
The following describes the supported direct upgrade paths and two-step upgrade paths for Flex Appliance version 2.0:
- Direct upgrade path - You can upgrade directly from version 1.2, 1.3, or 1.3.1 to version 2.0. 
- Two-step upgrade path - Any appliance running version 1.1 must first be upgraded to version 1.2. If you have a multi-node appliance, upgrade both nodes to version 1.2 before you upgrade to version 2.0.