New v5.3 Licensing Change

Ask general questions here.
User avatar
Posts: 1336
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

New v5.3 Licensing Change

Post by Ciege » Thu Jan 15, 2015 4:33 pm

Hi all,
Just received an email about the change in licensing starting with 5.3 in regards to virtual environments. This change is not trivial for us. Our existing 7 Premium licenses are all node locked and are all used on a virtual machine. At a minimum, the reason for using a virtual machine and not our physical machine is so that we can revert our test environments to clean states and test our different AUTs with clean environments. This is something that is not possible on a physical machine.

Forcing us to modify our licenses from node locked to floating will effectively double the cost of our Ranorex licenses. This is unacceptable, especially considering the growth we anticipate here within the next 2 years. This doubling of cost will force us to re-evaluate continued use of Ranorex as our automation solution going forward.

I've been a Ranorex user (and evangelist) for many years. Unfortunately this feels like a poorly thought out cash grab and does not sit well with me.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!


User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: New v5.3 Licensing Change

Post by Support Team » Fri Jan 16, 2015 5:01 pm

Hello Ciege,

I would like to write a short statement to your post.
In general we prefer to discuss questions like this by email.
One of my colleagues already contacted you by email and it would be great if you could respond to him directly.

In general the problem is that the way how Ranorex Node-Locked licenses are used has changed in the past few years. With the new version we just want to prevent misuses of Node-Locked licenses. Actually it was not allowed in the past, but there was no technical limitation.
I think it is a common approach to disallow Node-Locked licenses on virtual machines.
I hope you can understand our view and we are looking forward to discuss this in detail with you by email.