Softlock vs. Hardlock Licensing Systems - DR

---

Understanding Dietrich's Softlock and Hardlock Licensing Systems

INSTRUCTION TYPE: Overview INSTRUCTION TITLE: Softlock vs. Hardlock Licensing Systems CATEGORY: License Management OBJECTIVE: Learn the key differences between Dietrich's softlock and hardlock licensing systems, including deployment considerations, limitations, and best practices.

PREREQUISITES:

• Basic understanding of software licensing systems

• Access to Dietrich's licensing documentation

EXPERTISE LEVEL: Intermediate

PARAMETERS:

• Softlock Licenses: Software-based licensing system

• Hardlock Licenses: Hardware-based licensing system (Legacy Sentinel and WiBU CodeMeter)

---

STEPS:

1. License Types

Softlock Licenses:

• More convenient to deploy.

• May experience operational interruptions if activated and deactivated repeatedly.

• Not recommended for production environments where consistent access is critical.

Hardlock Licenses: Two types are supported:

1. Legacy Sentinel Hardlocks:

   • Requires specific Windows driver installation.

   • Limited ongoing support.

   • Not recommended for new deployments.

2. Current WiBU CodeMeter Hardlocks:

   • Native Windows driver support.

   • Standard deployment option for new installations.

   • Ships from Germany.

   • License file installation handled by North American support staff.

---

2. Deployment Considerations

Hardware Requirements:

• WiBU CodeMeter hardlocks use built-in Windows drivers.

• No additional driver installation required.

• Physical USB port access needed.

Enterprise Deployment:

• Organizations can implement a hard-lock server on their premises.

• Enables self-management of license activation/deactivation.

• Recommended for organizations requiring license mobility.

---

3. Known Limitations

License Recovery:

• No recovery procedure exists for hard-locks taken by departing employees.

• Organizations should implement internal processes to retrieve hard-locks before employee departure.

• Physical possession of the hard-lock is required for license deactivation.

License Management:

• License files are stored directly on the hard-lock device.

• Software can only be disabled when properly deactivated.

• License transfer requires physical access to the hard-lock.

---

4. Best Practices

• Maintain an internal inventory of assigned hard-locks.

• Implement checkout procedures for hard-lock devices.

• Include hard-lock return in employee off-boarding procedures.

• Consider implementing a premises-based hard-lock server for improved license control.

---

EXPECTED RESULTS:

You will understand the differences between softlock and hardlock licensing systems, their deployment requirements, limitations, and best practices for managing licenses effectively.

---

COMMON VARIATIONS:

• Some organizations may use a mix of softlock and hardlock systems depending on their needs.

• Legacy Sentinel hardlocks may still be in use in older deployments.

---

TROUBLESHOOTING:

• Issue: Hardlock not recognized by the system.

  • Solution: Ensure the USB port is functional and the hardlock is properly connected.

• Issue: License file installation fails.

  • Solution: Contact North American support staff for assistance.

---

FOLLOW-UP ACTIONS:

• Explore setting up a hard-lock server for enterprise deployments.

• Review internal processes for hard-lock management and employee off-boarding.

• Contact support for further assistance with deployment or licensing issues.

---

QUERY EXAMPLES:

• "What are the differences between softlock and hardlock licenses?"

• "How do I set up a hard-lock server for my organization?"

• "What should I do if an employee leaves with a hard-lock device?"

---

SUPPORT:

For hard-lock deployment and license file installation assistance, contact North American support staff.

---