Forum Discussion

kulldeepverma's avatar
kulldeepverma
Copper Contributor
Jul 21, 2026

Changing the License Type and Key of a SharePoint Subscription Farm

Hi everyone,

I need some assistance with a licensing issue on a brand new SharePoint Subscription Edition farm. I have 6 servers total 4 Application/Search servers + 2 Web Front End/Distributed Cache servers and current state of farm is Fresh installation  no custom code or solutions, no production content web apps configured yet.

The Problem: During setup, our systems team accidentally provided a SharePoint Standard Edition product key, which I used during farm creation. We actually require Enterprise Edition, but I am unable to convert the license type through Central Administration.

  • Issue 1: When I go to Central Administration > Upgrade and Migration > Convert farm license type, the Product Key text field and the OK button are both completely grayed out and disabled.
  • Issue 2: When I go to Central Administration > Upgrade and Migration > Enable Enterprise Features and enter our Enterprise key, the process fails with an Unknown Error / SkuUpgradeJob timer job exception ("Post setup configuration failed when attempting post setup configuration task -cmd services -install -cmd installfeatures").

What I Have Tried So Far:

  1. Running PSConfig CLI: Ran psconfig.exe -cmd sku -upgrade -key from an elevated Command Prompt. It fails during the installfeatures phase.
  2. PowerShell Feature Activation: Attempted to run Enable-SPFeature -Identity PremiumFarm -Force in the SharePoint Management Shell, but feature provisioning fails because the underlying SKU definition hasn't switched.
  3. Service Account Privilege Adjustments: Tried restarting the SharePoint Timer Service (SPTimerV4) and changing its logon account to Local System / Local Admin to rule out file permission issues on the 16-Hive directory, but hit SQL permission/authentication blocks.
  4. Clearing Timer Jobs and Restarts: Cleared stuck or failed SkuUpgradeJob instances under Timer Job Status, restarted the SharePoint Administration Service and Timer Service across all servers, and performed iisreset.

Since this is a completely fresh farm with no customization or data loss risk, what is the cleanest way to force the farm to accept the Enterprise product key without having to completely unjoin and rebuild the 6 servers?

Any suggestions or workarounds would be greatly appreciated!

sharepoint server

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 22, 2026

    The installfeatures failure means the Standard-to-Enterprise conversion cannot complete configuration; it is not a key-entry problem. There is no supported switch that safely bypasses that stage. First, return the SharePoint Timer service to the farm service account rather than Local System. Verify all six servers have the same SharePoint products and patch level, with no pending restart. Then check Central Administration’s Upgrade Status and the PSConfig and ULS logs for the first SkuUpgradeJob or feature-installation error and correlation ID. Retry only with the designated farm administrator, which must be a local administrator on every SharePoint server and hold the necessary SharePoint and SQL permissions. If installation still fails after the farm is consistent, open a Microsoft support case and provide those logs. Because this farm has no production content or customizations, rebuilding it with the Enterprise key is the cleanest supported fallback; forcing PremiumFarm or manually clearing jobs is not.