OMS Cloud uses a timeout feature for your security and to protect your company's data. This helps prevent unauthorized users and people from accessing your data when you're away from your computer.
If you're working in OMS Cloud and are inactive for 120 minutes (2 hours), you will receive a "time-out" security message and will need to reconnect to OMS Cloud.
The timeout duration cannot be changed and is applicable for all users on OMS Cloud.
OMS Cloud measures inactivity as no input to the OMS system, such as mouse movements, keyboard input, or button clicks. If you are timed out and log back in within 15 minutes, you can continue where you left off. After 15 minutes of logging off, OMS will close all windows open at the time of the disconnect.
If you're still receiving a timeout notification before the 2 hour limit
There are a number of reasons why you may still be receiving a timeout notification even sooner than two hours.
Another user has logged into your account
Another user may have logged into your account. Only one cloud connection user can be logged into OMS Cloud at a time.
Your computer experienced a network configuration change
If you actively move between networks, such as cellular to Wi-Fi or a VPN, your IP address may have changed when connecting to OMS Cloud and with an unapproved IP address. OMS Cloud requires your company to provide a list of IP addresses that is approved to access your OMS Cloud system.
Please contact us if you need to update your list of approved IP addresses.
Your computer's time limit is set sooner than 2 hours
Your computer or internal network's group policy may be setting session time limits sooner than 2 hours. To check if this is the case:
- Launch the Local Group Policy Editor in Windows. You can view it in Control Panel or by typing "gsedit.exe" in the Windows search bar.
- Click to expand User Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits (see screenshot below).
- View "Set time limit for active but idle Remote Desktop Services sessions" and click on "Edit".
- Check if the time limit is set to Not Configured, Disabled, or Enabled.
- If enabled, you'll need to modify the idle session limit to be greater than or equal to 2 hours. If you set it greater than 2 hours, OMS Cloud will still disconnect after 2 hours.
- Click on OK.
