You are not authorized to post comments.

Windows Tip: Locking a desktop at logon

ITworld.com |  Operating Systems Add a new comment

Send your Windows question to Mitch today! | See other Windows tips




Digg!


Recently an ITworld reader contacted me with an interesting question: Can you configure Windows XP so that it logs on automatically but into a locked state? In other words, if the AutoAdminLogon registry value found at HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon has been set to 1 and the DefaultUserName and DefaultPassword values have been configured appropriately, is it possible to make Windows lock the desktop immediately after automatic logon occurs?


The XP machine under consideration runs a scheduled task at night that copies data collected on the machine to another machine on the network. Unfortunately, to perform its work properly the machine has to automatically log on using admin credentials, but during the day this is not a problem as the user can simply lock the workstation when he has to leave the machine. But at night what happens is that whenever new security updates become available on the Windows Update website, the machine automatically downloads and installs these updates and reboots. Then the machine starts up, automatically logs on using admin creds, and the desktop appears. Anyone with physical access to the machine now has admin privileges on it, which is not good. Configuring a password-protected screen saver will help, but it still leaves a window of opportunity since an unrealistically short screen saver setting of 1 minute makes it frustrating to work on the machine during the day.


Unfortunately you can't configure Windows autologon to log on into a locked state, but a short script may provide a workaround for this situation. Simply open Notepad and copy and paste the following lines into it:

Wscript.Sleep 30000
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "rundll32.exe user32.dll,LockWorkStation",1,false

Save the file as lock.vbs (not lock.vbs.txt) on your desktop and test it by double-clicking on this script. What should happen is that in about 30 seconds your machine should lock. If this works, copy lock.vbs into the Startup folder on your Start menu. Now reboot your machine and log on (or autologon) and about 30 seconds after logging on your machine should lock. This is totally independent of your screen saver timeout, and uses rundll32.exe to call out the LockWorkStation function from user32.dll.


The reason for using 30 seconds (30000 in the first line of the script) is to give the desktop time to settle before automatically locking the workstation. Once you can confirm that this works, you can then experiment by lowering this time value if you want to reduce the window for your desktop being exposed before automatically locking it. You may even be able to use a value of 0 to lock the desktop immediately after logon, but it's best to try changing the value gradually in stages and of course doing so on a test machine before you try it on a production one, just in case it causes problems of some sort.

 

ITworld LIVE

Operating SystemsWhite Papers & Webcasts

White Paper

A Comparison of PowerVM and VMware vSphere (4.1 & 5.0) Virtualization Performance

This technical white paper presents benchmark results showing greater VM consolidation ratios than demonstrated in previous benchmarks and demonstrating the extent of the performance lead that PowerVM virtualization technologies deliver over x86-based add-on virtualization products.

White Paper

Consolidating Lotus Domino x86 Workloads on IBM Power Systems

Read the white paper to learn how moving up to Lotus Domino 8.5 and consolidating with IBM Power Servers can help you boost performance results and ROI.

White Paper

Task, workflow & issue management for teams. Try free!

Need a flexible system for managing team tasks, issue tracking, and automating and managing workflow processes? Comindware® Tracker helps you do it all.

Webcast On Demand

Best Practices in Monitoring VMware

The benefits of virtualization are unassailable: increased agility, scale, and cost savings to name a few. However, so too are the monitoring challenges posed by these environments-including complexities, lack of visibility and control, and inefficiency.

Sponsor: Nimsoft

White Paper

How Nimsoft Service Desk Speeds Deployment and Time to Value

For years, many support teams have been hamstrung by their traditional service desk platforms, which require complex, time-consuming coding for virtually every aspect of customization. This complexity makes it costly and difficult for support organizations to adapt-and places an increasingly substantial burden on the agility and efficiency of the business as a whole.

See more White Papers | Webcasts

Ask a question

Ask a Question