Microsoft Intune or Endpoint Manager is awesome but also a pain if something does not work as expected. For example, if you create a package that simply imports a reg file, it will import the keys under SOFTWARE\WOW6432Node (WOW or SysWoW means Windows32OnWindows64). This is normal behaviour because Microsoft Intune Extension runs as a 32 Bit process on Windows. Therefore it does not know about the 64 Bit architecture.

So the solution is to run the reg command with this option. This will import the keys directly under SOFTWARE\…

reg import file.reg /reg:64

There are other approaches to this but my solution works and is the fastest in my opinion.

If you are having issues with Microsoft Teams Meeting Addin missing in Outlook, here are a few tips:

1. Make sure Microsoft Teams Meeting Addin is installed and present in the Control Panel
2. Navigate as admin to C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe (Version number might have changed)
3. Copy MicrosoftTeamsMeetingAddinInstaller.msi
4. Run the following command:
   • msiexec.exe /i “MicrosoftTeamsMeetingAddinInstaller.msi” ALLUSERS=1 /qn /norestart TARGETDIR=”C:\Program Files (x86)\Microsoft\TeamsMeetingAddin\1.23.33413\” (Version number might have changed)
5. Also, make sure this key is set on the user side. You could make a GPO or Intune script for that
   • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect
   • “Description”=”Microsoft Teams Meeting Add-in for Microsoft Office”
   • “FriendlyName”=”Microsoft Teams Meeting Add-in for Microsoft Office”
   • “LoadBehavior”=dword:00000003

Here is a tip if you are having issues with Microsoft 365 Apps when trying to login to activate Office (error 1200).

• Update to the latest Microsoft Apps version
• Delete content in these folders:
  • C:\Users\user\AppData\Local\Microsoft\IdentityCache
  • C:\Users\user\AppData\Local\Microsoft\OneAuth
  • C:\Users\user\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
• Run powershell as user (non admin)
  • Add-AppxPackage -Register “$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown
  • Add-AppxPackage -Register “$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown
• Delete Subkeys under
  • HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities
• Reboot and try logging in to Microsoft Apps

References:

https://www.borncity.com/blog/2023/10/30/office-365-neues-zum-anmeldefehler-1001-sign-in-error-1001-microsoft-verffentlicht-workaround/

By default, if you send a mail on behalf of a Shared Mailbox, the sent item will be saved in the user’s primary mailbox and not the shared mailbox. If you want to change it to expected behaviour, i.e. save the items in the Shared Mailbox, execute following command. This works in Exchange Online and Exchange OnPrem.

set-mailbox -MessageCopyForSentAsEnabled $True

set-mailbox -MessageCopyForSendOnBehalfEnabled $True

References:

https://learn.microsoft.com/en-us/exchange/troubleshoot/user-and-shared-mailboxes/sent-mail-is-not-saved

When an Exchange Online user has access to a shared mailbox through full access permissions, he can reply on behalf of that address. The problem is that, by default, emails sent as the shared mailbox are saved in the user’s main mailbox instead of the delegated mailbox. To fix that you have 2 options:

Option 1: Use Exchange Online Powershell

For emails sent as the shared mailbox (Full Access)

Set-Mailbox <shared mailbox> -MessageCopyForSentAsEnabled $true

For emails sent on behalf of the mailbox (Send On Behalf)

Set-Mailbox <shared mailbox> -MessageCopyForSendOnBehalfEnabled $true

Option 2: Registry

HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\Preferences

DWORD DelegateSentItemsStyle 1

Note! Outlook must be configured to run in cached mode, otherwise mails will get stuck in the Outbox.

References:

https://learn.microsoft.com/en-us/exchange/troubleshoot/user-and-shared-mailboxes/sent-mail-is-not-saved