Windows 10: WIndows 10 going to sleep disconnects Outlook from local Exchange Does not do this with...

All my Windows 10 machines using Outlook 2016 or later are having this issue - when the computer goes to sleep, Outlook is offline and prompting for user credentials even with Outlook settings are not to ask when opening - and credentials are not populated in the prompt. The only way to fix issue is to close Outlook and reopen it.


I have disabled computer sleep in Power Settings and disabled power management on NIC card wired desktop, but Outlook still keeps disconnecting from local exchange server when computer is left idle for extended period over 2 hours of time.


From reading other community topics similar to this issue - this is not an Outlook or Exchange issue, but Windows 10 issue.


This is a persistent problem on multiple machines in my office.

:)

 

Outlook not connected in Microsoft Exchange Server

I am new to Exchange Server 2003 and I have a friend with a network server that I don't know how to re-establish a user to the network. I moved one of his non used computers to this station and now when I try to log in the user I get the error that the name can't be verified because Outlook is not connected or online. This computer used to be online with a different user. Can anyone tell me the steps to check this? Thanks.

 

Outlook 2016 not talking to Exchange 2010


Hi There,

I'm trying to configure Outlook 2016 on Windows 10, connected to a local network. However if I auto set up Outlook it doesn't go through and comes up with
''the Microsoft exchange information service in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service''.

I can ping the server and am getting information back but for some reason when in Outlook, even if I manually try and connect it just won't go through.

Any ideas, or any other forum posts with people having the same issue?

 

Windows 10 v1903 suspends Microsoft Outlook when Windows remote desktop user disconnects

It seems that Windows 10 Pro v1903 suspends Microsoft Outlook (365 or 2019 with latest office build v1908) when remote desktop user disconnects session (user closes session and does not log off).

In summary, we use remote desktop to connect to a clean install Windows 10 v1903 VM with Microsoft Outlook installed (365 or 2019 with latest build 1908). We set Outlook to Offline mode, queue 10 emails, turn Outlook back to online and quickly disconnect the session (not logging user out). I would expect that the emails should be sent. This however does not happen and is only sent when I log back into the remote session.

We can confirm that:

1. It is not a Windows 10 power and sleep setting, as all screen savers, sleep modes and such are disabled.
   
2. It is not a ‘System unattended sleep timeout’ as set out in this post. Bear in mind that the ‘suspension’ is immediate and does not take effect after 1 or 2 minutes.
   
3. It is not the NIC that is suspended, as we ran console ping tests while disconnected, which continued to poll.
   
4. But most importantly, an exact duplicate of the setup, using a Windows 10 Pro v1809 build, does not suspend Outlook build 1908, and the queued emails is successfully sent.
   
5. Updated. Changed group policy settings' Session Time Limits as suggested by harrymc, but it was unsuccessful.
   
6. Updated. The Terminal Server registry fix suggested here by harrymc , did not resolve the problem.
   
7. Workaround This disconnect shortcut proposed by harrymc DID WORK as interim workaround.
   

We are therefore convinced the problem is with a setting change on remote desktop users in Windows v1903. We have found that only Outlook is so far affected.

Any comment that might point us in the right direction to restore the functionality to Outlook whilst the remote session is disconnected, will be highly appreciated.