[v5.0] Logged in User - External Tool Variable


http://www.s-code.com/forum/Topic2453.aspx
Print Topic | Close Window

By jpickerell - Thursday, April 02, 2009
I would like to be able to open up the desktop folder of the currently logged in user. (without using the VNC file transfer dialog, as this isn't always available) I've tried creating my own "External Tool" that opens explorer.exe with " \\($SERVER_IP)\c$\documents and settings\($WINDOWS_USER)\Desktop" as an argument. A couple of problems with that. First, it uses my locally logged on username. Second, it is in domain\SAMAccount format. Is it possible to get a variable that pulls the username (without domain) that is currenly logged on to a machine? That would be so useful to me.

Thanks
Jared
By Yury Averkiev (s-code) - Thursday, April 02, 2009
Your wish has been granted Smile Look for the ($WINDOWS_USERNAME) variable (Windows User Name (Username) menu item) in the v5.0.1 Beta build, which is expected to be released in a few days.
By jpickerell - Friday, April 03, 2009
Fantastic! Can't wait to test it out!

-Jared
By jpickerell - Monday, April 06, 2009
Just tested out the 5.0.1.0 beta and the new ($WINDOWS_USERNAME). The problem is this still gives the username of the remote credentials, not the username of the locally logged in user. Any chance of getting that functionality?

Thanks
Jared
By Yury Averkiev (s-code) - Monday, April 06, 2009
Hi Jared,
I missed the part about the remote/local user name in your first post. I'm not sure whether or not such feature should be implemented. The immediate problem I can think of is that there are could be more than one user logged into a computer and there is no way for the VM to know which name it should return.

I'll add this feature to the features requests list and we will see what we can do about it.

By jpickerell - Friday, May 01, 2009
I've been thinking about this. As more than one user can be logged in how about adding a context menu that shows all currently logged in users that then has submenues under each user to do user specific (that specific logged on user) tasks? Then possibly under that it could have access to the user's desktop, my documents, etc or other scripts could be ran against that specific account?

I personally see value in that. What do you think?

-Jared