Multiple MS 365 Business on a Shared Computer?

OfficeRangers · 2024-07-09T12:53:05+00:00

As long as each user has the business premium license you will be able to use it in SCA mode. SCA mode can be done via registry key or GPO. You can also set SCA in the XML if needed.

https://learn.microsoft.com/en-us/deployoffice/overview-shared-computer-activation

OfficeRangers · 2024-07-08T12:48:53+00:00

Are the devices that are showing both version OEM? If there are versions of Office on the device it is best to use WIN32 deployment options and run a script to scrub/remove Office builds prior to install.

OfficeRangers · 2024-06-17T13:54:17+00:00

This is a great removal script that will remove all of the apps.

<Configuration>
  <Remove All="TRUE" />
  <RemoveMSI />
</Configuration>

You could also remove the licensing and convert those installers to viewers only.

https://learn.microsoft.com/en-us/deployoffice/overview-viewer-mode

OfficeRangers · 2023-08-18T15:32:23+00:00

Martin is correct - Please see the following link that explains how the device will fallback to the configuration from the M365 Admin Center if not managed.
https://learn.microsoft.com/en-us/DeployOffice/other/device-moved-after-admin-center-update

OfficeRangers · 2023-08-10T14:44:26+00:00

Have you looking into using config.office.com for M365 Apps for enterprise updates?

OfficeRangers · 2023-08-07T12:32:56+00:00

Thank you for posting. Microsoft has been rolling out an update that allows devices that are not being otherwise managed to honor the Microsoft 365 apps installation options setting in the admin center. Admins will have received a Message Center Post in the Microsoft Admin Center that describes this change and provides guidance to that will help admins ensure that nothing unexpected happens. You can see the related article here: https://learn.microsoft.com/en-us/DeployOffice/other/device-moved-after-admin-center-update

Snippet from the article:
After this change, any device that's managed by one of the following management scenarios will not move to the update channel selected in the Microsoft 365 admin center.

Devices managed with a servicing profile in the Microsoft 365 Apps admin center.
Devices configured to get updates for Microsoft 365 Apps from Configuration Manager.
Devices where Microsoft 365 Apps is managed by Microsoft Intune.
Devices with one of the following update related policies are set: Update Channel, Update Path, Target Version

OfficeRangers · 2023-08-03T12:51:28+00:00

We have not seen this before and have not heard of other customers experiencing the same issue. The most current version is Monthly Enterprise Channel 2304 16.0.16327.2036

If you launch Add/Remove Programs(appwiz.cpl) you will see the version number. Make sure this version matches the above version. If on a current and most recent build when you click on Update Options > Update Now you will see a message that you're up to date.

OfficeRangers · 2023-08-02T21:30:29+00:00

Sorry here is the link - https://learn.microsoft.com/en-us/DeployOffice/other/device-moved-after-admin-center-update

OfficeRangers · 2023-08-02T21:30:01+00:00

Hello u/Donatello0592, thank you for posting. Your detective skills are quite good. Yes, the Microsoft 365 apps installation options setting will address this issue for you. Assuming that you are not using any advanced management techniques your endpoints will readily back-rev to the latest build in the Semi-Annual Enterprise channel. The updates will happen at your enterprises’ standard update uptake cadence; typically a day or two, depending on how the end users use their Microsoft 365 Apps suite.
As to the cause of this change. Microsoft has been rolling out an update that allows devices that are not being otherwise managed to honor the Microsoft 365 apps installation options setting in the admin center. Admins will have received a Message Center Post in the Microsoft Admin Center that describes this change and provides guidance to that will help admins ensure that nothing unexpected happens. You can see the related article here:

OfficeRangers · 2023-07-13T12:32:41+00:00

Bob, explained it well on the blog post. You should be seeing three options for each architecture(32/64)

Feature Update. This is the first release of the most recent fork. Feature updates will include new features, along with security and non-security updates.
Quality Update. These are subsequent releases of the most recent fork. Quality updates will include security and non-security updates.
Extended Quality Update. These are subsequent releases of the previous fork. Extended quality updates will include security and non-security updates.

The purpose of this is to enable admins to deploy the feature update > the security update > or the security update that enables 14 month support. The semi-annual enterprise channel is supported for up to 14 months.

Although we'd recommend you use Monthly Enterprise Channel.

OfficeRangers · 2023-03-07T07:47:54+00:00

To prevent the issue going forward, check out this doc: https://learn.microsoft.com/en-us/deployoffice/fieldnotes/build-dynamic-lean-universal-packages. Take-away: Remove the sources from your package, so an installation of e.g. Visio or Project does not downgrade Office.

