Orchestrator License Expired After Database Migration? Here's Why (and How to Fix It!)

Updated: 23 Jan, 2025 • 0 • min read

Table of Contents

Orchestrator License Expired After Database Migration? Let’s Fix It!¶

Orchestrator License
image just illustration

So, you migrated your Orchestrator database to a shiny new SQL Server instance, and now your Orchestrator Designer is throwing a fit about an expired license key? Even though you entered the right key? Don’t worry, we’ve got you covered. This guide will walk you through why this happens and how to get things back on track.

The Problem: The Case of the Vanishing License¶

This frustrating issue usually pops up after migrating an Orchestrator database from one SQL Server instance to another. You open Orchestrator Designer, ready to automate the world, and BAM! “License key expired.” You dutifully enter your perfectly valid license key, hit “OK,” and… the same message stares back at you. It’s like a bad IT joke.

The Culprit: The Service Master Key (SMK)¶

The root of the problem lies with the Service Master Key (SMK). Think of the SMK as the guardian of your database’s secrets. When you migrate your database, the SMK needs to come along for the ride. It needs to be backed up from the original server and restored on the new one. If this crucial step is missed, or if the SMK wasn’t backed up in the first place, the connection between your license key and the database breaks down, leading to the “expired license” error.

The Solution: Restoring Order (and Your License)¶

Here’s the step-by-step guide to fixing this licensing headache:

Stop the Orchestrator Management Service: Before making any changes to the database, it’s essential to stop the Orchestrator Management service. This prevents any conflicts or data corruption.
Open Your Database: Connect to your Orchestrator database on the new SQL Server instance using SQL Server Management Studio (SSMS) or your preferred database management tool.
Prepare a New Query: Open a new query window within your database tool, and double-check that the correct Orchestrator database is selected.
Execute the Magic Commands: Here comes the fix. You’ll need to execute two SQL commands, one at a time. These commands essentially remove the old, broken key and create a brand new one:
- Delete the Old Key:
```
[Microsoft.SystemCenter.Orchestrator.Cryptography].[DropOrchestratorKeys]
```
- Create the New Key:
```
[Microsoft.SystemCenter.Orchestrator.Cryptography].[CreateOrchestratorKeys]
```
Restart the Orchestrator Management Service: Now that the key situation is resolved, restart the Orchestrator Management Service.
Enter Your License Key (One Last Time): Open Orchestrator Designer. You’ll be prompted for your license key again. Enter it, and this time, it should be accepted without any issues.

Why This Works¶

These SQL commands directly interact with the encryption mechanisms within the Orchestrator database. DropOrchestratorKeys removes the existing, potentially corrupted key information. CreateOrchestratorKeys generates a fresh set of keys, allowing the database to properly associate with your valid license key.

Preventing Future Headaches¶

The best way to avoid this issue in the future is to always back up the SMK when migrating your Orchestrator database. This ensures a smooth transition and avoids any licensing hiccups. Consider this as part of your standard migration checklist.

Need More Help?¶

This fix generally resolves the “expired license” issue after database migration. However, if you’re still encountering problems, double-check that the correct license key is being used and that the Orchestrator Management Service is running correctly.

Digging Deeper¶

This issue stems from how Orchestrator handles encryption and licensing within its database structure. The SMK plays a crucial role in securing sensitive information, including license details. When the SMK is not properly transferred during migration, this encryption process breaks down, leading to the license errors.

Orchestrator Database Migration
image just illustration

Your Turn!¶

We hope this guide has helped you resolve your Orchestrator licensing woes. If you have any questions, further insights, or alternative solutions, please share them in the comments below! We’re always eager to learn from your experiences and help others navigate the world of Orchestrator. Let us know what other challenges you’ve faced and what you’d like to see covered next. Happy automating!

Computacionvinchi