Customer Deployment Operational Checklist
This checklist consolidates the deployment activities from the deployment guide into an operational format that can be completed during planning, installation, validation, and handoff. Use the fill-in fields to capture customer-specific details as work is completed.
How to use this checklist
Complete the owner and customer data fields as decisions are made or tasks are performed. Mark each checkbox when the task is complete. Where a task is conditional, complete it only if that component or integration applies to the customer environment.
- 1 Deployment Readiness
- 2 Networking and Infrastructure Prerequisites
- 3 Architecture and Design Decisions
- 4 Cluster Installation and Registration
- 5 Hypervisor Build Tasks
- 5.1 VMware vSphere
- 5.2 Nutanix Prism
- 5.3 Proxmox VE
- 6 Gateway and Load Balancer Setup
- 7 External Hyperstream Configuration
- 8 System Updates
- 9 Apporto Service and Host Configuration
- 10 Administration and Resource Setup
- 11 User Management and Validation
- 12 Go-Live and Handover
- 13 Final Sign-Off
Deployment Readiness
# | Task | Customer Data | Owner | Status |
|---|---|---|---|---|
1.1 | Confirm Apporto instance name | Instance name: ____________________ | ____________________ |
|
1.2 | Confirm Apporto instance URL | URL: ____________________ | ____________________ | NOT STARTED |
1.3 | Identify initial control plane administrator | Name / email: ____________________ | ____________________ | NOT STARTED |
1.4 | List any additional local administrator accounts needed | Names: ____________________ | ____________________ | NOT STARTED |
1.5 | Plan identity management integration | Method: ____________________ | ____________________ | NOT STARTED |
Networking and Infrastructure Prerequisites
# | Task | Customer Data | Owner | Status |
|---|---|---|---|---|
2.1 | Assign static IP for manager node | IP: ____________________ | ____________________ | NOT STARTED |
2.2 | Assign static IP for worker node 1 | IP: ____________________ | ____________________ | NOT STARTED |
2.3 | Assign static IP for worker node 2 | IP: ____________________ | ____________________ | NOT STARTED |
2.4 | Assign static IP for gateway or load balancer | IP: ____________________ | ____________________ | NOT STARTED |
2.5 | Assign static IPs for workload VMs | IPs: ____________________ | ____________________ | NOT STARTED |
2.6 | Define control plane FQDN | FQDN: ____________________ | ____________________ | NOT STARTED |
2.7 | Define Hyperstream endpoint FQDN | FQDN: ____________________ | ____________________ | NOT STARTED |
2.8 | Define RDP management gateway FQDN | FQDN: ____________________ | ____________________ | NOT STARTED |
2.9 | Define secure gateway or load balancer FQDN | FQDN: ____________________ | ____________________ | NOT STARTED |
2.10 | Create internal DNS A records | Records: ____________________ | ____________________ | NOT STARTED |
2.11 | Create external or public DNS A records if required | Record / public IP: ____________________ | ____________________ | NOT STARTED |
2.12 | Confirm certificate common name and SAN entries | CN / SANs: ____________________ | ____________________ | NOT STARTED |
2.13 | Record issuing certificate authority | CA: ____________________ | ____________________ | NOT STARTED |
2.14 | Confirm private key is available and secured | Location: ____________________ | ____________________ | NOT STARTED |
2.15 | Confirm certificate chain is complete | Chain details: ____________________ | ____________________ | NOT STARTED |
2.16 | Record certificate expiration date | Dec 31, 2026 or actual expiry: ____________________ | ____________________ | NOT STARTED |
2.17 | Identify certificate renewal owner | Owner: ____________________ | ____________________ | NOT STARTED |
2.18 | Approve firewall access for management on port 443 | Approval reference: ____________________ | ____________________ | NOT STARTED |
2.19 | Approve gateway to appliance traffic on port 30443 | Approval reference: ____________________ | ____________________ | NOT STARTED |
2.20 | Approve admin access to secure gateway on port 8443 | Approval reference: ____________________ | ____________________ | NOT STARTED |
2.21 | Approve user network access to secure gateway on port 443 | Approval reference: ____________________ | ____________________ | NOT STARTED |
2.22 | Approve egress from appliance to DNS on port 53 | DNS servers: ____________________ | ____________________ | NOT STARTED |
2.23 | Approve egress from appliance to NTP on port 123 | NTP servers: ____________________ | ____________________ | NOT STARTED |
2.24 | Approve egress from appliance to Active Directory on ports 389 or 636 | Directory endpoints: ____________________ | ____________________ | NOT STARTED |
2.25 | Approve egress from appliance to public HTTPS endpoints on port 443 | Allowed destinations: ____________________ | ____________________ | NOT STARTED |
2.26 | Approve egress from appliance to VDI or RDS servers on port 3389 | Targets: ____________________ | ____________________ | NOT STARTED |
2.27 | Approve egress from appliance to Nutanix Prism on port 9440 if applicable | Prism endpoint: ____________________ | ____________________ | NOT STARTED |
2.28 | Approve egress from appliance to VMware vCenter on port 443 if applicable | vCenter endpoint: ____________________ | ____________________ | NOT STARTED |
2.29 | Select hypervisor platform | Platform: ____________________ | ____________________ | NOT STARTED |
2.30 | Confirm hypervisor version is supported | Version: ____________________ | ____________________ | NOT STARTED |
Architecture and Design Decisions
# | Task | Customer Data | Owner | Status |
|---|---|---|---|---|
3.1 | Finalize control plane ownership and availability model | Notes: ____________________ | ____________________ | NOT STARTED |
3.2 | Confirm cluster node sizing | Sizing plan: ____________________ | ____________________ | NOT STARTED |
3.3 | Finalize node count and roles | Manager: ____ Worker: ____ Mixed: ____ | ____________________ | NOT STARTED |
3.4 | Select load balancer type | Type: ____________________ | ____________________ | NOT STARTED |
3.5 | Confirm HAProxy sizing if Apporto HAProxy is used | Sizing: ____________________ | ____________________ | NOT STARTED |
3.6 | Finalize session delivery path | Path: ____________________ | ____________________ | NOT STARTED |
3.7 | Finalize identity provider integration | IdP: ____________________ | ____________________ | NOT STARTED |
3.8 | Document MFA requirements | MFA method: ____________________ | ____________________ | NOT STARTED |
3.9 | Finalize target host pools, images, and segmentation | Notes: ____________________ | ____________________ | NOT STARTED |
3.10 | Document backup and disaster recovery approach | Plan reference: ____________________ | ____________________ | NOT STARTED |
Cluster Installation and Registration
# | Task | Customer Data | Owner | Status |
|---|---|---|---|---|
4.1 | Sign in to the control plane with the initial administrator account | Administrator: ____________________ | ____________________ | NOT STARTED |
4.2 | Navigate to Setup, On-Prem Clusters, and start installation | Cluster name: ____________________ | ____________________ | NOT STARTED |
4.3 | Download the Apporto VM image for the selected hypervisor | File type: ____________________ | ____________________ | NOT STARTED |
4.4 | Enter Apps in the subscription field before checking hybrid implementation | Confirmed by: ____________________ | ____________________ | NOT STARTED |
4.5 | Open the on-prem cluster management interface on the manager node | Manager URL: ____________________ | ____________________ | NOT STARTED |
4.6 | Verify all nodes appear in node discovery | Nodes discovered: ____________________ | ____________________ | NOT STARTED |
4.7 | Create the cluster from discovered nodes | Selected nodes: ____________________ | ____________________ | NOT STARTED |
4.8 | Assign manager, worker, or mixed roles to each node | Role mapping: ____________________ | ____________________ | NOT STARTED |
4.9 | Register the cluster | Registration result: ____________________ | ____________________ | NOT STARTED |
4.10 | Select or create the resource hub | Resource hub: ____________________ | ____________________ | NOT STARTED |
4.11 | Enter Hyperstream name in resource hub settings | Value: ____________________ | ____________________ | NOT STARTED |
4.12 | Enter Hyperstream secret FQDN | Value: ____________________ | ____________________ | NOT STARTED |
4.13 |