IMD SolutionComputing LibraryShop main store

How-to

Running Studio 5000 in a VM with licensing and PLC access

Remote access and virtualization Published 8 min read

Short answer

Yes. Give each programming suite its own guest, serve FactoryTalk Activation from the host or a dedicated license VM so a rebuilt guest needs no rehost, and bind the guest to the physical NIC that carries the engineering network before touching USB passthrough. A guest that opens Logix Designer but cannot acquire a license or reach the controller has only passed installation.

On this page
  1. Verify the supported combination before building the image
  2. Put the activation where a rebuild cannot touch it
  3. Licensing three programming guests with one activation seat
  4. Bind the guest to the physical NIC before anything else
  5. Recover a disconnected adapter without rebooting
  6. USB adapters last, not first
  7. Questions asked

Yes. Give Studio 5000 its own guest, serve FactoryTalk Activation from the host or a dedicated license VM, and bind the guest to the physical NIC that carries the engineering network. Those three decisions answer both concerns that come with virtualizing a Rockwell engineering station: the license survives a guest rebuild, and controller access runs over Ethernet before anyone fights USB passthrough. The hypervisor is secondary — Hyper-V, VMware and VirtualBox guests all carry Rockwell suites in field service, from v20-era RSLogix releases to Logix Designer v32. What actually fails these builds is an unsupported software combination, an activation stranded inside a guest you are about to delete, or a virtual adapter bridged to the wrong physical NIC. Build the image around the license and the network path, not around the installer.

Verify the supported combination before building the image #

Write down three things before you create the guest disk: the Studio 5000 Logix Designer release your projects need, the guest Windows edition and version, and the communication software the equipment requires. The Rockwell Automation compatibility listings are the deciding source — they carry Studio 5000 Logix Designer releases including 26.01, 27.00.00, 28.02.01 and 30.00.00 with their supported combinations — and Rockwell's virtual design considerations document walks an engineering workstation and emulated controllers through a virtualized architecture. A clean install of the suite proves nothing about a supported combination.

Then partition the suites: one guest for the Rockwell stack, one for the Siemens stack, one for everything else. That isolation is the point — when an install wrecks one environment, you restore that one guest, reported in the field at an hour or less, instead of rebuilding the workstation. A guest that exists only to keep legacy software runnable deserves the same containment and recovery planning as a P2V migration plan for an aging machine controller.

Pick the hypervisor by your weakest peripheral, not by the suite; the trade-offs in Hyper-V vs VMware Workstation for PLC programming VMs come down to USB device support and management. License the guest Windows separately from the host — a licensed host edition does not cover its guests by itself. Size memory and processors from the suite's documented requirements, and if project loads still drag, work through fixing slow automation VMs on a Windows 11 host before blaming the suite.

Put the activation where a rebuild cannot touch it #

Open FactoryTalk Activation Manager and read the actual state before changing anything: an activation can be missing, or present and already in use. Those are different faults with different fixes. Then pick one of three arrangements:

  1. Activation service on the host. Run FactoryTalk Activation on the base machine and point the guest at it. Rebuilding, rolling back or deleting the programming guest leaves licensing untouched. This is the arrangement field users report as the simplest: licenses on the base machine, guests acquire them over the network.
  2. A dedicated license VM. A small guest runs only the activation service, and every programming guest reaches it over the network. Reported working with a Windows 11 license guest feeding Windows 10 and XP programming guests. Licensing is off both the host and the disposable guests; the cost is that the license VM must be running and reachable before Logix Designer opens.
  3. Activation in the guest, or on a dongle. The activation lives with the workstation that uses it, or on a USB dongle passed through to the guest. No network dependency at all — but the activation now sits inside the thing you built to be disposable. Dongle users report transferring port ownership to VirtualBox and VMware guests routinely.

Two rules apply whichever arrangement holds the seat. First, the authorized way to move an activation between machines is the rehost process in FactoryTalk Activation Manager, documented by Rockwell as an online transfer: run it before you delete, clone or replace a guest that holds one. Second, a seat in use is in use everywhere — dongle users report the seat counting as in use while another Logix Designer session stays open, outside the VM included, so close the other versions first. Duplicating a bound activation or spoofing a disk serial to run one seat on several machines at once is circumvention, not licensing; the rehost process is the only sanctioned move.

