Licensing Requirements FAQ
Licensing requirements for:
Licensing requirements for MKS System Toolkit for Administrators, MKS Toolkit for Developers, and MKS Toolkit for Interoperability:
If you have any questions, please feel free to contact any MKS office or send email to:
tk_info@mkssoftware.com.
Client Systems
MKS Toolkit is required for each single user client, i.e. 1 license per machine.
Server Systems
MKS Toolkit is required for each user using and/or building commands and/or scripts on the server. For example, if there are a series of scripts for 20 end users to utilize, a 20 user license will be required.
Volume Licenses
MKS Toolkit volume licenses are available and start at quantity 5. For further information, please contact your MKS representative, channel partner, or send email to:
tk_info@mkssoftware.com.
If you need MKS Toolkit for installing 3rd party software such as Oracle Applications, Sun J2SE/Java 2 SDK or IBM Tivoli Systems Business Manager, and the only work being done is installation of that software by a system administrator, then a single license is required for each machine that you intend to install the software on. Further, you may not use our evaluation copy for installation or maintenance of any 3rd party software, or for any commercial use, even if you only need a single command for a single one-time-only purpose.
You may not have MKS Toolkit products installed on more machines than you have licenses for at any time. Evaluation copies are for evaluation of MKS Toolkit ONLY.
We are always more than happy to review your particular situation and help you determine the proper licensing, simply contact
tk_info@mkssoftware.com.
Licensing requirements for MKS Toolkit for Professional Developers, MKS Toolkit for Enterprise Developers, and MKS Toolkit for Enterprise Developers 64-bit Edition:
MKS Toolkit for Enterprise Developers and MKS Toolkit for Professional Developers have both development and deployment licenses. Development licenses are required for each programmer doing development work, whether on separate client systems or on a server. Deployment licenses are required for each machine, client or server, that the ported software runs on. Deployment licenses for client applications are licensed per machine and for server applications are licensed per server CPU.
These types of deployment scenarios are somewhat more complex. We are always more than happy to review your particular situation and help you determine the proper licensing, simply contact
tk_info@mkssoftware.com.
Licensing requirements for MKS X/Server:
If you have any questions, please feel free to contact any MKS office or send email to:
tk_info@mkssoftware.com.
Computer Systems
A computer system means any type of single computer or workstation containing one or more central processing units and one operating system. A license is required for each computer system upon which the MKS X/Server software is installed.
Users
A user means any individual who from time to time uses the X/Server software, provided that any individual who permanently ceases to use the software may be replaced by another individual. An MKS X/Server license is required for each individual user.
Volume Licenses
MKS X/Server volume licenses are available and start at quantity 10. For further information, please contact your MKS representative, channel partner, or send email to:
tk_info@mkssoftware.com.
You may not have MKS Toolkit products installed on more machines than you have licenses for at any time. Evaluation copies are for evaluation of MKS X/Server ONLY.
We are always more than happy to review your particular situation and help you determine the proper licensing, simply contact
tk_info@mkssoftware.com.
Licensing requirements for MKS AlertCentre:
The AlertCentre Add-on to MKS Toolkit products, as of v2.03, is a freely downloadable add-on which will default to the underlying MKS Toolkit product licensing requirements.
Licensing and MKS Preferred Customer
Subscription (PCS) for All Products:
MKS licenses are perpetual unless you have purchased a special limited license of fixed duration.
A one-year PCS subscription is included with all MKS Toolkit, MKS AlertCentre and deployment software purchases. Customers with PCS subscriptions receive technical support, updates and patches at no additional charge during the subscription period (one year) for electronic downloads and a small shipping charge if you'd like us to deliver a CD.
If PCS is not in effect, you are not entitled to support, updates or patches and may be restricted from buying new copies of the software. Again, our licenses are generally perpetual, so you may continue to use your existing licensed software long after your PCS subscription lapses under the terms of that license. Software past PCS expiration is still subject to all terms of our license with respect to restrictions on number of machines and number of users.
Once PCS lapses, you have 30 days to renew at the standard PCS renewal price without penalty. After 30 days, and for up to 2 years after it lapses, you can purchase an update at a higher price, which will reactivate PCS on your license(s) for another year. If PCS has lapsed for more than 2 years, and you have not reactivated, you will need to replace the old copy with a new license(s) if you wish to begin receiving updated software.
If your PCS has lapsed, and you wish to buy additional licenses, you must either (a) reactivate PCS on all existing licenses in your immediate organization, or (b) have an Officer of your organization certify every 6 months to MKS that the new copy purchased will not be propagated to or used by, even temporarily, licensed users of older versions, or installed on any other machines not licensed in the new purchase.
If you have more than 1 license in your immediate organization, you cannot purchase PCS for one copy. All copies must be covered under a single PCS subscription with the same expiration date. PCS on new copies you purchase can be prorated to expire at the same time your existing PCS contract expires. There are two exceptions to this policy: (a) if you certify to MKS that you are no longer using the copies licensed that you do not wish to cover, and (b) if you certify to MKS that you will not allow the new version to propagate to the other licenses that you do not wish to cover. In the latter case, the customer must describe the internal processes that will prevent this from happening, and agree to certify semi-annually the total number of copies of each version owned. All certifications must be signed by an officer of the company.
Once copies are removed from PCS, they may be reinstated under the policy noted above.
Our support policy can be found at
http://www.mkssoftware.com/support/updates.asp. Again, if you have any questions, please contact us and we will endeavor to help you.
Additional licensing information can be found in the
Product FAQ under the sub-heading "Licensing."
Don't see what you are looking for? Contact
tk_info@mkssoftware.com to get complete licensing information on all of the MKS products.
| 
