![]() ![]() I assume that the IdleTime is being reported in minutes, since my initial tests only display single integers. Though it might be nice to pay them a phone call first :PĮdit: Well that's a good answer for versions of Server prior to 2012 :( But since they eliminated Terminal Services Manager from newer versions of Server, it seems like this powershell script might be the best option: It's also worth noting that you can log these sessions off by right clicking and disconnecting them. It can also be configured by using Group Policy or Windows Management Instrumentation. It can be used to configure the sign in requirements, as well as to enforce a single instance of remote session. So for example, if the output is "4+11:23" the user has been idle for 4 days, 11 hours, and 23 minutes. Terminal Server is managed by the Terminal Server Manager Microsoft Management Console snap-in. The output is intererpeted as "Days+Hours:minutes". There will be a listing of all active sessions and there is an "IdleTime" column. Then select the host in the left pane and in the middle pane select the "Sessions" tab. Enter the computer names for each terminal server. Click on Object Types > select Computers > OK. ![]() Select Groups > double click on Session Directory Computers > Add. Under administrative tools -> Terminal Services -> Terminal Services Manager Add Terminal Servers to the Session Directory Computers Local Group on the TS Session Broker Server: Start > Server Manager > Configuration > Local Users and Groups. Terminal Services Manager can get you this information. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |