Cisco TMS Sunset: Why the Obvious Next Step Isn’t Always “the Cloud”

As Cisco prepares to retire TMS, enterprises face a pivotal decision about how to manage video infrastructure—balancing cloud innovation with security, control, and operational continuity

Security, Compliance & RiskNews

Published: June 29, 2026

Kristian McCann

Cisco’s TelePresence Management Suite (TMS) reaching end of life marks a significant inflection point for organizations that have relied on it for over a decade. What was once a cornerstone of enterprise video infrastructure is now being phased out, forcing IT leaders to reassess how they manage devices, calls, and collaboration environments going forward. This is not simply a technical upgrade—it is a strategic shift.

In a recent UC Today discussion, Kristian McCann sits down with Giles Adams, CEO at VQ Communications, to unpack what this transition really means. Adams brings a practitioner’s perspective, shaped by years of working closely with Cisco environments and guiding enterprises through complex migrations. His insights cut through the surface-level narrative of “move to the cloud” and instead highlight the nuanced realities facing IT teams.

The conversation sets out to clarify both the urgency and the opportunity. While the end of TMS may feel disruptive, it also opens the door to modernizing infrastructure, improving visibility, and rethinking how video services are delivered—particularly in a world shaped by hybrid work, heightened security concerns, and evolving compliance requirements.

From Stability to Uncertainty

One of the most immediate reactions Adams observes among customers is concern. “In some cases there’s a sense of panic,” he explains, noting that organizations are confronting the loss of a platform they have depended on for years. This is less about emotional reaction and more about operational risk—TMS has been deeply embedded in workflows, and replacing it is not trivial.

However, the shift away from TMS has been building for some time. The platform has seen limited development in recent years, and many organizations have already explored alternatives such as Cisco Control Hub. Even so, adoption has not been universal. Adams points out that “there could be security reasons why they can’t access cloud-based services,” particularly in sectors where data sovereignty and compliance are critical.

This tension between modernization and control is becoming more pronounced. While cloud platforms offer scalability, rapid feature development, and rich integrations, they also introduce new risk considerations. Adams highlights geopolitical instability and real-world incidents impacting data centers as factors influencing decision-making: “People are considering that cloud is at risk… data centers are now legitimate military targets.”

As a result, organizations are not simply defaulting to cloud migration. Instead, they are conducting deeper risk assessments—evaluating where their communications should be hosted, how sensitive data is handled, and what level of control they are willing to relinquish.

Rethinking the Path Forward

Rather than presenting a one-size-fits-all solution, Adams emphasizes a more tailored approach. For some, Cisco Control Hub remains the logical next step. For others—particularly in regulated or high-security environments—on-premises or air-gapped solutions remain essential.

To address this gap, VQ Communications has developed tooling designed to help organizations transition off TMS while maintaining control over their infrastructure. Adams describes this as “a modern version of some of the basic functionality that TMS delivered,” but with significant enhancements. These include deeper analytics, improved automation, and better visibility into device performance and compliance.

Importantly, the goal is not to replicate TMS, but to evolve beyond it. Adams stresses that organizations should expect more from their next platform: “Nobody wants to replace one piece of software that just does the basics.” Instead, modern systems should enable proactive monitoring, policy enforcement, and operational efficiency through automation.

For example, capabilities such as template-based configuration allow IT teams to enforce consistent policies across devices. Adams illustrates this with a simple use case: ensuring devices are muted by default to prevent unintended audio exposure. These kinds of controls, combined with richer data insights, help organizations improve both user experience and security posture.

Balancing Innovation and Control

Ultimately, the end of TMS is less about the retirement of a legacy tool and more about a broader shift in how enterprises approach video and collaboration infrastructure. Organizations must now balance competing priorities: the agility and innovation of the cloud versus the control and assurance of on-premises environments.

Adams encourages a pragmatic approach. “Go out and do a little bit of research… what are my options here?” he advises, underscoring the importance of informed decision-making rather than reactive migration. The right path will vary depending on industry, risk tolerance, and operational needs.

What is clear, however, is that standing still is not an option. Whether organizations move to cloud platforms like Control Hub or adopt modernized on-prem solutions, the transition presents an opportunity to enhance capabilities, improve resilience, and future-proof their environments.

As enterprises navigate this shift, the conversation highlighted by McCann and Adams serves as a useful guide. It reframes the TMS end-of-life moment not as a disruption to manage, but as a strategic reset—one that will define how organizations deliver secure, reliable, and scalable video experiences in the years ahead.

Call RecordingCollaboration SecurityCollaborative Work ManagementCommunication Compliance​Mobile Device Management (MDM)Security and Compliance
Featured

Share This Post