User Tools

Site Tools


access:licensekey-rework-2018

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
access:licensekey-rework-2018 [2018/10/02 00:57]
mikeclapp [Revision 1]
access:licensekey-rework-2018 [2018/11/07 17:34] (current)
mikeclapp [Table]
Line 6: Line 6:
 **Desktop** **Desktop**
  
-  - Add Export - Sitework 3D compatible file Function+  - Add **Export - Sitework 3D compatible file** function instead of using IP Grid Compatible
   - Check for Update to be run on program start - also user command on Help - Check for Updates   - Check for Update to be run on program start - also user command on Help - Check for Updates
     - Requires checking with server for version     - Requires checking with server for version
Line 29: Line 29:
  
 **Server** **Server**
 +
 +Task list, including FingerPrinter:​ [[access:​LicenseKey-reworkd-2018-tasks|LicenseKey refactor tasks 2018]]
  
   - Server planning for rejection of of designated older versions. Faculty to designate said versions and tracking   - Server planning for rejection of of designated older versions. Faculty to designate said versions and tracking
-  - Setting up limited Company with limited user access to files for all versions. Currently we store under Current Versions of the AGTEK Corporate Company +  - Setting up limited Company with limited user access to files for all versions. Currently we store under Current Versions of the AGTEK Corporate Company ​(MC) 
-  - Creation of a Web Update page to be used for this campaign with clear messaging and direct links to versions both 64 bit and 32 bit. Not behind Firewall but set to not web index or link directly to the site.+  - Creation of a Web Update page to be used for this campaign with clear messaging and direct links to versions both 64 bit and 32 bit. Not behind Firewall but set to not web index or link directly to the site.(MC)
   - Creation of a check key status (verify? name?) for use by the desktop code to verify the current key status at a random range and generate back to desktop when the next check time will be. This is distinguished from other calls in order to log possible dual use of keys. Server will at this time just log situations where the same key number is checking in too early. The absence of a checkin would not constitute a log situation necessarily as the user could have closed the program but retained the key. Make the bounds configurable from the server.   - Creation of a check key status (verify? name?) for use by the desktop code to verify the current key status at a random range and generate back to desktop when the next check time will be. This is distinguished from other calls in order to log possible dual use of keys. Server will at this time just log situations where the same key number is checking in too early. The absence of a checkin would not constitute a log situation necessarily as the user could have closed the program but retained the key. Make the bounds configurable from the server.
   - Add support for messaging with links, basic html.   - Add support for messaging with links, basic html.
Line 41: Line 43:
  
 Check Web and mobile for compatibility. Check Web and mobile for compatibility.
 +
 +
 +Versions that will be updated
 +
 +^ Program ​       ^ New Version ​ ^ Version Cutoff (still works) ​ ^
 +| Earthwork 4D   | 1.20.2 ​      | 1.20.2 ​                       |
 +| Materials 4D   | 1.14.6 ​      | 1.14.6 ​                       |
 +| Gradework 4D   | 1.2.3        | 1.2.3                         |
 +| Trackwork 4D   | 2.15.3 ​      | 2.15.3 ​                       |
 +| Protect32 ​     | None         | Kill all                      |
 +|                |              |                               |
 +^ Not Supported ​                                              |||
 +| GradeModel ​    | 1.79.2 ​      | 1.79.2 ​                       |
 +| Material 3D    | 1.67.2 ​      | 1.67.2 ​                       |
 +
 +
 +Will ask again for clarity on GradeModel and Materials 3D. At this point I'm saying no.
 +
 +The New Version column may be redundant since it pretty much matches the cutoff version
 +
 +Cutoff date at this point is set for November 13th. 
 +
  
 ===== Revision 2 ===== ===== Revision 2 =====
Line 47: Line 71:
   - Tells and other information based on Citrix experience   - Tells and other information based on Citrix experience
   - Process limiting?   - Process limiting?
 +  - Monitoring of older versions being used and later rejected.
  
  
  
 +
 +
 +
 +
 +
 +====== Timeline ======
 +
 +  - Version - soft release web & new versions
 +  - Registered Letter - 9th
 +  - Email - October 22nd
 +  - Message
 +  - Server version Monitoring for older versions - method of reporting/​notifications
 +  - Cutoff
 +  - Messaging
  
  
Line 208: Line 247:
  
  
-** Modeling Fingerprint Scenarios **+===== New Fingerprinter Weights October 2018 ===== 
 + 
 +^ Value                ^ Weight ​ ^ Ratio  ^ Negative Weight ​ ^ Negative Ratio  ^ 
 +| Machine ID           ​| ​ 8      | .21    |  -20             ​| ​ -.52           | 
 +| Computer Name        |  8      | .21    |  -8              |  -.21           | 
 +| OS Install Key       ​| ​ 8      | .21    |                  |                 | 
 +| Hard Drive Serial 1  |  4      | .10    |                  |                 | 
 +| CPU Description ​     |  2      | .05    |  -5              |  -.13           | 
 +| OS Name              |  2      | .05    |                  |                 | 
 +| CPU Core Count       ​| ​ 2      | .05    |                  |                 | 
 +| Memory Size          |  2      | .05    |                  |                 | 
 +| BIOS Date            |  2      | .05    |                  |                 | 
 +| Total Possible ​      ​| ​ 38     ​| ​       |                  |                 | 
 +| Passing Value        |  22     ​| ​       |                  |                 | 
 + 
 + 
 +Original Spreadsheet with scenarios here: 
 + 
 +{{ :​access:​fingerprinting_values_and_scenarios.xlsx |}} 
 + 
 +{{ :​access:​fingerprinting_values_and_scenarios_-_finger_print_model.pdf |}} 
 + 
 +New concept is negative weights. Removed User ID because it isn't always available when the fingerprinter is run and could cause issues by not being available. Since the fingerprinter is really about identifying the machine not the user, it should not be part of the fingerprinter code. Instead it should be used with the time check and verify if used at all. Decisions on whether to make a username mismatch a problem for the user still needs to be decided but it is not part of the fingerprinter. 
 + 
  
  
access/licensekey-rework-2018.1538441848.txt.gz · Last modified: 2018/10/02 00:57 by mikeclapp