• drdread
  • 100% (Exalted)
  • Advanced Member Topic Starter
3 years ago
Presumably this is related to office 365 trying to update the app and failing as our remote desktop server is nearly always in use.

What is the best practice for keeping office 365 up-to-date on a remote desktop/terminal server?

Log Name: Application
Source: Microsoft-Windows-RestartManager
Date: 19/09/2020 10:57:50
Event ID: 10010
Task Category: None
Level: Warning
Computer: termserv.domain.local
Application 'C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE' (pid 71184) cannot be restarted - Application SID does not match Conductor SID..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
<TimeCreated SystemTime="2020-09-19T09:57:50.366901800Z" />
<Correlation />
<Execution ProcessID="174544" ThreadID="37164" />
<Security UserID="S-1-5-18" />
<RmUnsupportedRestartEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
<FullPath>C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE</FullPath>
<DisplayName>Microsoft Outlook</DisplayName>

Want to thank us? Use: Patreon or PayPal or Bitcoins: 3GJia7gLLY8V8eYBf5Q3RjCrNV8kZC3aNn

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.

  • Lemonde
  • 100% (Exalted)
  • Advanced Member
3 years ago
This is going to happen with many users logged in to O365 on a server trying to perform updates.

The issue is that Excel or Outlook or whatever is trying to update under an administrator privilege but is already running under user privilege which is not allowed.

The simple answer is that you have to either have an idle log-out policy in place, or if your users need to return to complex work repeatedly, then you have to endure this error and programme in restarts where they have to log out once a month or similar.

The other option is that you follow the preferred Microsoft model of Windows 10 VMs for each user which is actually easier than it sounds as you do not need Office 365 E4 and you can reboot people when and as you choose.

In these situations it is only a small fraction of users who need to come back to extremely complex work over and over (the old 80/20 rule where 20% of people cause 80% of the hassle) so you could always find a fit with the few users refusing reboots can have their own Microsoft Windows 10 VM and the rest on the RDS server can have an idle time logout of 1 hour.

Food for thought...