SCSM Strong Name Signature: Sealing a Management Pack

Generating a Strong Name Key File to Seal a Service Manager Management Pack

If you’re building custom management packs for System Center Service Manager (SCSM), you’ll need to seal them with a strong name signature before they can be properly versioned and safely referenced by other management packs — an unsealed management pack can’t be incrementally updated without breaking references to it. The key file used for sealing is generated with sn.exe, the Strong Name tool that ships as part of the Windows SDK / Microsoft SDKs, rather than anything Service Manager-specific:

sn.exe -k MyManagementPack.snk

sn.exe is typically found under your Microsoft SDKs installation folder (the exact path varies depending on which SDK version is installed — commonly somewhere under C:\Program Files (x86)\Microsoft SDKs\Windows\...\bin), so you may need to locate it first if it’s not already on your path. Keep the resulting .snk file safe and consistent across your team — every management pack you want to be able to update or reference against the same “family” needs to be sealed with the same key file, so losing it means you can’t issue an in-place update to a previously sealed management pack, only a brand new one under a different key.

Is This Still Current in 2026? (Updated for 2026)

System Center Service Manager is still a supported, maintained product — the current release, System Center 2022 Service Manager, is in Mainstream Support until April 2027 and Extended Support until April 2032, so management pack sealing with sn.exe remains a normal part of the workflow rather than something Microsoft has moved away from. sn.exe itself hasn’t changed — it’s still shipped as part of the Windows SDK / .NET Framework tooling with Visual Studio, with no deprecation notice against it. Worth noting Microsoft’s longstanding caveat that strong names provide identity, not security — they’re not a substitute for code signing if you’re distributing management packs outside your own organisation, but for the versioning/reference purpose covered above, nothing has changed.

Resources

• guide