One routing trap quietly breaks the first two arrangements: host and guest on different networks. Sharing hardware is not sharing a network, and a reported host license server failure traced exactly to that. Test the guest-to-license-server path as its own item, separately from PLC communication.

Licensing three programming guests with one activation seat #

Inputs:

  • 3 programming guests on one host — a field-reported arrangement: Windows 10 with Studio 5000, Windows 10 with the Siemens suite, Windows XP with RSLogix 5000.
  • 1 activation seat for Logix Designer — the single-seat activation or dongle arrangement users report on engineering stations.
  • The seat rule, reported by dongle users: while one session holds the seat, any other session that needs it finds it in use.
  • The transfer rule, from Rockwell's documented rehost process: moving an activation off a machine is an authorized transfer, not a file copy.

Rule in words: divide the number of programming guests that must open Logix Designer by the number of seats you own. If the ratio is above one, the seat has to live outside the guests.

Arithmetic, guest-local activation:

  • 3 guests ÷ 1 seat = 3 guests per seat, so the seat installs into only 1 of the 3 guests.
  • 3 − 1 = 2 guests that cannot open Logix Designer at all.
  • Every hand-off to another guest costs 1 rehost, and clearing the guest that holds the seat costs 1 rehost before deletion.

Arithmetic, network-served activation:

  • The same 1 seat on the host or license VM serves 3 ÷ 1 = 3 guests.
  • 0 rehosts per guest rebuild, however many rebuilds you run.
  • Concurrency stays at 1 simultaneous session across host and guests, per the seat rule above.

Result: with three guests and one seat, network serving activates 3 of 3 guests with zero rehost events; guest-local activation activates 1 of 3 and adds a rehost at every move. Decision: above one programming guest per activation seat — here 3 ÷ 1 = 3 — serve FactoryTalk Activation from the host or a dedicated license VM. Keep activation inside the guest only at exactly one guest per seat, accepting a rehost at every rebuild of that guest.

Bind the guest to the physical NIC before anything else #

PLC access is a networking task first. In Hyper-V that means an external virtual switch paired with the physical network card — the switch type Microsoft documents for giving guests a path through one specific physical adapter. Work it in order:

  1. Identify, by name, the physical NIC wired to the engineering network. If the host also carries wireless and USB Ethernet adapters, automatic bridging eventually picks the wrong one; select explicitly.
  2. Create the external virtual switch and pair it with that physical card.
  3. Attach the guest's virtual adapter to that switch and set the guest's address on the controller subnet.
  4. Test by explicit address before browsing. Discovery traffic does not always cross the selected path, so a controller that answers by address but never appears in the browse list is a discovery or driver problem, not a PLC problem.
  5. Leave NAT for the guest's internet access only. A NATed guest is not equivalent to a device on the controller subnet: inbound connections and broadcast discovery behave differently across that boundary.
  6. Permit the suite's traffic in the host and guest firewalls under your policy. An engineering network with no internet still carries the controller path; never disable the firewall globally to get it.
Symptom First cause to check
Host reaches the controller, guest does not Switch bound to the wrong physical NIC, or guest addressing
Controller answers by address, absent from browse Discovery not crossing the path, or the driver on the wrong interface
PLC communication works, activation fails License server on a different or blocked network path
Communication dies after a cable unplug and replug Guest link state or addressing never recovered

Decision point: if the guest reaches the controller by address, the network path is done and stays untouched while you troubleshoot anything else.

Recover a disconnected adapter without rebooting #

A reported nuisance on a long-running VirtualBox guest: after the Ethernet adapter disconnects, communication returns only after a full guest reboot. Make recovery deterministic instead of accepted. Give the guest static addressing, then toggle the virtual adapter's connection in the hypervisor and re-check the guest's address and route before rebooting anything — most dead-adapter cases are addressing that never came back, not a failed virtual device.

