HP Anyware and Zero Client Portfolio End of Life Announced
HP Anyware End of Life: What You Need to Know
HP has announced the end of life for HP Anyware and its zero client portfolio, marking a significant shift in enterprise remote access technology. Organizations relying on PCoIP zero client hardware must now plan for endpoint replacement, as AWS has confirmed that existing hardware cannot migrate to successor protocols.
HP Anyware delivered secure remote desktop access and application streaming through its zero client endpoints, eliminating the need for traditional operating systems on client devices. The platform’s Trusted Zero Clients provided simplified device management, reduced security vulnerabilities, and lower total cost of ownership for data centre environments—but the impending end of life means IT teams must evaluate alternative remote access solutions and budget for hardware refreshes.
HP has announced end of life for HP Anyware and its zero client portfolio. AWS has confirmed that PCoIP zero client hardware cannot move to its replacement protocol. If you run zero clients, the endpoint refresh is no longer a question of if.
What HP announced, and when each date lands
In April 2026 HP announced the planned end of life for HP Anyware, Trusted Zero Clients, and the Anyware Trust Center. HP described it as a decision to concentrate investment on other product categories.
The dates are staggered across four years, which is why the announcement has not produced a rush. It also means many estates have a replacement deadline that has not yet been budgeted.
| Date | What happens |
|---|---|
| 9 April 2026 | Trusted Zero Clients and Anyware Trust Center: end of sale. |
| 7 May 2026 | HP Anyware: end of sale to new customers. |
| 31 July 2026 | AWS PCoIP-based WorkSpaces Personal closes to new customers. |
| 31 October 2026 | Trusted Zero Clients: support ends. Last supported version is 25.10, with no further updates or patches. |
| 31 October 2027 | AWS PCoIP WorkSpaces end of support. Zero client endpoints must be replaced by this date. |
| 31 December 2028 | Desktop Access renewals close for Tera2 zero clients and the PCoIP Management Console. |
| 31 October 2029 | HP Anyware maintenance and support end for customers on multi-year terms. |
| 31 December 2029 | Tera2 zero clients and PCoIP Management Console: end of life. |
HP is offering HP Z Remote Graphics Software as an alternative for certain HP Anyware customers with workstation-centric use cases.
The hardware line that decides the project
AWS ended support for PCoIP-based WorkSpaces Personal effective 31 October 2027 and closed the service to new customers on 31 July 2026. In its own FAQ, AWS attributes the decision directly to HP: HP owns PCoIP and has announced end of life, so WorkSpaces is consolidating on Amazon DCV.
For anyone with zero clients on the desk, one sentence in the AWS migration guidance matters more than the rest of the document.
“PCoIP Zero Clients cannot support DCV given their proprietary hardware level integration with the PCoIP protocol. Users connecting with Zero Clients will need to replace the endpoint devices before October 31, 2027.” Amazon WorkSpaces Administration Guide, PCoIP-based WorkSpaces Personal end of support
There is no firmware path across. The silicon speaks PCoIP. Migrating the back end to DCV leaves the endpoint stranded, and the capital cost of the endpoint fleet is usually the larger half of the estate.
Definition: what a PCoIP zero client is
A PCoIP zero client is a stateless endpoint device with no local operating system, no local storage, and no user-installable software. Decoding is handled by a dedicated Teradici Tera-series chip that implements the PCoIP protocol in hardware. The device does nothing except decode a PCoIP stream and pass keyboard, video, mouse, and USB traffic back to a host.
That design is why zero clients were adopted in finance, defence, and government: no local attack surface, no patching, no data at rest. It is also why they cannot be repurposed. The protocol is not a software layer that can be swapped. When PCoIP retires, the hardware retires with it.
Why IP KVM is entering the shortlist
Adder set out its position on 3 July 2026 in a post on PCoIP end of life. The argument is not that KVM replaces VDI. It is that the environments zero clients were bought for have changed, and a hardware access layer answers a different set of requirements than a streaming protocol does.
Access below the operating system
IP KVM reaches a machine when its OS is unavailable or unresponsive. A software client depends on the OS being up to answer.
Protocol independence
KVM transmits the video signal rather than streaming a session from a host. No third-party protocol roadmap sits underneath the estate.
Physical and virtual
The same matrix reaches bare-metal servers, workstations, and virtual machines. VDI protocols only reach the virtual side.
One-time capital cost
Hardware bought once instead of licensed annually. Adder makes predictable CapEx a central part of its migration argument.
No cloud dependency
Runs over LAN, WAN, or a direct point-to-point link. Suitable for isolated and offline deployments where internet access is not permitted.
Operating system agnostic
No agent to install, no guest OS support matrix to track, minimal firmware maintenance across the endpoint fleet.
Five questions to answer before you buy the replacement
Adder published these as the evaluation set for organisations scoping a PCoIP replacement. They are worth answering before any vendor conversation, because the answers rule options in and out quickly.
- Is access required to physical systems, virtual systems, or both?
- How important is support for graphics-intensive applications?
- What are your long-term and lifecycle requirements?
- Will the chosen solution scale as the organisation grows?
- Are software licensing costs a factor in long-term planning?
The first question does most of the work. If the answer includes physical systems, a VDI protocol alone does not cover the requirement, and the shortlist has to include a hardware access layer.
How to sequence the migration
1. Count the endpoints and find the deadline that applies
Trusted Zero Clients lose support on 31 October 2026. Tera2 devices run to 31 December 2029. Estates connecting to AWS WorkSpaces face 31 October 2027 regardless of device generation. Most sites have a mix, so the date that matters is the earliest one in the estate.
2. Separate physical access from virtual access
Split the user base by what they actually reach. Users who only touch virtual desktops can follow a protocol migration. Users who touch physical machines, or who need access when a host is down, are the group a streaming protocol will not serve.
3. Pilot before the fleet purchase
Validate peripheral behaviour, multi-monitor layouts, and video performance on a small group first. Zero client users tend to have fixed, bespoke desk configurations, and those configurations are the most common source of migration friction.
4. Decide the cost model deliberately
A subscription renewal and a hardware purchase land in different budgets and behave differently over a five-year horizon. Model both against the actual replacement deadline rather than the current renewal date.
Scoping a PCoIP replacement in Singapore
Enova Technologies is an authorised Adder partner in Singapore. Send us your endpoint count and how your users split between physical and virtual access, and we will map it to an Adder configuration with regional pricing.
Email [email protected]Frequently asked questions
When exactly do PCoIP zero clients stop working?
The devices do not switch off on a date. Support ends in stages. Trusted Zero Clients lose support on 31 October 2026, with 25.10 as the last supported release. Tera2 zero clients and the PCoIP Management Console reach end of life on 31 December 2029. Anyone connecting to Amazon WorkSpaces has a harder deadline of 31 October 2027, because AWS ends PCoIP support on that date and the endpoints cannot move to DCV.
Can a PCoIP zero client be updated to run a different protocol?
No. AWS states that PCoIP zero clients cannot support DCV because the protocol is integrated at hardware level in the device. There is no firmware upgrade path to another protocol. Endpoints have to be replaced.
Why did HP end support for PCoIP?
HP announced in April 2026 that it was winding down parts of its remote desktop portfolio to concentrate investment on categories where it saw stronger long-term returns. HP Anyware, Trusted Zero Clients, and the Anyware Trust Center were all included. HP Z Remote Graphics Software is offered as an alternative for certain workstation-centric HP Anyware customers.
What is the difference between IP KVM and a VDI protocol like PCoIP or DCV?
A VDI protocol streams a virtual session from a host, which requires the host operating system to be running and responsive. IP KVM transmits the video signal from a physical or virtual machine and passes keyboard, mouse, and USB back, which works below the operating system. That means an operator can reach a machine during boot, in BIOS, or when the OS has failed.
Does IP KVM require internet or cloud access?
No. Adder IP KVM operates over LAN, WAN, or a direct point-to-point connection without cloud services or internet connectivity. That makes it deployable in isolated and offline environments, which is a common requirement in government, defence, and utilities.
Is IP KVM a subscription or a one-time purchase?
Adder IP KVM is a hardware purchase with no ongoing per-seat subscription. Adder positions this as one of the main reasons organisations are moving off software-licensed remote access: a capital purchase gives a predictable cost over the lifecycle rather than a renewal price that can change.
Sources: HP Anyware, Trusted Zero Clients and Anyware Trust Center end of life announcement (HP, April 2026) · PCoIP-based WorkSpaces Personal end of support (Amazon WorkSpaces Administration Guide) · PCoIP Zero Clients Are Reaching End Of Life, What Organizations Need to Consider Next (Adder Technology, 3 July 2026) · Remote desktop, enabled by KVM (Adder Technology).
Published by
eNOVA Technologies is Singapore's specialist distributor for data centre IT management solutions, representing Adder, Guntermann & Drunck, Raritan, Sunbird, ZPE Systems, and VuWall across Singapore and Southeast Asia. Our technical content is produced with AI assistance and reviewed by our in-house team before publication.
This article was produced with AI assistance and reviewed by the eNOVA Technologies team. All technical claims are verified against manufacturer documentation.
