I am currently facing a dilemma as I attempt to set up a virtual machine for various versions of RSlogix 5000 and Studio 5000. While I have always been a fan of using a VM for troubleshooting and offline work, I have encountered some compatibility issues along the way. Specifically, Windows 10 had trouble installing version 27, with Rockwell confirming that it is not supported. Surprisingly, Windows 7 seems to work for most versions except the later ones. I am curious if anyone else has dealt with similar challenges and if there are any workarounds available. I would prefer to have all versions of Studio and Rslogix 5000 on a virtual machine rather than on my host machine. Any advice or insights from those who have experienced similar headaches would be greatly appreciated.
I have Windows 10 VM with every version of software installed from 7 to 35. Here are some valuable suggestions for a smooth installation process: 1. To avoid issues, install the software in reverse order starting from the highest version to the lowest. (Contrary to Rockwell's recommendation) 2. For older versions like 20 and below, use an installer that can install multiple versions at once. This will ensure all necessary components, including dotnet 1.0, are properly installed. 3. Remember to reboot your system whenever prompted. 4. Always select "activate later" during the installation process. 5. If any installation errors occur, particularly due to Rockwell's shortcomings, uninstall newer versions, install the older version, and then reinstall any missing components using the v35 installer. 6. Be patient during installations as they can be time-consuming. Following these steps, you can set up a VM or workstation with all versions in about a week. Pro Tip: When installing Studio 5000 Application Code Manager, be aware of a bug in the SQL Express 2016 installer. Uninstall the older version of SQL Client (2012) and ODBC driver for SQL Server from the add/remove programs section before retrying the installation. This will ensure a successful installation without any issues. ~Trevor
The conflicting statements from Rockwell and the distributor have been a source of frustration. I have poured countless hours into creating a comprehensive virtual machine (VM) with all versions to streamline my service work. I rely on having access to every controller without any technical issues. Once I successfully create a fully functional VM with all versions, I will definitely back it up. Your advice is appreciated, and I am determined to give it another try.
As a controls engineer for a company servicing numerous customers using different software versions, I understand the challenges of updating systems without disrupting operations. How much storage space does your VM require to accommodate all those versions? I typically allocate 120GB for my VMs, but I anticipate needing more space due to the variety of versions. Expanding VM disk space can be a cumbersome process. - Mitch.
I agree with tlf30 that building an all versions VM is feasible. Follow his advice and troubleshoot any installation issues that may arise. Common problems include encountering the "there is a newer version installed" error for a software component, as well as difficulties with DotNet 1.0 installation. My VM typically ranges from 160 to 200 GB in size, depending on the level of defragmentation. It includes various software versions like 5000 software, PLC 5 & 500, Studio SE V12, along with other vendor applications and utilities. Regularly clean up the VM by utilizing Devices -> Hard Disk, Defragment, and Compact features to minimize disk space usage. I recommend configuring a 300 GB hard drive that grows as needed, instead of allocating the entire space upfront. This approach reduces the time required to back up the VM. Additionally, it is possible to Expand an existing VM hard drive through Devices -> Hard Disk settings. If using snapshots in VMWare Pro, please note: 1. Defragment and Compact functions are not compatible with snapshots. 2. Reverting to a snapshot can disrupt Rockwell Codemeter activations hosted within the VM, requiring reactivation. Rockwell recently made changes to this behavior, impacting the functionality of snapshots. This inconvenience diminishes the benefits of using snapshots in the VM environment.
To ensure the smooth activation of all my software, I rely on using a dongle and highly recommend it. By using a dongle, I can easily transfer installations to another computer without worrying about activation limits. It's important to note that older versions of software may require Windows 7, and some may even run on Windows 95-98, or in some cases, only on DOS. For running DOS-based software, I utilize virtual machines for compatibility. I prioritize the safety of my data by storing everything on my personal cloud storage and regularly backing up my virtual machines, software, and projects. When it comes to installing Rockwell software, it's crucial to install older versions before upgrading to newer ones. Each version of the software installs its own driver, which can cause compatibility issues if not installed in the correct order. During a recent computer upgrade, it took me nearly two days to reinstall all necessary software. This experience taught me the importance of proper planning to avoid any downtime due to software installation issues. Remember, preparation is key! Good luck with your software installations.
I completely understand your frustration, I faced a similar issue a few months back. If you can bear the slightly slower performance, you can have a VM with Windows 7 for the older RSlogix versions while maintaining another VM with Windows 10 for the newer ones. Another approach could be to create separate virtual hard drives for each version. This won't save you from the limitation of the host OS, but this method always worked for me when dealing with differing system specifications. And remember, Rockwell technical support is your friend, they can often provide surprising solutions.
I was actually in the same boat not too long ago and I found a workaround that might help you. I decided to create multiple VMs, each with a different operating system suited for the specific version of RSLogix or Studio 5000 I needed. For instance, one VM with Windows 7 for the older versions, and another with Windows 10 for the more recent ones. I understand it might take a bit more of storage space, but this method gave me an efficient and manageable way of working with these different versions without encountering compatibility issues. You might give this a try.
✅ 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: Yes, there are compatibility issues reported, especially with certain versions of Windows and the software applications.
Answer: While Windows 7 seems to work for most versions except the later ones, Windows 10 had trouble installing version 27, which is confirmed as not supported by Rockwell.
Answer: Yes, other users have encountered similar challenges, as mentioned in the discussion thread. It seems to be a common issue.
Answer: Workarounds may include using different Windows versions, seeking advice from the software providers, or exploring alternative virtual machine software.
Answer: Having the software on a virtual machine can be beneficial for troubleshooting and offline
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.