If you look at the event viewer as the administrator there are server logs but not for login/logout as far as I know. Please check the Event Viewer tree on the left side under 'Applications and Services Logs -> Windows -> TerminalServices-*' where * is all of the logs there. I think you are most interested in the TerminalService-LocalSessionManager Operational log. Event ID 21 will provide the IP address of the incoming connection. There is also a 'RemoteDesktopServices-RemoteDesktopSessionManager' node in the event viewer tree on the left side under 'Applications and Services Logs -> Windows'. Only the Administrator role is allowed to view the file I believe.
Please confirm and let me know if this addresses your use case. Maybe try this for logging login/logout as well.
It will generate you all sort of reports from logs and will save you a bunch of time if you want to get all of the details about RDP connections and other stuff. Please note: I am affiliated with Acceleratio, the makers of the tool mentioned above, so I might be a little bit biased here.
I can't tell you how to check from your work machine when you established a VPN as presumably it isn't the VPN server (?). However, if you're using Remote Desktop Connection to control that work PC you may be able to pull the logon / logoff times from the Event Viewer. Look in the Security logs for those. RDP logons are an Event ID 4624 but just searching for 4624 won't work.
Rdp Access To Server
How To Enable Remote Desktop Windows 7
App-for-mac-calendar/css at master mariodev12/app-for-mac. Within the event you need the Logon Type value to be '10' and the SecurityID value to be yours. Not sure how to filter those.
The other day I set up a new workstation for an employee in a remote office. We are a small company so I usually have new computers shipped to me in our main office where I configure them before shipping them out. In a hurry to get the XP machine out the door I did everything else except enable remote desktop.
How To Enable And Send Rdp Logs
I've done this several times. Of course as soon as the computer arrived the remote user had an issue with something that needed to be tweaked. I think I had neglected to set up his profile in Outlook. He didn't want me to walk him through the steps on the phone so he went to lunch and left the machine on for me to work on remotely. That's when I discovered I couldn't get into it. We're on a Microsoft domain here. The computer had been joined to the domain before it left the building.
0 kommentar(er)
