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
Keywords:
User: SYSTEM
Computer: termserv.domain.local
Description:
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">
<System>
<Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
<EventID>10010</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-09-19T09:57:50.366901800Z" />
<EventRecordID>2289683</EventRecordID>
<Correlation />
<Execution ProcessID="174544" ThreadID="37164" />
<Channel>Application</Channel>
<Computer>termserv.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<RmUnsupportedRestartEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
<RmSessionId>0</RmSessionId>
<Pid>71184</Pid>
<FullPath>C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE</FullPath>
<DisplayName>Microsoft Outlook</DisplayName>
<AppVersion>0</AppVersion>
<AppType>0</AppType>
<TSSessionId>72</TSSessionId>
<Status>67108865</Status>
<Reason>1</Reason>
</RmUnsupportedRestartEvent>
</UserData>
</Event>