Hi All,

Am using this below code snippet to get current logged in user, it works fine over here...

I tested in another system having 3 users , but its not fetching the username...its returning NULL value.

What would be the problem...?

Thanks

Divakar

If the script is running on the computer, WMI will be much slower than using the wshNetwork object. For example:

Set objNetwork = CreateObject("Wscript.Network")
Wscript.Echo "The current user is " & objNetwork.UserName

-----

In a similar manner, you can retrieve the name of the local computer, from objNetwork.ComputerName. And, if you want the distinguished name of the current user (so you can query AD for other information), you can use the ADSystemInfo object. For example:

Set objSysInfo = Createobject("ADSystemInfo")
Wscript.Echo "DN of current user: " & objSysInfo.UserName

-----

Is it possible the other system was a 64-bit machine? I think your original method is only good for 32-bit machines (this function stopped working for me when I migrated to a 64-bit machine). Richard's solution is probably a better method for running on local machines anyway.

No one answered the question as asked.  The code works exactly the same on any machine.  Read the whole question very carefully.

The OPs question:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I tested in another system having 3 users , but its not fetching the username...its returning NULL value.

What would be the problem...?

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This statement/question makes the cause extremely obvious.  Only a real Windows geek would get this.  Are you a geek or a gawker?

Look very closely.  The answer is in the question.

Note that this is a question on an Admin WMI test that is given to applicants for Admin jobs. It is usually given as an open book question so feel free to look up the answer.

Note that this is a question on an Admin WMI test that is given to applicants for Admin jobs. It is usually given as an open book question so feel free to look up the a

Note that this is a question on an Admin WMI test that is given to applicants for Admin jobs. It is usually given as an open book question so feel free to look up the a

I've never seen a difference in performance between the wshShell and wshNetwork objects. Both will be faster and more reliable than WMI. I like the ADSystemInfo object because it is fast. In particular, if you are not sure the user will be authenticated to a domain, you can use error trapping and the UserName property will raise an error immediately (if the user is authenticated locally). Other methods result in a long timeout.

Good advice Richard.

In general it is a good idea to avoid WMI in logon scripts.

I understand that this is an old topic, but:

there IS a difference between wshShell and wshNetwork, not in performance, but in operation.

If you use wshNetwork to get username, and the script is invoked by system, the user name would be "system" (or localized string for "system").

If wshShell is used, then its ExpandEnvironmentStrings( "%USERNAME%" ) in this scenario will give "COMPUTERNAME$".