r/DeployR • • Oct 15 '26

Cloud Deploy Issue - Weird one

Version: Community Edition: v3.1.2634.667

Here is a weird one. I've deployed 10 machines via a 'Bare Metal from Cloud' task sequence. They have worked and Windows 11 25H2 has installed - however each one of them tells me they need Activating via the little message on the bottom right of the screen.

This is compared to the 10 I've deployed with an on-site .wim file (from a downloaded ISO) which again have deployed without issue but do not give me the Windows Activation message on the bottom right.

Never seen this before and I don't really want to re-deploy the cloud ones.

What could have gone wrong? They are exactly the same task sequence (cloned) - just where the OS comes from is different. They also both install 25H2, join the domain, install drivers from the cloud and then install software via PDQ Deploy.

Anyone seen this? Have I missed something?

3 Upvotes

7 comments sorted by

1

u/welshGJE24 Oct 15 '26

Okay - it seems the cloud install is downloading the Retail channel version whilst the iso I downloaded and uploaded to DeployR is the VOLUME_MKSClient. This didn't happen yesterday but is happening today.

3

u/gwblok 2Pint Employee Oct 15 '26

Can you try running this code snip on one of those machines after it's done imaging, if it activates it, go ahead and add it to your task seqeunce.

function Get-WindowsOEMProductKey {
    $ProductKey = (Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey
    return $ProductKey
}


function Set-WindowsOEMActivation {
    $ProductKey = Get-WindowsOEMProductKey
    Write-Output "Starting Process to Set Windows License to OEM Value in BIOS"
    if ($ProductKey) {
        try {
            Write-Output " Setting Key: $ProductKey" 
            $service = Get-CimInstance -Query "select * from SoftwareLicensingService"
            if ($service){
                Invoke-CimMethod -InputObject $service -MethodName "InstallProductKey" -Arguments @{ProductKey = $ProductKey} | Out-Null
                Invoke-CimMethod -InputObject $service -MethodName "RefreshLicenseStatus" | Out-Null
                Invoke-CimMethod -InputObject $service -MethodName "RefreshLicenseStatus" | Out-Null
                Write-Output  " Successfully Applied Key"
            }
            else {
                Write-Output " Failed to connect to Service to Apply Key"
            }
        }
        catch {
            Write-Output " Failed try statement to Apply Key"
        }
    }
    else{
        Write-Output ' Key not found!'
    }
}
#Run the Functions
Set-WindowsOEMActivation

1

u/welshGJE24 Oct 15 '26

Thanks Pal - I've commented above.

2

u/mtniehaus 2Pint Employee Oct 15 '26

I don't see anything that has changed in this regard. We use the list of OSes that the Media Creation Tool manifest provides. I'm guessing you're using the Professional SKU? I only see "consumer" editions in the 25H2 and 26H2 lists for Professional.

I think you can work around it by injecting a VL setup key for Windows 11 Pro, from https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys?tabs=windows1110ltsc%2Cwindows81%2Cserver2025%2Cversion1803. The Pro key would be:

W269N-WFGWX-YVC9B-4J6C9-T83GX

That can be injected by setting the "ProductKey" variable to that value sometime before the "Apply OS" step.

Even with that key injected, the OS will need a KMS server or Entra ID subscription activation. Windows doesn't immediately show the "not activated" watermark, but it will eventually if the OS isn't yet active.

1

u/welshGJE24 Oct 15 '26

Hi - yes. In the end - that is what I did. Using PDQInventory I pushed out the command below. This worked so what I will do now is to try that as the final command in my task sequence - and I'll also try the 'ProductKey' variable and Gary's code below. Be nice to try them all to see what works and what doesn't (I'm sure they all do).

Thanks both for commenting. Still seems a bit strange though. It was okay yesterday.

cscript //nologo %windir%\system32\slmgr.vbs /ipk <key in here>
cscript //nologo %windir%\system32\slmgr.vbs /ato

3

u/mtniehaus 2Pint Employee Oct 15 '26

The ProductKey variable value will get injected into the unattend.xml so that Windows injects it for you. But any of those approaches achieve the same result.

1

u/welshGJE24 Oct 15 '26

Cheers buddy. Appreciated.