Where jobs run: what changed from OpCon Classic
This page maps OpCon Classic concepts to their OpCon Continuum equivalents. It is a conceptual mapping under review, and it deliberately does not compare the two products' platform or job-type breadth. Use it to translate what you already know — not as the basis for a migration plan. Confirm specifics with your Continuous contact.
What this solves
In OpCon Classic, jobs ran on LSAM agents pinned to named Machines and Machine Groups. In OpCon Continuum, work runs on the Universal Agent and is routed through Agent Pools, and your existing LSAM machines keep working, reached through a relay. Knowing how the old targeting maps to the new one is what makes an incremental move painless.
What you get. The mapping from Classic machines to OpCon Continuum agents and pools, plus how to keep driving your existing LSAM automation during a transition.
Related topics
- Manage agents and agent pools (Administrator)
- Prepare agents for connectors (Administrator)
- Run commands on legacy LSAM machines (Builder)