As an administrator many of us have had to deal with the dreaded session timeout at one point in time or another.  If you are an enterprise administrator you know that at any given time you could have more than 5 different applications or servers open and logged into.  No one hates sessions time-outs more than me, especially when you are super busy and up against a deadline.  If you are in a situation where there are a ton of security restrictions, such as working for a government agency or financial institution, you know how strict those timeout sessions can be.  When you have to log back in every 15 minutes or inactivity, or in some cases even less, it can be a real productivity killer.  In vRealize Operations Manager 6.2 (vROps) you can edit the session time-out threshold pretty easily.  The only issue is whether you are able to or not, in some instances your security restrictions may keep you from changing that setting.  Either way, I thought I would show you how to do it if you are in fact able to.


Changing the ‘Session Timeout’ Threshold

I’m going to make the assumption that you, at the very least, have vROps 6.2 installed and you know your way around fairly well.  Even if you don’t, I’ve provided pictures to help guide you along the way.  The first thing you need to do is log into your vROps instance by navigating to the URL for your vROps Manager UI.  Once logged in, follow the steps below to make the change.

Step 1

From the home page, click on the ‘Administration’ button, this will take you to your administration interface where you can make necessary changes to your vROps installation.





Step 2

Once you are in your administration view pane, on the left hand side of the screen almost at the very bottom of the list, you will see ‘Global Settings’, click on ‘Global Settings’ to launch a view of all the settings you can make changes to.





Step 3

After getting to the ‘Global Settings’ pane, you are presented with 14 different settings that you can edit to your liking.  The setting we are looking to edit is called ‘Session Timeout’.  From this current view we can’t make any changes, we first need to click on the pencil icon at the top of the ‘Global Settings’ view.  After clicking the pencil icon, edit mode is enabled, and the options we saw in the last pane now have boxes where we can change the default setting.




Step 4

Find the ‘Session Timeout’ setting (5th option down), and the edit box is at the far right of the window.  The default setting is 30 minutes, but you can set it anywhere between the minimum of 1 minute to 34560 minutes which equates to 24 hours.  Unfortunately there is no longer an option for ‘Never’ to set the timeout threshold, so you have to be content with 24 hours as your max.  Once you are done, click ‘OK’ at the bottom right of the window and you are done.  No need to log out/log back in, the change takes immediately.





Security, Security, Security…

In effect, you can now never have to worry about being logged out of vROps, at least consistently for 24 hours.  I have to put my security hat on for a second and preach to you about the necessity of the timeout threshold in some environments.  When there are few administrators, you want to ensure that you don’t have unlimited access to vROps, or any part of your domain.  Timeout thresholds are in place for a very good reason, we all forget to log out at times, or lock our screen, and the last thing we want is for ‘Joe User’ to walk by and see the unlocked screen and start clicking things inadvertently or maliciously.  I don’t think that happens everywhere, but it does happen from time to time.  Free yourself from the timeout if you need to, but make sure to lock your screen when you walk away, use common sense.  End of my PSA, thanks for listening.

Greg W Stuart
Greg is the owner and editor of He's been a VMware vExpert every year since 2011. Greg enjoys spending time with his wife and 3 kids. He works as a Sr. Consultant at VMware and resides in Northern Virginia, 15 minutes west of Washington DC.

Leave a Reply

Your email address will not be published. Required fields are marked *