Check Draftable Legal activation across machines

Use the Windows Registry to check saved activation markers and configured product keys. This check does not verify current licence validity.

Use the Windows Registry to check for a saved Draftable activation marker and configured product keys. This check does not verify whether a licence is currently valid.

This article explains:

• Where to look in the registry for user settings and policy keys.
• What each value means, including what it cannot tell you about activation.
• How to use a PowerShell script to read these locations locally or on remote PCs.

​

How Draftable decides which key to read

Draftable reads the recorded activation key in the user’s settings first, then product keys supplied through user policy and machine policy. A configured product key does not prove successful activation. This applies to both installer types.

​

Registry locations and meanings

Location	Value	Meaning
HKCU\Software\Draftable\Compare	ActivatedProductKey	Records a prior activation for this user, for either installer type. Does not verify current licence validity.
HKCU\Software\Policies\Draftable\Compare	ProductKey	Supplies a product key through user policy. Does not confirm activation.
HKLM\Software\Policies\Draftable\Compare	ProductKey	Supplies a product key through machine policy. Does not establish that every user has activated.

Example of a saved activation marker in user settings

To supply a product key before first launch, set ProductKey in one of the policy locations above.

​

Manual, one-off check

1. Open Registry Editor

   Press Win + R, enter regedit, and press Enter.

2. Find the registry key

   Browse to the relevant path in the table above. HKCU refers to the account running Registry Editor.

3. Interpret the values

   Look for a non-empty ActivatedProductKey in user settings as a saved activation marker. A configured ProductKey alone does not determine activation. Record only whether values are present, not the product keys themselves.

​

Automated audit with PowerShell

Save this as Check-DraftableActivation.ps1 and run it in Windows PowerShell 5.1. It defaults to the local machine and uses direct registry access, so local checks do not require the Remote Registry service. Reading other users’ loaded hives may require additional permissions.

For remote PCs, add -ComputerName. Remote checks require network connectivity, Remote Registry access, and suitable permissions.

<#
  Check-DraftableActivation.ps1
  Purpose: Report saved activation markers and product-key presence only.
  Usage:
      .\Check-DraftableActivation.ps1               # local machine
      .\Check-DraftableActivation.ps1 -ComputerName PC01,PC02
#>

param(
    [string[]]$ComputerName = $env:COMPUTERNAME
)

function Get-DraftableStatus {
    param($Computer)

    function Read-DraftableKey {
        param($BaseKey, $Path, $Scope, $UserSID)

        $sub = $BaseKey.OpenSubKey($Path)
        if ($null -eq $sub) { return }
        try {
            $pending = $sub.GetValue('ProductKey', $null)
            $activated = $null
            $recorded = $null
            if ($Scope -eq 'User settings') {
                $activated = $sub.GetValue('ActivatedProductKey', $null)
                $recorded = -not [string]::IsNullOrEmpty([string]$activated)
            }
            [pscustomobject]@{
                Computer = $Computer
                UserSID = $UserSID
                Scope = $Scope
                RegistryPath = $(if ($Scope -eq 'Machine policy') { 'HKLM\' + $Path } else { 'HKU\' + $Path })
                ActivationRecorded = $recorded
                ProductKeyPresence = $(if ([string]::IsNullOrEmpty([string]$pending)) {
                    'absent'
                } else {
                    'present'
                })
            }
        }
        finally {
            $sub.Dispose()
        }
    }

    $local = $Computer -in @('.', 'localhost', $env:COMPUTERNAME)
    foreach ($hiveName in @('LocalMachine', 'Users')) {
        $base = $null
        try {
            $hive = [Microsoft.Win32.RegistryHive]$hiveName
            if ($local) {
                $base = [Microsoft.Win32.RegistryKey]::OpenBaseKey(
                    $hive, [Microsoft.Win32.RegistryView]::Default)
            } else {
                $base = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey(
                    $hive, $Computer)
            }
            if ($hiveName -eq 'LocalMachine') {
                Read-DraftableKey $base 'Software\Policies\Draftable\Compare' 'Machine policy' $null
            } else {
                foreach ($sid in $base.GetSubKeyNames()) {
                    if ($sid -notmatch '^S-1-5-21-(\d+-){3}\d+$' -and
                        $sid -notmatch '^S-1-12-1-(\d+-){3}\d+$') { continue }
                    Read-DraftableKey $base "$sid\Software\Draftable\Compare" 'User settings' $sid
                    Read-DraftableKey $base "$sid\Software\Policies\Draftable\Compare" 'User policy' $sid
                }
            }
        }
        catch {
            Write-Warning ("Could not read {0} on {1}: {2}" -f $hiveName, $Computer, $_.Exception.Message)
        }
        finally {
            if ($null -ne $base) { $base.Dispose() }
        }
    }
}

$results = $ComputerName | ForEach-Object { Get-DraftableStatus $_ }
$results | Format-Table -AutoSize

What the script does

• Reads machine policy and supported loaded user hives under HKU, including user settings and user policy. It excludes system/service and _Classes hives; users whose hives are not loaded are not included.
• Reports ActivationRecorded = True for a non-empty ActivatedProductKey in a user-settings row, or False otherwise. A blank value on a policy row means activation is not assessed there. This checks for a saved marker, not the validity of the key or licence.
• Reports ProductKeyPresence = present or absent for the ProductKey value at that exact RegistryPath. Product keys are never printed.
• Produces no row for a missing path. Read failures produce warnings and can leave the results incomplete.

To create a spreadsheet report, add this line after the script’s final line. Export the unformatted $results, not the Format-Table output. The CSV contains key presence indicators, not product keys. Use it when you need full paths, which narrow terminals may truncate.

$results | Export-Csv .\DraftableActivationAudit.csv -NoTypeInformation

​

Troubleshooting

Symptom	Possible cause	What to check
No row for a user or policy path	The path is absent, the user’s hive is not loaded or is excluded, or a read failed	Check the relevant path, loaded user hives, and any warnings. An empty table does not prove non-activation.
Warnings, errors, or a partial table	A registry read failed; the script skips the rest of that hive’s processing after an exception	Resolve the reported access or read error, then rerun. Treat partial results as incomplete.
Remote target returns access or connection errors	Remote Registry is unavailable, network access is blocked, or permissions are insufficient	Check connectivity, the target’s Remote Registry service, and your access rights. Local mode does not use Remote Registry.

​

Next steps or further questions?

• Use the script to review saved activation markers and configured product keys, keeping its coverage limits in mind.
• Pair this check with Draftable’s Group Policy templates to automate licence rollout and other settings.
• For an organisation-level usage report on request, see Configure an Organisation Identifier; the report does not verify each user’s licence.
• Still have questions? Contact [e-mail].