Windows server who am i

No I'm not getting notifications of Windows expiry. I do not have a Homegroup. Was wondering why there would be events such as: Group Policy received notification CreateSession from Winlogon for session 1. Thanks I am not in front of this pc at the moment. Will post on Monday. What I'm trying to determine is what build of Windows was installed. It sounds to me like the tech might have installed a Volume License which would be illegal on your PC. This is not the name of my computer.

Thanks very much. I see nothing in the images you presented that would indicate your computer has any knowledge of a server. In reply to payges's post on June 17, You have Windows 10 Home which does not have the capability to join a domain. A question came up in class this week which is asked quite often when I am teaching an Active Directory class. Have the logged on user launch the command prompt on the target computer. Type Set Logonserver the name of the domain controller that authenticated the user will be returned.

See the figure below. The returned results will provide you the name of the domain controller that provided the logged on user with GPOs. This shows active environment variables. This reports most of the same information that everyone else is saying but you can also just type. From command line? The logged in user is stored in the environmental variable "username". The above are native to the OS and better answers, but in the spirit of completeness, there's literally a whoami. At 32 kb, it'd be easy to roll out through group policy, if you had your heart set on that command.

Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. What is the Windows equivalent of Unix "whoami" command? Ask Question.

Asked 12 years, 8 months ago. Active 1 year, 4 months ago. Wouldn't the user login details be located in the security logs of one of the DCs? Every DC would have to be queried to find that entry and it would take time and people would not like you for the overhead it would cause.

Logon details might be in the DC security logs, but the OP wants to know on which server s the user is currently logged in. Like as of now. Also, those events might not include all of the info he is looking for, like, for example, the computer he logged in at. I agree that the logon script approach might be useful.

But they might not want to implement that for a variety of reasons. Office Office Exchange Server.