Overview

Thinfinity Cloud Manager fully automates the VDI lifecycle on Proxmox VE — creation from template, user assignment, pool management, power scheduling, and scheduled destruction. However, because the Proxmox integration is snapshot-based rather than golden-image–based, OS-level customization such as Sysprep, hostname generation, and automatic domain join is not executed at provisioning time. Those steps must be performed manually after the VM is created, typically through PowerShell.

This article explains the difference between the two provisioning models, the exact scope of automation available today on Proxmox, and the recommended operating model.

Golden image vs. snapshot provisioning

Understanding the difference between these two provisioning models is essential to understanding the current Proxmox integration.

Golden image

• A generalized VM image prepared to be cloned at scale.
• Uses Sysprep (Windows) or cloud-init (Linux) to reset machine identity at first boot.
• Supports automatic hostname generation, automatic domain join, and user, network, and OS customization applied before first use.
• Designed for fully automated, hands-off VDI lifecycles.

Snapshot

• A point-in-time copy of an existing VM.
• The cloned VM is effectively the same machine, not a generalized one.
• Cannot be Sysprepped.
• Machine identity (hostname, SID) is preserved from the source.

Current Proxmox provisioning model

At this time, VM deployment on Proxmox in Thinfinity Cloud Manager is snapshot-based. In practice, this means:

• VMs are created from an existing snapshot or template.
• No Sysprep or cloud-init is executed during or after creation.
• Any OS-level change required for the VM to enter production use cannot be automated from the Cloud Manager creation workflow. Those steps must be performed manually — typically through PowerShell — after the VM has been created.

Supported capabilities

All VDI lifecycle and operational automation features work as expected on Proxmox:

In short, all VDI automation at the infrastructure and Workspace level behaves as expected.

Known limitations

Because provisioning is snapshot-based, the following operations are not executed automatically at VM creation:

Any of the above must be performed manually before the VM is considered ready for productive use.

Required manual steps after VM creation

When Sysprep-equivalent behavior is needed, perform these steps after the VM is provisioned by Cloud Manager. They are typically scripted in PowerShell:

1. Rename the machine to a unique hostname.
2. Join the domain (after the hostname has been changed).
3. Apply post-deployment OS configuration (policies, agents, local settings, and so on).
4. Restart the VM to finalize identity and domain membership.

Tip: Standardize this process in a reusable PowerShell script so it can be executed consistently across all newly provisioned machines.

Recommended operating model on Proxmox

Because automatic domain join is not available, the recommended deployment model for Proxmox is the General Purpose Model (without domain):

• Machines are provisioned standalone (workgroup).
• Best suited for workgroup-based VDIs, test and lab environments, and non-domain workloads.

Domain-joined deployments remain technically possible, but require the manual post-creation procedure described above.

Summary

Thinfinity Cloud Manager fully automates the VDI lifecycle on Proxmox, but because provisioning is snapshot-based (not golden-image–based), OS-level customization such as Sysprep, domain join, and hostname changes must be performed manually after VM creation.

Frequently asked questions

Can I use Proxmox today for a production VDI environment with Thinfinity?

Yes. All lifecycle automation (create, assign, pool, power schedule, destroy) is fully supported. The only caveat is that any identity-level customization, such as hostname change and domain join, must be handled manually post-creation.

Is golden-image / Sysprep support planned for Proxmox?

This article reflects the current capability. Contact your Cybele account team for the latest roadmap commitments.

Does this limitation also apply to other hypervisors?

No. This limitation is specific to the Proxmox integration. Other supported platforms may offer different provisioning models — see the KB article for your target hypervisor.

Can the manual post-creation steps be triggered from Thinfinity Cloud Manager?

Not as part of the creation workflow. They must be executed externally — for example, via a PowerShell script run against the VM after it has been created.

Which deployment model should I choose on Proxmox?

Unless you have a strict domain-join requirement, the General Purpose (workgroup) Model is recommended, as it avoids the manual steps entirely.