Greetings, I am faced with the task of supporting both older Firmware Version 1756 ControlLogix machines in RSLogix 5000 and newer versions in Studio 5000. To streamline this process, I utilized a concurrent license to set up a 'Windows XP mode' virtual machine (VM) in Hyper-V on a Windows 10 64-bit host. Within this setup, the VM host serves as the FactoryTalk Activation Manager server while the VM guest functions as the FactoryTalk Activation Manager client. After installing versions 10, 11, and 17 (in chronological order) and RSLinx to ensure compatibility, I encountered an issue. Although the FactoryTalk Activation Client on the VM successfully connected to the FactoryTalk Activation Manager on the host and validated the RSLinx license, it failed to obtain a license for RSLogix. Has this dilemma been faced by anyone else? When I reached out to Allen Bradley for assistance, their reluctance to address VM-related issues was evident. Despite researching various forums, I have not come across a similar issue. It seems possible to configure this setup successfully, but the solution eludes me. If anyone has insights on resolving this matter, I would greatly appreciate it!
I wholeheartedly endorse the use of a virtual machine (VM); however, I have exclusively utilized VMWare rather than Hyper-V. With VMWare, I simply set up FT Activation Manager on both the host and guest, connecting the guest to the host through a host-only network. This configuration seamlessly operates without utilizing the license until the software is accessed.
I would like to clarify that the screenshot shown is from rslogix being open. It indicates that I am currently in a grace period where the available license does not seem to be recognized as applicable. Instead, it is being identified as a generic license on the virtual machine guest.
It appears that the XP image is using an outdated version of FTAM. To resolve this issue, consider updating to the latest XP-compatible version. Also, ensure that Windows Firewall is not blocking any required ports.
At my previous workplace, we successfully implemented this process after some trial and error by my colleague. To optimize your Hyper-V server, locate the activation files and ensure your Factory Talk Activation Server is directed to the correct location. On the client side, run the Activation Manager and specify the Hyper-V license location. It may be necessary to grant the laptop access on the Hyper-V server. - James.
Can the Factory Talk Activation Manager be installed separately from installed RSLogix versions? This feature came as a surprise to me, but I'm eager to try it out.
It sounds like a tricky situation you're dealing with! I’ve encountered similar issues with VM configurations and licensing before. One thing to double-check is whether the virtual machine's network settings allow proper communication with the host—especially if there are firewall settings that could block the licensing protocols. Also, it might help to run the VM with the same user privileges as the host to see if that resolves any licensing conflicts. If not, the FactoryTalk Activation Manager might require specific configurations for older versions in a VM setup, so consulting the user guides for those versions might offer some clues. Keep us posted on your progress!
It sounds like you've put in a lot of effort to set up your virtual environment! I had a similar issue once where the licensing just wouldn't cooperate in a VM setup. Have you checked if the license files are correctly linked to the VM's network settings? Sometimes, it helps to ensure that the VM is on the same subnet as the host for better communication. Also, don’t forget to run both the VM and the FactoryTalk Activation Manager with the same permissions—administrative rights sometimes make a difference. Good luck, and I hope you get it sorted!
âś… Work Order Management
âś… Asset Tracking
âś… Preventive Maintenance
âś… Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The setup involves using a virtual machine (VM) in Hyper-V on a Windows 10 64-bit host to support both older Firmware Version 1756 ControlLogix machines in RSLogix 5000 and newer versions in Studio 5000. The VM host serves as the FactoryTalk Activation Manager server, while the VM guest functions as the FactoryTalk Activation Manager client.
Answer: Answer: Although the FactoryTalk Activation Client on the VM successfully connected to the FactoryTalk Activation Manager on the host and validated the RSLinx license, it failed to obtain a license for RSLogix.
Answer: Answer: The original poster mentioned reaching out to Allen Bradley for assistance, but encountered reluctance in addressing VM-related issues. Despite researching various forums, no similar issue has been found.
Answer: Answer: While the solution to the problem remains elusive for the original poster, it seems possible to configure this setup successfully with the right insights or assistance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.