Is there anyone here with experience managing an activation server? Our plant's IT department is responsible for managing our server, which is currently running on version 4.xx. We recently updated our maintenance laptops to Studio 5000 v34, which also updated FTAM to version 5.xx. However, we are now facing activation issues as our laptops are not able to activate using the server. A message indicates that the server needs to be on version 5.00 or higher. Despite the need for an update, our IT department is reluctant to update the server, citing concerns that our plant's 'legacy' equipment may not be compatible with the newer version. In the past, I have successfully had them update the server for the same reason without any issues. I fail to see any potential issues that may arise from upgrading the server from v4.xx to v5.xx. Does anyone have any insights on this matter? Thank you.
If you own multiple activations, it is likely that you have a Rockwell Tech Connect support contract. Contact Tech Connect to inquire about the necessary system requirements for installing v5 of the activation server software. This information may also be available on the Rockwell website. It is important for customers to know the specific system requirements, such as the Windows version needed. Unfortunately, I cannot search for this information at the moment as I do not have access to my laptop.
Remove version 5.xx from your workstation and upgrade to the newest release of version 4.xx. This temporary solution will work well until you complete the upgrade of your license server. Additionally, I have never encountered any issues with updating the license server using older software versions.
In my previous experience, I have encountered challenges with Factorytalk Activation Manager when older versions of the FTAM Client are not able to communicate effectively with the FTAM server due to significant version differences. To resolve this issue, I found it beneficial to update the clients to align with the server version. Fortunately, this upgrade process alleviated most major issues. I would suggest utilizing Wireshark on the licensing server to track the number of connected clients. This can be done through the Resource Manager or the FTAM settings. By monitoring the IPs connected to the server, you can identify which ones to focus on during the upgrade process.
tlf30 recommended uninstalling version 5.xx from the workstation and installing the latest version of 4.xx as a temporary solution until the license server upgrade is complete. He also mentioned that he has not encountered any problems with updating the license server using older software. Thank you for the suggestion, I will attempt a downgrade on one of my laptops using FTAM.
I've dealt with similar issues in the past. While it's true that legacy equipment can sometimes have compatibility issues with newer software versions, in my experience, the benefits of updating typically outweigh the risks. Studio 5000 v34 demands an activation server of v5.00 or higher and keeping your server at v4.xx may pose more significant operational risks moving forward, especially if the server fails to activate your maintenance laptops. However, to mitigate the risk, I would suggest running a test environment first. If possible, update a clone of your current server to v5.xx, then try running all processes with the 'legacy' equipment to ensure there's no disruption before applying the changes to the active server. Good luck!
I've had similar issues in my own workplace when it comes to updating servers, and it seems like your IT department's concerns about 'legacy' equipment are quite common in these situations. Here's a suggestion: Have them create a back up of your current server before attempting the update to the newer version. This way, if any compatibility issues do arise with your legacy equipment, you could simply revert back to the older version. Additionally, consider running a pilot test on a small scale before changing the whole infrastructure - this could help address their worries in a more controlled manner.
I've run into similar situations at our facility. Generally, backward compatibility is a standard feature with many server updates, especially in the case of incremental versions like from v4.xx to v5.xx. I understand your IT department's concerns, but the need to stay up-to-date often outweighs potential compatibility issues. Perhaps suggest setting up a sandbox environment to test the new server version? This way, you can ensure all your 'legacy' equipment runs smoothly on the new version without disrupting the live environment. It's a bit of work but could smooth the way for the necessary update and provide peace of mind for your IT team.
I agree with your inclination to update the server, however, the IT department's concerns about compatibility with legacy equipment are valid as well. It's a delicate balance to maintain between staying current and ensuring the smooth operation of existing systems. A possible workaround could be to run a parallel server for the newer laptops while maintaining the old server for the legacy equipment. This might put some extra burden on your IT department but it can prevent potential compatibility issues. It'd be wise to also ask the vendor about any known issues between the legacy equipment and the newer software version for better preparedness.
It sounds like a frustrating situation! If I were you, I’d suggest organizing a meeting with your IT department to discuss the potential risks versus the benefits of upgrading the activation server. Bringing in specific examples of past successful updates could help ease their concerns about compatibility with legacy systems. Plus, maybe you can involve a representative from the vendor or a tech expert who can address their worries directly and provide evidence that upgrading usually resolves these activation issues without impacting older equipment. Sometimes, having an outside voice can really help clarify things!
It sounds like you're in a bit of a tough spot! Given that your maintenance laptops are now on version 34 and need the activation server at version 5.00 or higher, it definitely makes sense to push for the upgrade, especially since you've had success with it before. One thing you might want to do is gather some documentation on any compatibility tests that show the legacy equipment can handle the new server version. Sometimes IT departments are more responsive when they see cold hard facts or case studies from similar setups. Additionally, perhaps propose a phased approach or a testing environment first—this could alleviate some of their concerns about compatibility while still moving the project forward. Good luck, and I hope you can sort this out soon!
✅ 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: The issue arises because Studio 5000 v34 requires FTAM server version 5.00 or higher for activation, which is not compatible with the current server version.
Answer: The IT department is concerned about the compatibility of the newer version with the plant's 'legacy' equipment, fearing potential issues with the upgrade.
Answer: The individual asking the question has successfully had the server updated in the past without any issues, and fails to see any potential problems that may arise from the upgrade.
Answer: Seek advice or experiences from individuals who have encountered similar activation issues when upgrading FTAM servers to newer versions for compatibility with software updates like Studio 5000 v34.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.