English
Asset Management Overview
Next Terminal calls every managed remote resource an asset. Because configuration, access methods and available tools differ significantly by protocol, this page covers only shared concepts and directs you to protocol-specific guides.
Choose a guide by asset type
| Resource | Guide | Main capabilities |
|---|---|---|
| Linux, Unix and network devices | SSH Assets | Web terminal, SFTP file management, snippets and SSH client access |
| Windows servers and desktops | Windows / RDP Assets | Web desktop, clipboard, network drive, RemoteApp and native RDP clients |
| Graphical control and legacy terminals | VNC and Telnet Assets | VNC graphical sessions and Telnet terminals |
| Internal websites | Web Assets | Authentication, reverse proxy, authorization and private publishing |
| Databases | Database Audit | Database proxy, SQL approval and audit |
Common asset workflow
- Confirm that Next Terminal or the selected gateway can reach the target address and port.
- Prepare a target-system password or private key; create a reusable Credential when appropriate.
- Open Asset Management > Assets and click Create.
- Select a protocol and enter the name, address, port and account.
- Complete the protocol-specific advanced settings.
- Save the asset and test it as an administrator.
- Use Resource Authorization to assign it to users or departments.
- Connect through the browser, a proxy server or Termark.
Shared fields
| Field | Purpose |
|---|---|
| Name | Name shown in administration and user asset lists |
| Alias | Target name for SSH proxy direct mode; starts with a letter and uses letters, numbers, underscores or hyphens |
| Group | Hierarchy used in the asset tree and group authorization |
| Protocol | Determines the port, authentication, session type and advanced settings |
| Network address | Target IP/hostname and port reachable through the actual connection path |
| Account type | Direct password, SSH private key or saved credential |
| Gateway chain | Forwarding path used when the target cannot be reached directly |
| Tags | Cross-group properties such as environment, region and owner |
| Notes | Operational context; never store passwords or tokens here |
Groups, tags and bulk operations
- Use groups for stable hierarchy, such as
Production / Shanghai / Windows. - Use tags for cross-cutting properties, such as
critical,financeorvendor. - For bulk import, download the current template, test a small batch, then verify protocol, port, credential, group and gateway values.
- Use bulk edit carefully to update shared properties such as gateways.
Choose a network path
- Directly reachable from the Next Terminal server: do not select a gateway.
- Located in a VPC, office network or remote site: use a Security Gateway.
- Reachable through an existing SSH jump host: use an SSH Gateway.
- With a gateway chain, enter the address reachable from the final gateway, not the address visible only from the user's computer.
Why a newly created asset may still be unavailable
Creating an asset stores connection information but does not grant every user access. Check that:
- An administrator can connect successfully.
- The user or department has resource authorization.
- The authorization has not expired.
- Its access strategy permits required actions such as upload, download and clipboard use.
- The selected access method supports the protocol.