Like a lot of SMS administrators, I have hundreds of reports that I use to know the health or asset information of my SMS environment. One of the key elements in any of any report is User Name & PC Name. PC Name is good, but what is ES-01, ES-02 or ENHANSOF-08E7EC?
To carry on the blog from yesterday.
Consider this situation: the security officer of the Gartek domain noticed via a SMS web report that Ellen is logged on to a server that she shouldn’t have access to.
After talking to Ellen, we have decided to minimize the risks, reset her password and eliminate the possibility that her account was compromised.
Since my report is based on v_R_System.User_Name0 then I would not notice that Ellen is logged on to the ES-01 server locally and not using her domain account. How long would the security officer and I be looking in the wrong place? This would slow down the process of why she is logged on to servers until I finally looked and found out that she was logged on locally.
The point here is to show that if my report used v_GS_COMPUTER_SYSTEM.UserName0 instead of v_R_System.User_Name0 I would see immediately that Ellen is logged on locally to the server and not using her domain account. Thereby I would know to look at ES-01 instead of the Gartek domain.
The other interesting thing to note is Gartek\Ellen is logged on to a lot more servers than just ES-01 and Gartek-dc.