BEFORE YOU BEGIN
Check before you begin
Agents, Communicator, Data Mover and application-specific restore components have different roles. Match installation steps to the OS, agent type and approved release; a lab candidate is not a general customer release.
Screenshots were captured from the actual lab interface on 16 October 2026. The interface is in English; explanations follow your selected language. Resource names, dates and settings are examples; use values for your own environment.
Some lab screenshots are withheld pending privacy review. Follow the documented steps and use your own environment values.
Visual note: the earlier real Linux File Backup connection screen is reused. Agent is alive and responsive is only a connectivity check, not an installer or new data acceptance. No agent was installed, no registration/token/service or policy was changed, and no backup/restore was started.
- OS, architecture, agent type and release
- Approved package, checksum and trusted source
- Master/repository address, CA and secret files
- Authorized test window and recovery acceptance plan
011. Select the role and package
Distinguish the Windows file/AD agent, Communicator service and Linux Data Mover component. Verify OS, x64 architecture, workload and master compatibility against approved release documentation. A virtualization platform connection is not guest-agent installation.
Expected resultThe required component and release are identified.
022. Verify the package and trust chain
Obtain the package through an authorized distribution channel and verify provenance and SHA256SUMS. A hash alone is not a publisher signature. WINDOWS_SIMPLE_SETUP documents pending fresh-install/GUI acceptance for the Simple Setup candidate; do not distribute it as a universal customer package.
Expected resultPackage provenance and acceptance status are recorded.
033. Prepare connectivity and secret files
Obtain master/repository HTTPS addresses, repository identity and the correct CA file from the administrator. An enrollment code and repository token are different credentials; enrollment does not automatically provide repository credentials. Deliver secret files through a protected channel; never embed them in guides, a general Setup or logs.
Expected resultEndpoints, trust roots and credential roles are matched.
044. Verify Windows installation scope
The inspected install-windows-agent.ps1 requires administrator privileges, verifies package hashes and stops for reviewed upgrade/migration if config, service, task or a 62107 listener already exists. ValidateOnly is not installation. Communicator installation does not automatically complete AD restore task provisioning acceptance.
Expected resultWindows prerequisites and separate restore scope are validated.
055. Install the Linux component for the correct role
The inspected install-client.sh requires root privileges, an HTTPS repository endpoint, repository-id, token/API password files and CA; it checks Linux x86-64 binaries. Do not treat this Data Mover installer as a universal installer for every Linux file agent. Use approved package instructions for the environment; do not copy example addresses.
Expected resultThe Linux role is matched to package requirements.
066. Check registration and connectivity
Check the master agent identity, hostname and expected source mapping. Agent is alive and responsive in the Linux File Backup example is a connection response; it does not validate the file tree or backup data. For TLS/CA or network errors, inspect endpoints, permissions and certificate chains rather than disabling security checks.
Earlier real Linux File Backup draft: Agent is alive and responsive. This is a connectivity check, not evidence of installation, file selection or successful backup/restore. The policy was not saved.
Expected resultAgent identity and connectivity results are recorded.
077. Complete initial data acceptance
Using authorized small test data, validate file/application access, the initial backup and isolated restore. A running service and successful enrollment are not data acceptance. Document installation release, components, connection and test results without secrets; track pending restore tasks separately.
Expected resultInstallation and recovery acceptance are documented separately.
COMMON QUESTIONS
Does successful enrollment mean backup is ready?
No. Repository access, data scope, application privileges and backup/restore acceptance require separate validation.