KMScript.comDIGITIZED as KMScript
- Intro
- KMSZ is compiled script from KMS by author with or without a lock.
- the author can own differentlocks by Developer ID.
- the author can made many key from kmscript.com for that locks.
- the key only open it's lock, can't use for other lock.
- to run a locked KMSZ, the user must require a key for unlock from author.
- the key will bind the machine when unlock a KMSZ, it's can't be use again.
- multiple software on this machine run same time require multiple different keys.
- repeat key may black list forever.
- a valid key bind work for all KMSZ if same lock.
- the author can use same lock for next version of KMSZ(or new function of KMSZ)
- the key has a 30-day validity period after the first use and the key will become invalid after expiration.
- this period is not affected by the time zone and time of the user's current device.
- a same lock unused key can use for extend old key, the old key extended30 days.
- author can extend a key for 10 years before send to user(only ARMBox, because bind when use).
- the key will be recycled to the next developer if it has not been used after 365 days from its creation time.
- User
- ready
- make sure the KMSZ is locked, if not you don't need the key
- make sure the machine is current kmscript for bind
- make sure the time current machina is correct
- each locked KMSZ first run will do key activate, that need online, aftet that can switch to offline
- if KMSZ use any cloud function, still need online
- all cloud function will check the key is valid
- apply
- config the KMSZ wish to run in "Startup Script" by W3Config in a target kmscript
- click the menu "Node Manage" enter node manager
- in top, select the target, for example 127.0.0.1 is local or target node IP. you will see

- check the "Key Required" is "Yes" if not that KMSZ don't need the key
- check the "expire date" is after now, for example(the time format may different look like depends you locale):
- 1970-01-01 07:59:58 mean the key already expire
- 1970-01-01 other time mean the key invalid
- get the key from author
- select "use new key" and enter the key for apply
- or select "extension current key" for extend the current key
- extend current key got +30 days. if current key already expired will got 30 days after now not it's last time
- rememeber
- the key become to invalid if hardware changed! including the CPU, GPU, memory, network card
- Developer
- ready
- make sure the time current machina is correct
- remember if function with cloud flag you want use that need a valid key, so user need online

- the cloud function code in server, so even the kmscript or KMSZ cracked/hacked still no function
- to protect you KMSZ you may need an cloud call, the succeed and failed both goto right step
- you need register as developerto get the ID and developer key, all lock and it's key own by this ID
- only key bind the machine, the ID and locks not, you can use on other machine
- release
- in release page, you can select an lock or let free(no lock)

- you can click "reload the locks" to list the locks you have
- click "new lock" request an lock from kmscript.com
- if "disabled the lock" click, the lock selected and all it's key will disabled, this can't undo.
- an lock disabled, all KMSZ locked by this lock can't run anymore, because all key(of this lock) are disabled.
- but you can release the KMS with new lock to make new KMSZ.
- you can request an lock for public test only, after all you can disable that lock
- manager
- in "Keys Manage" you can list the keys(of lock you selected) you have

- the type "key free" mean list unused only
- click "create keys" you can made the keys for lock you selected
- in the table
- you can double click the "Key" to extend the field, then copy to user
- or double click all you want, then copy all to save
- the create_flag is flag you set in you create the key, this flag keep forever, so don't leak something you don't want
- if used_for have the value, mean the key is used for, if not it self mean used for extend other key
- if key used in user_ip you can only see first 2 part of ip address for privacy reason, for example: 123.234.*.*
UI: li_tag