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.
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 |
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 |
Enter secure gateway FQDN if applicable |
Value: ____________________ |
____________________ |
Not started |
|
4.14 |
Enter RDP management gateway hostname |
Value: ____________________ |
____________________ |
Not started |
|
4.15 |
Select default traffic routing target |
Selection: ____________________ |
____________________ |
Not started |
|
4.16 |
Review installation settings before completion |
Reviewer: ____________________ |
____________________ |
Not started |
|
4.17 |
Finish installation and confirm success |
Outcome: ____________________ |
____________________ |
Not started |
Hypervisor Build Tasks
Complete only the section for the hypervisor or cloud platform used by the customer.
VMware vSphere
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
5.1 |
Import OVA as an OVF template in vSphere |
Template name: ____________________ |
____________________ |
Not started |
|
5.2 |
Select compute resource, storage, and network |
Resource / datastore / network: ____________________ |
____________________ |
Not started |
|
5.3 |
Convert the imported VM to a template if needed |
Template reference: ____________________ |
____________________ |
Not started |
|
5.4 |
Create VMs from the template for all nodes |
Node names: ____________________ |
____________________ |
Not started |
|
5.5 |
Adjust CPU and memory for each node type |
Configured sizing: ____________________ |
____________________ |
Not started |
|
5.6 |
Power on the manager node and configure networking |
Manager config: ____________________ |
____________________ |
Not started |
|
5.7 |
Configure networking on each additional node |
Node configs: ____________________ |
____________________ |
Not started |
|
5.8 |
Set NTP to UTC on all nodes |
NTP setting: ____________________ |
____________________ |
Not started |
Nutanix Prism
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
5.9 |
Import the VMDK file in Prism |
Image name: ____________________ |
____________________ |
Not started |
|
5.10 |
Create the VM and attach the imported disk in Legacy BIOS mode |
VM names: ____________________ |
____________________ |
Not started |
|
5.11 |
Verify the VMDK points to the correct storage container |
Container: ____________________ |
____________________ |
Not started |
|
5.12 |
Power on the manager node and configure networking |
Manager config: ____________________ |
____________________ |
Not started |
|
5.13 |
Repeat the build and network configuration for worker nodes |
Worker configs: ____________________ |
____________________ |
Not started |
|
5.14 |
Set NTP to UTC on all nodes |
NTP setting: ____________________ |
____________________ |
Not started |
Proxmox VE
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
5.15 |
Upload the OVA to the Proxmox datastore |
Datastore: ____________________ |
____________________ |
Not started |
|
5.16 |
Import with the correct bridge, CPU type, and auto-start settings |
Settings: ____________________ |
____________________ |
Not started |
|
5.17 |
Set advanced options for storage controller and NIC type |
Controller / NIC: ____________________ |
____________________ |
Not started |
|
5.18 |
Power on the manager node and configure networking |
Manager config: ____________________ |
____________________ |
Not started |
|
5.19 |
Repeat the build and network configuration for worker nodes |
Worker configs: ____________________ |
____________________ |
Not started |
|
5.20 |
Set NTP to UTC on all nodes |
NTP setting: ____________________ |
____________________ |
Not started |
Microsoft Azure
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
5.21 |
Send the subscription ID and tenant ID to Apporto, and confirm image access |
Subscription ID: ____________________ |
____________________ |
Not started |
|
5.22 |
Create a resource group for the cluster only, and give the installer Contributor on it |
Resource group / region: ____________________ |
____________________ |
Not started |
|
5.23 |
Confirm vCPU quota in the region: 2 of the DSv5 family and 4 of the ESv5 family |
Quota: ____________________ |
____________________ |
Not started |
|
5.24 |
Store the front door certificate and its password in Key Vault, and turn on template deployment access |
Key Vault: ____________________ |
____________________ |
Not started |
|
5.25 |
Choose the users’ DNS name and who may reach the front door |
DNS name / source range: ____________________ |
____________________ |
Not started |
|
5.26 |
Connect the cluster network to AD and the RDS or VDI servers, by peering or VPN if needed |
Peering / VPN: ____________________ |
____________________ |
Not started |
|
5.27 |
Run the preflight checks, preview the deployment, and deploy the template |
Deployment name: ____________________ |
____________________ |
Not started |
|
5.28 |
Point the users’ DNS name at the front door |
Front door address: ____________________ |
____________________ |
Not started |
|
5.29 |
Turn off the manager node’s public address after the install |
Date: ____________________ |
____________________ |
Not started |
Gateway and Load Balancer Setup
Apporto HAProxy
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
6.1 |
Provision two Linux VMs for HAProxy |
Node 1 IP: ____________________ Node 2 IP: ____________________ |
____________________ |
Not started |
|
6.2 |
Allocate VIPs for Hyperstream and RDP management |
HS VIP: ____________________ RDP VIP: ____________________ |
____________________ |
Not started |
|
6.3 |
Record network gateway and DNS server IPs |
Gateway / DNS: ____________________ |
____________________ |
Not started |
|
6.4 |
Enable non-local bind on both nodes |
Nodes updated: ____________________ |
____________________ |
Not started |
|
6.5 |
Install HAProxy, Keepalived, and Conntrackd |
Package versions: ____________________ |
____________________ |
Not started |
|
6.6 |
Configure Conntrackd peer and interface settings |
Config summary: ____________________ |
____________________ |
Not started |
|
6.7 |
Configure Keepalived router IDs, VIPs, and priorities |
VRRP settings: ____________________ |
____________________ |
Not started |
|
6.8 |
Create PEM certificate files for HAProxy |
Certificate files: ____________________ |
____________________ |
Not started |
|
6.9 |
Configure haproxy.cfg including frontends, backends, checks, and TLS |
Config version: ____________________ |
____________________ |
Not started |
|
6.10 |
Validate HAProxy configuration |
Validation result: ____________________ |
____________________ |
Not started |
|
6.11 |
Start and enable all services |
Service state: ____________________ |
____________________ |
Not started |
|
6.12 |
Verify VIP assignment |
VIP check result: ____________________ |
____________________ |
Not started |
|
6.13 |
Test HTTPS connectivity through each VIP |
Test result: ____________________ |
____________________ |
Not started |
|
6.14 |
Perform failover testing |
Failover result: ____________________ |
____________________ |
Not started |
|
6.15 |
Verify HAProxy statistics interface access |
Stats URL: ____________________ |
____________________ |
Not started |
Customer-Managed Load Balancer
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
6.16 |
Record load balancer platform or product |
Product: ____________________ |
____________________ |
Not started |
|
6.17 |
Define frontend VIP for Hyperstream on port 443 |
VIP: ____________________ |
____________________ |
Not started |
|
6.18 |
Define frontend VIP for RDP management |
VIP: ____________________ |
____________________ |
Not started |
|
6.19 |
Configure backend pool to node port 30443 |
Pool members: ____________________ |
____________________ |
Not started |
|
6.20 |
Configure load balancer health checks |
Health check: ____________________ |
____________________ |
Not started |
|
6.21 |
Configure TLS termination with valid certificate |
Certificate reference: ____________________ |
____________________ |
Not started |
|
6.22 |
Confirm WebSocket support |
Validation notes: ____________________ |
____________________ |
Not started |
External Hyperstream Configuration
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
7.1 |
Create external DNS A record for the Hyperstream FQDN if externally exposed |
Record / public IP: ____________________ |
____________________ |
Not started |
|
7.2 |
Obtain wildcard or SAN certificate covering the Hyperstream FQDN |
Certificate CN: ____________________ |
____________________ |
Not started |
|
7.3 |
Install the certificate on the perimeter load balancer or gateway |
Installation notes: ____________________ |
____________________ |
Not started |
|
7.4 |
Configure NAT or port mapping from external 443 to internal 443 |
NAT rule: ____________________ |
____________________ |
Not started |
|
7.5 |
Update Hyperstream external FQDN in the resource hub |
Configured value: ____________________ |
____________________ |
Not started |
|
7.6 |
Update secure gateway public FQDN if applicable |
Configured value: ____________________ |
____________________ |
Not started |
|
7.7 |
Validate external Hyperstream session launch with valid TLS |
Test result: ____________________ |
____________________ |
Not started |
|
7.8 |
Validate WebSocket upgrade and confirm no certificate warnings |
Validation notes: ____________________ |
____________________ |
Not started |
System Updates
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
8.1 |
Open the system updates page in the on-prem cluster management tool |
Accessed by: ____________________ |
____________________ |
Not started |
|
8.2 |
Record the current appliance version |
Version: ____________________ |
____________________ |
Not started |
|
8.3 |
Record the current infrastructure version |
Version: ____________________ |
____________________ |
Not started |
|
8.4 |
Check for available updates |
Check date: ____________________ |
____________________ |
Not started |
|
8.5 |
Download and install available updates |
Updates applied: ____________________ |
____________________ |
Not started |
|
8.6 |
Confirm updated version numbers after completion |
Post-update version: ____________________ |
____________________ |
Not started |
Apporto Service and Host Configuration
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
9.1 |
Identify target host operating systems for service installation |
OS types: ____________________ |
____________________ |
Not started |
|
9.2 |
Install ApportoService on Linux hosts if applicable |
Linux hosts: ____________________ |
____________________ |
Not started |
|
9.3 |
Install ApportoService MSI and prerequisites on Windows hosts if applicable |
Windows hosts: ____________________ |
____________________ |
Not started |
|
9.4 |
Deploy ApportoService by Group Policy if the customer uses GPO-based distribution |
Deployment path: ____________________ |
____________________ |
Not started |
|
9.5 |
Verify services are running and connected to the control plane |
Verification notes: ____________________ |
____________________ |
Not started |
|
9.6 |
Create or identify the RDS or VDI baseline GPO |
GPO name: ____________________ |
____________________ |
Not started |
|
9.7 |
Enable H.264 or AVC hardware encoding |
Policy path or confirmation: ____________________ |
____________________ |
Not started |
|
9.8 |
Enable hardware graphics adapters for RDS sessions |
Policy confirmation: ____________________ |
____________________ |
Not started |
|
9.9 |
Enable WDDM graphics display driver |
Policy confirmation: ____________________ |
____________________ |
Not started |
|
9.10 |
Set RemoteFX adaptive graphics to medium |
Policy confirmation: ____________________ |
____________________ |
Not started |
|
9.11 |
Set idle session timeout |
Timeout: ____________________ |
____________________ |
Not started |
|
9.12 |
Set disconnected session timeout |
Timeout: ____________________ |
____________________ |
Not started |
|
9.13 |
Configure session security layer and encryption level |
Security settings: ____________________ |
____________________ |
Not started |
|
9.14 |
Link the GPO to the session host organizational unit |
OU: ____________________ |
____________________ |
Not started |
|
9.15 |
Force and validate policy application on a test host |
Validation output: ____________________ |
____________________ |
Not started |
Administration and Resource Setup
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
10.1 |
Confirm the product is configured for hybrid implementation |
Confirmed by: ____________________ |
____________________ |
Not started |
|
10.2 |
Configure identity management method |
Method: ____________________ |
____________________ |
Not started |
|
10.3 |
Record domain controller or PDC hostname for LDAP or AD integration |
Host: ____________________ |
____________________ |
Not started |
|
10.4 |
Enter the root certificate for LDAP or AD integration if required |
Certificate reference: ____________________ |
____________________ |
Not started |
|
10.5 |
Record the certificate generation host for SSO to desktop if used |
Host: ____________________ |
____________________ |
Not started |
|
10.6 |
Generate SSO certificates for desktop sign-on if used |
Certificate details: ____________________ |
____________________ |
Not started |
|
10.7 |
Configure AD sync settings and select the on-prem resource hub |
Sync configuration: ____________________ |
____________________ |
Not started |
|
10.8 |
Document that on-prem AD or LDAP sync should be run manually with Sync Now |
Process owner: ____________________ |
____________________ |
Not started |
|
10.9 |
Configure login page branding |
Branding notes: ____________________ |
____________________ |
Not started |
|
10.10 |
Configure help menu links |
Links: ____________________ |
____________________ |
Not started |
|
10.11 |
Configure email templates |
Template notes: ____________________ |
____________________ |
Not started |
|
10.12 |
Configure desktop feature settings and session toolbar options |
Feature set: ____________________ |
____________________ |
Not started |
|
10.13 |
Complete resource hub configuration |
Hub settings: ____________________ |
____________________ |
Not started |
|
10.14 |
Create desktop pools |
Pool names: ____________________ |
____________________ |
Not started |
|
10.15 |
Add multi-session RDS servers |
Server names or IPs: ____________________ |
____________________ |
Not started |
|
10.16 |
Add single-session VDI servers |
Server names or IPs: ____________________ |
____________________ |
Not started |
|
10.17 |
Use separate pools for each operating system type |
Pool separation notes: ____________________ |
____________________ |
Not started |
|
10.18 |
Create virtual desktops in Apps and Desktops |
Desktop names: ____________________ |
____________________ |
Not started |
|
10.19 |
Create published applications in Apps and Desktops |
Application names: ____________________ |
____________________ |
Not started |
|
10.20 |
Set license limits for applications and desktops |
Limits: ____________________ |
____________________ |
Not started |
User Management and Validation
|
# |
Task |
Customer Data |
Owner |
Status |
|---|---|---|---|---|
|
11.1 |
Create user groups |
Group names: ____________________ |
____________________ |
Not started |
|
11.2 |
Define user roles |
Roles: ____________________ |
____________________ |
Not started |
|
11.3 |
Import users or run directory synchronization |
Method: ____________________ |
____________________ |
Not started |
|
11.4 |
Confirm at least one test user can sign in |
Test user: ____________________ |
____________________ |
Not started |
|
11.5 |
Identify user acceptance test participants |
Users: ____________________ |
____________________ |
Not started |
|
11.6 |
Validate authentication and SSO behavior |
Result: ____________________ |
____________________ |
Not started |
|
11.7 |
Validate desktop launch through Hyperstream |
Result: ____________________ |
____________________ |
Not started |
|
11.8 |
Validate application launch |
Result: ____________________ |
____________________ |
Not started |
|
11.9 |
Validate external access if applicable |
Result: ____________________ |
____________________ |
Not started |
|
11.10 |
Run network diagnostics from the on-prem tool if issues are found |
Diagnostic notes: ____________________ |
____________________ |
Not started |
|
11.11 |
Enable a support tunnel if vendor assistance is needed |
Support case / notes: ____________________ |
____________________ |
Not started |
Go-Live and Handover
|
# |
Readiness Item |
Operational Notes |
Owner |
Status |
|---|---|---|---|---|
|
12.1 |
Cluster is installed, registered, and healthy in the control plane |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.2 |
Gateway or load balancer is passing health checks |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.3 |
Resources, pools, desktops, and applications are configured |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.4 |
User authentication is validated |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.5 |
Representative users can launch desktops and applications successfully |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.6 |
Baseline GPO settings are applied and validated on session hosts |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.7 |
System updates have been checked and applied as appropriate |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.8 |
Monitoring, troubleshooting, and support paths are understood by the deployment team |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.9 |
Open issues have owners, priorities, and resolution plans |
Notes: ____________________ |
____________________ |
Ready to review |
|
12.10 |
Support contacts and escalation path are documented |
Support contact: ____________________ |
____________________ |
Ready to review |
Final Sign-Off
|
Field |
Value |
|---|---|
|
Customer name |
____________________ |
|
Deployment lead |
____________________ |
|
Customer technical owner |
____________________ |
|
Go-live date |
____________________ |
|
Handover completed |
____________________ |
|
Notes |
________________________________________________________________________________ |