02.04.2013 Views

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 6 – Secure Remote Updates<br />

Contents Glossary Index Troubleshooting<br />

Generating Update Codes<br />

162 <strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> Developer’s <strong>Guide</strong><br />

<br />

You can generate update codes to activate features/applications, or new<br />

license additions remotely. For a bidirectional update you must have<br />

obtained a request code from the customer6 who has requested remote activation<br />

of features/applications.<br />

The following section explains the <strong>Sentinel</strong> Key details you must know for<br />

generating an update code file (.upw) or a new license addition file (.nlf):<br />

1. Remote Feature/License Update: Requires generating a .upw,<br />

update code file from the Key Activator tab of the Toolkit. The<br />

update file can be generated using either of the following methods:<br />

Bidirectional Update: Requires the following files to generate the<br />

.upw, update code file:<br />

A Request Code (.req) file from your customer<br />

Unidirectional Update: The unidirectional update could be one of<br />

the following types:<br />

Unidirectional Single Target Update: Requires the <strong>Sentinel</strong><br />

Key Serial Number targeted for a single target update.<br />

Unidirectional Broadcast Update: Requires the common<br />

Developer ID for all the <strong>Sentinel</strong> <strong>Keys</strong> targeted for a unidirectional<br />

broadcast update.<br />

Note: In all of the above modes, the cheat counter value can be specified in the<br />

Cheat Counter (only for non-RTC keys) field, before generating the<br />

*.nlf file. The update packets for LKDT packet is also integrated with the<br />

*.nlf file.<br />

2. Remote License Addition: Requires generating a .nlf, new license<br />

addition file from the Export-File Manager of License Manager in<br />

Toolkit.<br />

6. Your distributors might also require update codes to remotely update distributor<br />

keys with them.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!