Jump to content

Authenticating Office 2024 LTSC Pro Plus - No KMS?

Miscbrah

By Miscbrah
in Office Software

 Share

Recommended Posts

Miscbrah

Miscbrah

Posted
  • Author
Posted

Thanks all - sorry didn't mention I do have a KMS server and AD, was looking to authenticate with KMS.

 

Microsoft told me categorically there is NO KMS option for this, so I'm just moving to standard 2024 which does seem to. Even though @BKGarry it does seem like somewhere out there (and from what I've been reading) there actually might be. Just not for me it looks like.

 

If all else fails will indeed put the MAK in the config xml and stop my faffing.

 

Thanks again everyone.

Miscbrah

Miscbrah

Posted
  • Author
Posted
1 hour ago, 3s-gtech said:

I have a KMS key for 2024 Pro Plus. MS lied to you (or more accurately, that representative had no idea). I've used my reseller to sort this stuff before now.

 

Haha yeah actually it's TWO of them who've fibbed now. I might go in for the hat-trick and try again tomorrow...

Lxshm

Lxshm

Posted
Posted
45 minutes ago, 3s-gtech said:

Check your setup XML and also your license activation. I've seen similar, and I had to push the KMS client key as part of the install.

thanks for a bit it shows LTSC edition but after awhile it switches to 365 and ask to sing in for some reason

Miscbrah

Miscbrah

Posted
  • Author
Posted

Ok so I ran the .exe for 2024 STANDARD on the KMS server in preparation for the AD-based auth for 2024 STANDARD and went back to check the test 2024 PRO PLUS machine and it's just fine now. Product activated.

 

I'll give it a week to make sure it's "safe" to roll out and it stays authenticated and then I'll just say it's fine.

 

I don't know quite why this is working now.

 

Nobody from Microsoft I talk to knows why/why not or what I can/can't authenticate or which way I can/can't so at least I'm ending this crap-shoot with a licensed install. Hopefully...

 

Thanks everyone you were all more help than the people who actually make and sell this stuff!

3s-gtech

3s-gtech

Posted
Posted
36 minutes ago, Lxshm said:

thanks for a bit it shows LTSC edition but after awhile it switches to 365 and ask to sing in for some reason

That will happen if it doesn't check-in with KMS.

  • Like 1
Miscbrah

Miscbrah

Posted
  • Author
Posted
On 27/11/2025 at 10:22, Miscbrah said:

Ok so I ran the .exe for 2024 STANDARD on the KMS server in preparation for the AD-based auth for 2024 STANDARD and went back to check the test 2024 PRO PLUS machine and it's just fine now. Product activated.

 

I'll give it a week to make sure it's "safe" to roll out and it stays authenticated and then I'll just say it's fine.

 

I don't know quite why this is working now.

 

Nobody from Microsoft I talk to knows why/why not or what I can/can't authenticate or which way I can/can't so at least I'm ending this crap-shoot with a licensed install. Hopefully...

 

Thanks everyone you were all more help than the people who actually make and sell this stuff!

 

Felt optimistic so I got back in touch with Microsoft and explained the above. They said that actually does work, as if all along they hadn't been telling me it's literally impossible.

 

I'm baffled but my Office is all working so go me I guess!

 

Thanks again everybody for the help/sanity with that one.

JazzFlute

JazzFlute

Posted
Posted

My Working Office Professional Plus 2024 xml for reference rolled out using the Office Deployment tool with commands of.  

 

•    setup /download configuration.xml
•    setup /configure configuration.xml

 

 

<Configuration>
  <Info Description="Office Professional Plus 2024 (64-bit)" />
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024" SourcePath="C:\OfficeSetup">
    <Product ID="ProPlus2024Volume" PIDKEY="YOUR MAK KAY">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

 

 

  • Like 1
Lxshm

Lxshm

Posted
Posted (edited)
23 hours ago, JazzFlute said:

My Working Office Professional Plus 2024 xml for reference rolled out using the Office Deployment tool with commands of.  

 

•    setup /download configuration.xml
•    setup /configure configuration.xml

 

 

<Configuration>
  <Info Description="Office Professional Plus 2024 (64-bit)" />
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024" SourcePath="C:\OfficeSetup">
    <Product ID="ProPlus2024Volume" PIDKEY="YOUR MAK KAY">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

 

 

 

why not use "en-GB" ?

 

 

\\*\setup.exe /configure \\*\config.xml


  <Info Description="office 2024" />
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024" OfficeMgmtCOM="TRUE">
    <Product ID="ProPlus2024Volume" PIDKEY="*">
      <Language ID="en-gb" />
      <ExcludeApp ID="Lync" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

 

Edited by Lxshm
JazzFlute

JazzFlute

Posted
Posted
3 minutes ago, Lxshm said:

 

why not use "en-GB" ?

 

 

\\*\setup.exe /configure \\*\config.xml


  <Info Description="office 2024" />
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024" OfficeMgmtCOM="TRUE">
    <Product ID="ProPlus2024Volume" PIDKEY="*">
      <Language ID="en-gb" />
      <ExcludeApp ID="Lync" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

 

 

I've only just noticed that 😂I remember I always check after an office install that the @ key is where its supposed to be and then I know its UK so never changed the XML being as I didn't notice anyway.  Just checked a recent install and everything is set to UK in windows settings and in office languages, I wonder as in highlighted in yellow office takes it language settings from your office profile so doesn't matter what set up language is used?  Never had an issue in 2 years using the same setup.

Screenshot 2025-12-02 093918.jpg

Olliedawg

Olliedawg

Posted
Posted

Super similar to what we use, works well

  

<Configuration ID="XXXXX-XXXXX-XXXXX">
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume" PIDKEY="XXXXX-XXXXX-XXXXX">
      <Language ID="en-gb" />
      <ExcludeApp ID="Lync" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Updates Enabled="TRUE" />
  <RemoveMSI />
  <Display Level="Full" AcceptEULA="TRUE" />
  <AppSettings>
    <Setup Name="Company" Value="XXXXX-XXXXX-XXXXX" />
  </AppSettings>
</Configuration>

 

Koldov

Koldov

Posted
Posted (edited)
5 hours ago, Lxshm said:

 

why not use "en-GB" ?

 

 

Or even...

 

<Language ID="MatchOS" />

 

I presume you are using the English 'International' Windows ISO, aren't you...?

Edited by Koldov
  • Haha 1
  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...