logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Offline drdread  
#1 Posted : 21 September 2020 14:06:29(UTC)
drdread

Rank: Advanced Member

Groups: Registered
Joined: 26/08/2020(UTC)
Posts: 55
Australia

Thanks: 9 times
Was thanked: 2 time(s) in 2 post(s)
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>
Sponsor

If you ever wanted to thank us, you can send us Bitcoins using:

12G4A52Znm5s35buKDEmKU2p2vQY69Nsyo

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.

Offline Lemonde  
#2 Posted : 12 January 2021 11:02:49(UTC)
Lemonde

Rank: Advanced Member

Groups: Registered
Joined: 08/01/2017(UTC)
Posts: 672
United Kingdom
Location: London

Thanks: 17 times
Was thanked: 6 time(s) in 6 post(s)
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 you users need to return top complex work repeatedly, then you have to endure this error and programme in retstarts 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...
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.