ContributionsMost RecentMost LikesSolutionsRe: Logged In User integration into LogMeIn Client and Central Yeah it was the current local user's name I would like to see as an optional field in the views for central and the logmein client app. Though being able to use the search on the site and the app for a username and see the list of computers they are signed into would be nice. I think it would be great. Being able to see all the users logged on a TS server as well would be nice too. I'm guessing it would be tough to make it look nice in a table format or in the app if it's more than a few users though. Logged In User integration into LogMeIn Client and Central While we do have some computers that only is used by one user, alot of our computers are used by multiple users. Instead of naming each computer in our computer list with the name of user + hostname. It would be great If one of the fields in the list of computers in Central and the LogMeIn client was Current Logged In User. Than we can have it searchable in the search bar in central and the logmein client app. This way we can remote into computers without asking more questions to the users or getting them to follow instructions. It's not something super important but it would be a nice to have. Feature Request: TLS 1.2 Just wondering if it’s planned to move all the functionality of LogMeIn Central to function on TLS 1.2. As of now TLS 1.1 is needed for One2Many & Remote Execution to function at the moment. While using the LogMeIn Client, if you use the “Open the command prompt / powershell” button. It uses TLS 1.0 for the user sending the command, while the receiving end get’s it in TLS 1.1. Now I don't know if other features of LogMeIn Central uses anything older than TLS 1.2. Though if it does we would like to see them moved to TLS 1.2 (or at least functionable in TLS 1.2). We would like to see these moved to TLS 1.2 for security purposes if possible. Cheers, Brandon