University of South Carolina turns to AppsAnywhere to expand virtual access to engineering software
The University of South Carolina’s Molinaroli College of Engineering and Computing has selected AppsAnywhere to power a Virtual Computer Labs initiative, aiming to broaden access to critical engineering applications for roughly 5,000 students. The move highlights growing institutional efforts to deliver complex software beyond campus computer labs while raising technical, licensing and equity questions.
By Where Should I Learn Editorial ·
The University of South Carolina’s Molinaroli College of Engineering and Computing (MCEC) has adopted an application-delivery platform from AppsAnywhere to support a new Virtual Computer Labs initiative intended to expand access to academic software for about 5,000 engineering students. The announcement, issued from AppsAnywhere’s Charlotte, N.C., office, frames the platform as a way to help students use specialized tools “where and when they are most productive,” a point underscored by Brian Hull, the university’s director of IT services.
Virtual computer labs refer broadly to systems that let students run campus-licensed software from personal devices, often through application streaming, virtualization or remote desktop technologies. For engineering programs, which routinely rely on CAD packages, simulation suites and other resource-intensive tools, extending access beyond physical labs has become a practical priority for both instruction and student schedules.
MCEC’s stated goal — extending critical academic software to thousands of students — speaks to a tension many engineering colleges face: balancing high costs and space constraints of on-campus computer labs with student demand for flexible study time. "Engineering students increasingly need the flexibility to work where and when they are most productive," Hull said in the announcement, framing the university’s rationale for the initiative.
Moving those applications off the lab workstation and onto a student’s personal laptop or a remote session raises a set of logistical and technical questions. High-performance engineering software can have heavy CPU or GPU requirements, strict licensing terms that bind use to campus machines, and data-management needs tied to large project files. Each of these factors shapes how a virtual lab must be designed.
Accessibility is another central consideration. Virtual labs can reduce geographic and scheduling barriers by allowing students to complete assignments from home, an off-campus job site, or late at night. At the same time, that benefit depends on students having reliable broadband connections and devices capable of handling streamed or virtualized applications — conditions that are uneven across any student population.
Scaling a virtual lab to serve an engineering college of roughly 5,000 students also presents capacity-management challenges. Administrators must decide how to allocate concurrent session slots, prioritize courses and projects with heavy resource requirements, and plan for peak demand around midterms and project deadlines. These operational choices affect both the user experience and the cost profile of a virtual lab deployment.
AppsAnywhere is described in the announcement as a "student-first application delivery platform for higher education." Vendors in this space generally emphasize unified portals, simplified software delivery and reducing the need for students to install complex packages locally. Implementations differ, however, in how they handle licensing, performance optimization and integrations with campus learning-management systems.
From an institutional budgeting perspective, virtual labs represent a tradeoff. They can reduce the need for physical lab space and desktop refresh cycles, but they can also introduce new expenses: cloud compute or licensing fees, staff time for integration and support, and investments in networking. Universities considering similar moves must weigh those costs against the pedagogical value of broader access.
Security and compliance remain part of the conversation, particularly for engineering work involving controlled research data or proprietary designs. Institutions need to ensure that any remote access model includes appropriate authentication, data segregation and backup practices. Those operational safeguards influence vendor selection and contractual arrangements as much as feature lists do.
The University of South Carolina’s adoption of AppsAnywhere is a clear example of how engineering colleges are experimenting with technology to meet student needs without simply expanding brick-and-mortar facilities. The vendor announcement sets out the intent and scale of the initiative, but it leaves open questions about timelines, technical architecture, licensing models and how the rollout will be evaluated. Those details will determine whether the virtual labs deliver the flexibility and reliability MCEC intends to provide to its students.
All articles