How are we deploying office 2024 LTSC ?

[chazzy2501]

Got the OVS licence, so like 2019 and 2021 I can only deploy the 2024 version of office... seems that the PC though will ignore what you deploy, the MAK you include with it and will capture your login details and BAM, you are using office 365!?

 

I had to sign out and jam it up three times with the MAK key to convince it to use office 2024... I think it maybe the office configurator and the per user licencing options.. (that are greyed out)

 

any help?

 

(I'll ask for a KMS key as well)

Edited December 11, 2024 by chazzy2501

[OLdMan99]

Us this to create your xml file

https://config.office.com/deploymentsettings

[chazzy2501]

Us this to create your xml file

https://config.office.com/deploymentsettings

 

Yes, I was using this but it only allows for per user licencing? is this correct? My old XML for 2019 and 2021 have no mention of licensing model. (other than MAK or KMS)

 

I think looking at the documentation that to use shared licensing is wrong and device licensing is only for M365 APPs that are connected to entra?....

 

So I'm stuck, on how to deploy, I tried a test deployment with a MAK key but in use it changed to M365 using my credentials NOT 2024LTSC that I deployed?!! (I'm guessing that office can just change itself now depending on license)

[michaeljbrewis97]

I started testing Office 2024 LTSC a few weeks ago and ran into this problem of it trying to get users to sign in to Office 365. Will try creating the configuration file from the link suggested and will do some tests to see if it now works.

 

But also getting the shared device option greyed out.

 

 

Yes, I was using this but it only allows for per user licencing? is this correct? My old XML for 2019 and 2021 have no mention of licensing model. (other than MAK or KMS)

 

I think looking at the documentation that to use shared licensing is wrong and device licensing is only for M365 APPs that are connected to entra?....

 

So I'm stuck, on how to deploy, I tried a test deployment with a MAK key but in use it changed to M365 using my credentials NOT 2024LTSC that I deployed?!! (I'm guessing that office can just change itself now depending on license)

[chazzy2501]

FFS Office updated over the weekend and is now unlicensed.... asking for my office login or product key...

 

I have a KMS now so will deploy using this method and see what new pain it brings.

[chazzy2501]

OMG, this is turning into a blog but Outlook stop getting emails, I had force quit the program and now when it loads it is 365 NOT 2024... FFS. I put the MAK key in YESTERDAY...

[supportman]

Here is our configuration.xml file if that helps? We had similar issues as on OVS you cant deploy 365 properly.

 

Edited December 17, 2024 by supportman