You are here: Managing Entitlements > Checking in C2V File

Checking in C2V File

This section is relevant only for Sentinel LDK Products/Entitlements.

The Check in C2V pop-up enables you to process and store the Sentinel security key information that is contained in a Customer-to-Vendor (C2V) file. This information can be used in connection with Protection Key Update orders.

In addition, it enables you to format a key, or to generate a file that you can send to a Customer to format a key that is already deployed.

To Check in C2V Data

Removing/Applying Pending Updates

If previous updates are pending for a C2V file then you need to remove or apply these before applying new updates.

To remove/apply pending updates:

  1. Select a C2V file and click Check In.
  2. If previous updates are pending for the C2V file, "You have # pending updates" message is displayed. You will need to apply or remove the pending updates.

    1. To remove all pending updates, click Remove.
    2. To apply pending updates
      1. Click View. The Pending Updates dialog box appears.

      2. Select the Product Key and click Generate to generate the V2C file for the pending updates.

Formatting a Sentinel Protection Key

Formatting a key erases all license and memory data stored in the key and resets the data for that key in the EMS database. Formatting can be applied in the following ways:

To format a locally connected Sentinel HL key:

When a Sentinel HL key is received from a customer, you need to check in the information, in order to make the data in the key available to Sentinel EMS. Next you can format the key.

To generate an update file (V2C) for formatting a remote Sentinel protection key:

When a C2V file is received from a Customer, you need to check in the information, in order to make the data in the file available to Sentinel EMS.

To apply the Format Key file to a Sentinel protection key at the end-user site:

Enabling Licenses that have been Disabled due to Clone Detection

If Sentinel EMS detects that the licenses for one or more applications that are locked to a Sentinel SL Legacy key are running on a cloned machine, those applications will be disabled until the disabled licenses are cleared from the Sentinel SL Legacy key and new licenses applied.

In order to clear disabled licenses, you can use the Clear Cone feature in the Check in C2V process to generate a special V2C file.

Clearing a Sentinel SL Legacy key does not format the key.

To create a V2C file to clear a Sentinel SL Legacy key that has been disabled due to clone detection:

  http://www.safenet-inc.com/Support
 
© Copyright 2014, SafeNet, Inc. All rights reserved. Sentinel EMS for Sentinel LDK v.7.3