
Quote: Originally Posted by
NCondulmari

Quote: Originally Posted by
NCondulmari
This tweak is very useful when you have working stations shared by different users. For example: salespersons who come to the office to post their work or check their mail. It happens even in this era of internet connectivity. The occasional user logs in to the workstation with username and password. The "username on computername" tweak allows to see if somebody is still logged in, or who logged in last.
You can rename or change the keys values if you have administrative priviledges and make yourself owner of the keys you want to modify. But the modifications have no effect in windows 7. The name of the desktop icon remains "Computer". Very frustrating
This is the reason why I'm trying to import the tweak in Windows 7. I'm a consultant to a financial services Company (who represents various Leasing Companies) for whom I developed various applications (mostly in Microsoft Access VBA and VB .NET). We have agents who perform as the salespersons in my quote.
If I understand correctly, you're talking about a scenario where a domain-joined workstation has been abandoned in a logged-on state, and you're got IT/support staff periodically roaming the "hot desking" area to try to deal with the situation?
If I haven't misunderstood, then IMHO the organisation has a fairly severe disciplinary problem on its hands, followed by a somewhat less severe but still substantial domain policy configuration issue, and finally a bit of a skills shortage in the roaming IT staff who inspect these machines. Without wishing to sound flippant in the least, the very last thing I'd worry about under those circumstances is haxx0ring the name of the computer icon on the desktop.
Disciplinary: Any user who walks away from a workstation without locking the thing is in breach of security best practices. It's bad enough when it's done for a two-minute loo break, but it's downright dangerous when they walk away for good and leave the computer logged on,
especially given it's a financial services organisation. Remind me not to trust them with my money.
Configuration: Domain policy ought to be enforcing locking screen savers, and hence precluding the possibility of a machine being left unattended and logged on for longer periods of time. It may be different in an educational institution, but in a corporate environment there is really no excuse for this oversight.
Skills: Should one of the roving IT/support staff find a logged on machine, they can tell who's logged on in myriad ways. The WHOAMI command springs to mind. HOSTNAME would show them the computer name.
It's not my intention to be confrontational, but to help. With respect, in many financial orgs somebody (in IT) would get kicked down the stairs for merely allowing this situation to develop. It's better to fix it properly by educating users and the IT staff, than to seek workarounds for lax security practices.