vz2rjohnson
06-07-2011, 07:05 AM
is there a way to make custom serial number and/or subscription keys ? example one of my clients has two values that he assigns to customers when they purchase one of his products, a serial nnumber in the form of
SC-000-123-ABC (for single users) or SVC-000-1234-0987-DEFG (for volume license customers) and a special serial number format for OEMs in the format: 16699-OEN-0044501-78420 and what he calls "an authorization token" for single users it is in the form 01-200SUXXXXX-95-673 for VLCs it is in the foem #licenses-VKXXXXX-90-909 (where #licenses can be any value) and for OEMs it looks like OEM-SGX-XXXXX-89-000. in the above examples of authorization keys the 01 is a constant across all licenses for single user, the second group 200 can be replaced by any three digit number, SU is a constnat across all licenses for single user and xxxxx can be replaced by any combination of letters and numbers. the last two groups are variable values consisting of numbers. in the vlk example, #licenses is variable for the first group, the second group is VK is a constant across all volume licenses xxxxx is variable of letters and numbers and the last two groups are variable consisting of numbers. in the OEM example OEM- is a constant, SGX is variable consisting of any three character value, the final three groups are variable with the first of the three being made up of letters and numbers and the final two being made up of only numbers. Ok now with all the examples and breakdowns out of the way, the question is can sb7 generate these two values as serial number and subscription keys, validate them at install time and then write them to the regestry, thus "authorizing" the software to run and updates to function so long as those two values are still in place.
SC-000-123-ABC (for single users) or SVC-000-1234-0987-DEFG (for volume license customers) and a special serial number format for OEMs in the format: 16699-OEN-0044501-78420 and what he calls "an authorization token" for single users it is in the form 01-200SUXXXXX-95-673 for VLCs it is in the foem #licenses-VKXXXXX-90-909 (where #licenses can be any value) and for OEMs it looks like OEM-SGX-XXXXX-89-000. in the above examples of authorization keys the 01 is a constant across all licenses for single user, the second group 200 can be replaced by any three digit number, SU is a constnat across all licenses for single user and xxxxx can be replaced by any combination of letters and numbers. the last two groups are variable values consisting of numbers. in the vlk example, #licenses is variable for the first group, the second group is VK is a constant across all volume licenses xxxxx is variable of letters and numbers and the last two groups are variable consisting of numbers. in the OEM example OEM- is a constant, SGX is variable consisting of any three character value, the final three groups are variable with the first of the three being made up of letters and numbers and the final two being made up of only numbers. Ok now with all the examples and breakdowns out of the way, the question is can sb7 generate these two values as serial number and subscription keys, validate them at install time and then write them to the regestry, thus "authorizing" the software to run and updates to function so long as those two values are still in place.