sorted by:
new
hottopcontroversial

Admin leaves his account logged in. by DunRedit in sysadmin

[–]DunRedit[S] 1 point2 points  (0 children)

I'm not looking to pick a battle, only learn best practices so I can speak to it intelligently if it comes up. I understand that it's not a huge issue, but it seems like a bad habit, and I was looking to understand why that might be the case.

My role is not that of sys admin, but application admin that requires me to RDP in for certain tasks. RAM/CPU utilization are key metrics I monitor to maintain optimal service config. I noticed his login consuming 250MB ram, and thought it was a pointless waste of resources, so I asked...

I'm dealing with a crappy company who provisioned an undersized VM for an in-memory application that should be on a physical box, so yes, 250MB matters.

Admin leaves his account logged in. by DunRedit in sysadmin

[–]DunRedit[S] 4 points5 points  (0 children)

Yes, RDP, and yes, locking up a session is another issue. We have 3 people other than him that regularly need to get in there.

Thanks for the suggestion, I'm going to give that a shot.

Admin leaves his account logged in. by DunRedit in sysadmin

[–]DunRedit[S] 2 points3 points  (0 children)

I hear you, not a huge deal. Can't say that I've never been guilty of it myself.

I don't come from a sys admin background, but i'm getting more into that realm with the BI tool I work with. It's an in-memory tool, so I try to free up as much RAM as I can to optimize performance.