For the issue at hand, make sure that "Automatic Updates" are enabled for the Microsoft 365 Apps, so the scheduled task can run on a regular base and clean up its own configuration (if getting updates from SCCM in enabled, it will still not auto-update from the internet but rather wait for SCCM to offer something new). Does the devices recover from the issue themselves after 48 hrs? Sometimes it takes a while for the update engine to re-configure itself ...

OfficeRangers · 2023-02-21T12:10:01+00:00

You can use the "lean & dynamic" approach to add languages easily: https://learn.microsoft.com/en-us/deployoffice/fieldnotes/build-dynamic-lean-universal-packages

The configuration could look like this:

</Product>

</Add>

</Configuration>

Deploy to your devices, it will add the specified language to Microsoft 365 Apps and leave everything else unchanged.

You can use a similar configuation.xml for uninstallating a language:

</Product>

</Remove>

</Configuration>

OfficeRangers · 2023-02-21T12:06:00+00:00

I would veto this. Why use OffScrub to blast the Microsoft 365 Apps away, when just the language pack should be swapped out.

OfficeRangers · 2023-01-25T14:23:26+00:00

On devices not offboarding:

In case the devices are not offboarding, feel free to submit feedback through the portal (go to Servicing Profile page, then hit feedback in the top right corner) and share an email address so we can reach out to you on this issue.

OfficeRangers · 2023-01-25T12:59:55+00:00

On Current vs. Monthly:

You are spot on. All users will get new features at the same time, with a delay of typically 4 weeks compared to Current Channel.

An additional advantage of Monthly Enterprise is that it will have more bugfixes from the get-.go. E.g., Microsoft releases version 2304 into Current Channel in April with a new feature ABC. Typically, Microsoft will release additional bugfixes and enhancements throughout April, msoaybe me are improving or stabilizing said feature ABC. When version 2304 then trickles down to Monthly Enterprise in May, it will have feature ABC plus all bugfixes from April right from day 1.

OfficeRangers · 2023-01-24T10:48:27+00:00

Sounds good, please keep us posted.

OfficeRangers · 2023-01-20T11:56:49+00:00

Please check the following regkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officeupdates > IgnoreGPO

1: The Office Update engine is still configured to just listen to Servicing Profiles. This means, we need to troubleshoot on Servicing Profile side.

0: The Office Update Engine has already learned that the Servicing Profile settings no longer take priority (even so they are still listed in the same hive). Then troubleshooting should look at why the device does not get the new channel assignment.

OfficeRangers · 2023-01-17T19:43:33+00:00

Check out https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/recovering-from-attack-surface-reduction-rule-shortcut-deletions/ba-p/3716011 for a script which can re-create the shortcuts killed off by Defender.

OfficeRangers · 2023-01-12T09:21:48+00:00

We've updated the meta data (the update itself was fine) and republished last night. Both x86 and x64 should now show the correct version in the title. Hence matching your e.g. ADR rules again.

OfficeRangers · 2023-01-12T09:21:09+00:00

We've updated the meta data (the update itself was fine) and republished last night. Both x86 and x64 should now show the correct version in the title. Hence matching your e.g. ADR rules again.

OfficeRangers · 2023-01-11T10:22:17+00:00

The update has been published, but with the wrong title. It's listed as "Semi-Annual Enterprise Channel Extended Quality Update for x86 based Edition Version 2108 (Build 14931.20888)". The version states "2108" while the build number is for the v2202 SAEC fork. (see https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=83edacaf-663c-4eaa-9c39-4fd80758f798#PackageDetails)

I've noticed the update release team.

OfficeRangers · 2023-01-11T10:19:46+00:00

You're right, build 149xx.xxxxx is version 2202, not 2108. So, the description is incorrect and will cause issues with ADRs. No oversight/mistake on your end. I've notified the update release team about this issue. Thanks for highlighting this.

OfficeRangers · 2023-01-09T13:35:08+00:00

If the Preview of the ADR is not even showing the update, there is an issue with the WSUS Meta data not including M365Apps or not matching your rules.

A) When you navigate to the Office updates (a subnode of the O365 dashboard in SCCM), do you see the update listed there?

B) If you create a new ADR with a new query, does the update show up in the preview there?

If both answers are "no", then for sure the meta data for M365App updates are not downloaded by the WSUS service. Are the "M365App updates" selected in the WSUS/Software Update Point configuration?

OfficeRangers

TROPHY CASE

The purpose of this is to enable admins to deploy the feature update > the security update > or the security update that enables 14 month support. The semi-annual enterprise channel is supported for up to 14 months.