Changes can be made using the Set-OrganizationConfig cmdlet, for example to set the timeout interval to 15 mins we'd issue the following cmd: Note that this parameter has a range of 5 min - 8 hrs. The ActivityBasedAuthenticationTimeoutInterval parameter controls the actual timeout interval in hh: mm: ss format where hh = hours, mm = minutes and ss = seconds. ActivityBasedAuthenticationTimeoutIntervalĪctivityBasedAuthenticationTimeoutEnabled is pretty self-explanatory, you will want to keep it enabled if you intended to set the timeout interval.ActivityBasedAuthenticationTimeoutEnabled.There are two parameters in particular worth paying attention to:
Get - OrganizationConfig | FL ActivityBasedAuthenticationTimeout *
#Outlook for mac idle timeout Offline#
(3) It’s optional to check the option of Schedule an automatic send/receive every x minutes in the When Outlook is Offline section, and enter a send/receive interval time in the box. You can confirm this configuration via PowerShell using the Get-OrganizationConfig cmdlet: For example, if you need Microsoft Outlook scheduling automatic send/receive every hour, just enter 60 in the box. Given that email remains a vitally important business tool for many organizations, reducing the session timeout on Exchange Online (and Exchange 2016) is a fairly common request and it is really simple to do.īy default, session timeout is enabled for OWA (let’s just call it that, shall we?) and it set to 6 hours. This can be especially dangerous when these applications are accessed on shared terminals or public computers. The idea generally is that if a user is not actively using and application for 10 –15 mins, they have completed the task they were working on and have forgotten to logoff correctly. In today’s browser first, cloud first world, many organizations look at reducing risk by imposing strict session timeout settings on their productivity tools and applications.
0 kommentar(er)