Keep PLC programs out of the guest disk at the same time: a host-shared folder or a synced folder means a restored VM backup, which beats reinstalling a full suite stack by hours, costs you no project files. Pointing every guest's data at a separate host folder is established field practice.

USB adapters last, not first #

Modern Logix processors are reached over Ethernet, so the bridged NIC above covers most online sessions with no USB involvement. USB is for legacy paths: DH485 through a 1747-UIC, serial links through USB-serial adapters. Those are field-reported working inside VMware guests, and license dongles pass cleanly to VirtualBox and VMware guests. Under Hyper-V, USB is the weak edge: Enhanced Session Mode redirects devices for compatible guests — field users call it essential — and an XP programming guest may need a separate remote-desktop connection to bridge the gap. For attaching an adapter to a Microsoft hypervisor, follow running a USB programming cable inside a Hyper-V VM; USB programming adapter passthrough workarounds under Hyper-V cover adapter-specific behavior on that hypervisor.

Decision: prove the bridged Ethernet path and the license path first, then add USB passthrough only for an adapter with no Ethernet equivalent.

Questions asked

Can I clone a Studio 5000 VM that holds its activation?

No. The activation is bound to that machine, and a clone does not create the right to a second seat; duplicated bound activations also leave your licensing records out of step. Rehost the activation out through FactoryTalk Activation Manager first, then clone or delete the guest. If activation is served from the host or a license VM, the problem never arises.

Do snapshots keep a Studio 5000 guest licensed?

A snapshot restores machine state, not license rights. Engineers do save open, activated sessions with snapshots, but the seat counts as in use for as long as that state holds it, and rolling a bound activation backward can desynchronize licensing records. Treat snapshots as session state; keep the activation itself outside the guest.

Do I need USB passthrough to go online with a modern Logix controller?

No. Current Logix processors are reached over Ethernet: bind the guest to the physical NIC with an external virtual switch, set the guest address on the controller subnet, and connect by explicit address. Reserve USB passthrough for adapters with no Ethernet path, such as DH485 through a 1747-UIC or legacy serial links.

Why does the guest fail to find the host license server?

Because sharing hardware is not sharing a network. The guest reaches a host or license-VM activation only over a routed IP path with the firewall open for the activation traffic. Host and guest sitting on different networks is a reported cause of exactly this failure: put both on the same virtual switch or add the route, then retest.

Is Hyper-V or VMware the better host for a Rockwell guest?

Both run Rockwell suites in the field, so decide on the edges. If your controllers and adapters are all Ethernet, Hyper-V ships with Windows Pro and Enterprise. If you depend on USB adapters or license dongles, VMware Workstation and VirtualBox passthrough is more field-proven than the Hyper-V workarounds.

Keep reading

  • Troubleshooting

    Fixing a VM remote PLC connection with a NAT adapter

    Set the guest's virtual adapter to NAT with DHCP, disable every other guest adapter, and keep the remote-access soft key on the host. The failure that repeats is a second bridged adapter pulling the PLC route away from the NAT path. Test the host path first, then the guest, and check that no local subnet matches the plant network.

    Remote access and virtualization

  • Troubleshooting

    Using a USB programming cable inside a Hyper-V VM

    Hyper-V gives Generation 1 guests no USB passthrough, so a Siemens USB PPI or MPI cable cannot appear inside the VM. Redirect the cable's host COM port over RDP, or move to an Ethernet-to-PPI adapter with an emulation driver on an isolated subnet; fix host-to-guest networking with an internal virtual switch and static IP addresses.

    Remote access and virtualization

  • Troubleshooting

    Fixing slow automation VMs on a Windows 11 host

    The usual cause is the Microsoft hypervisor layer under VMware, confirmed by the turtle icon in the status bar. Turn off Memory Integrity, disable Virtual Machine Platform and Windows Hypervisor Platform, run bcdedit /set hypervisorlaunchtype off, reboot, and rerun the same workload — with IT approval on a work machine. Guest memory is ruled out: 16 GB did not help, and working setups run smaller allocations.

    Remote access and virtualization