Skip to main content
Solved

2024 Microsoft Office LTSC - Signin Popup

Forum|alt.badge.img+4

In Jamf Pro, We have policies to install the 2024 Microsoft Office suite LTSC during our Provision policy which is a script that calls each policy to install individual pieces of software we want to install on a Mac.

Here is the order for the Microsoft install we have 2 policies:

1. Install 2024 Microsoft Office 16.106.26020821.pkg

(This is the older version from February. Testing. I tried the lastest version too)

2. Install Microsoft_Office_LTSC_2024_VL_Serializer.pkg

(I have also tried swapping the order)

Ever since I can remember this has worked exactly as intended. The Office suite is installed then the volume serializer is installed to activate the license. At first launch it opens to the templates/recent documents page.

However, over the last couple weeks of testing, the activation is no longer applying. I’ve tried everything I can to try and deactivate the license/reactivate it, but the only fix appears to be completely removing all office components, and reinstalling them - only then does the volume serializer work. 

I thought this might be as a result of the latest Office apps, so I reverted to using older versions of the pkg files but the problem remains.

Has anyone found a fix for this? 

Best answer by ubcoit

Yes, we started seeing this on June 3. Lots of testing of versions etc.  I discovered that it began March 17 with version 16.107.1 in my testing but others seem to have reported it sooner.  Anyways, browsing the Macadmins slack channel I found a solution.  You can either do local plist files for the system, per user or config profile(s). I just went with system wide plist files on fresh machines. If any need the fix I’ll handle that with a separate Jamf policy.

Macadmins on slack

 

#!/bin/zsh

# Word
sudo defaults write /Library/Preferences/com.microsoft.Word kSubUIAppCompletedFirstRunSetup1507 -bool true
# Excel
sudo defaults write /Library/Preferences/com.microsoft.Excel kSubUIAppCompletedFirstRunSetup1507 -bool true
# PowerPoint
sudo defaults write /Library/Preferences/com.microsoft.Powerpoint kSubUIAppCompletedFirstRunSetup1507 -bool true
# Outlook
sudo defaults write /Library/Preferences/com.microsoft.Outlook kSubUIAppCompletedFirstRunSetup1507 -bool true
sudo defaults write /Library/Preferences/com.microsoft.Outlook FirstRunExperienceCompletedO15 -bool true
# OneNote
sudo defaults write /Library/Preferences/com.microsoft.onenote.mac kSubUIAppCompletedFirstRunSetup1507 -bool true

Good luck!

View original

    4 replies

    Forum|alt.badge.img+7
    • ubcoit
    • Contributor
    • Answer
    • June 9, 2026

    Yes, we started seeing this on June 3. Lots of testing of versions etc.  I discovered that it began March 17 with version 16.107.1 in my testing but others seem to have reported it sooner.  Anyways, browsing the Macadmins slack channel I found a solution.  You can either do local plist files for the system, per user or config profile(s). I just went with system wide plist files on fresh machines. If any need the fix I’ll handle that with a separate Jamf policy.

    Macadmins on slack

     

    #!/bin/zsh

    # Word
    sudo defaults write /Library/Preferences/com.microsoft.Word kSubUIAppCompletedFirstRunSetup1507 -bool true
    # Excel
    sudo defaults write /Library/Preferences/com.microsoft.Excel kSubUIAppCompletedFirstRunSetup1507 -bool true
    # PowerPoint
    sudo defaults write /Library/Preferences/com.microsoft.Powerpoint kSubUIAppCompletedFirstRunSetup1507 -bool true
    # Outlook
    sudo defaults write /Library/Preferences/com.microsoft.Outlook kSubUIAppCompletedFirstRunSetup1507 -bool true
    sudo defaults write /Library/Preferences/com.microsoft.Outlook FirstRunExperienceCompletedO15 -bool true
    # OneNote
    sudo defaults write /Library/Preferences/com.microsoft.onenote.mac kSubUIAppCompletedFirstRunSetup1507 -bool true

    Good luck!

      Forum|alt.badge.img+4
      • wdoty
      • Author
      • New Contributor
      • June 11, 2026

      Hi ubcoit,

      Thank you VERY MUCH for the suggestion!

      I created a configuration profile in Jamf Pro to enforce these plists.

      It seems to be working perfectly!

        • rstella
        • New Contributor
        • June 23, 2026

        Running into this too. But not sure what the process is. Tried running the bash script on a system that already has Office and serializer installed but still getting the login prompt.

        Not sure what I’m missing. TIA.

         

        Forum|alt.badge.img+4
        • wdoty
        • Author
        • New Contributor
        • June 29, 2026

        Running into this too. But not sure what the process is. Tried running the bash script on a system that already has Office and serializer installed but still getting the login prompt.

        Not sure what I’m missing. TIA.

         

        I’m not sure on the bash script way, but adding these to my existing MS Office configuration profile worked.

        Here are some screenshots:

         

          Terms & ConditionsAccessibility statement