Article ID: 262625 - View products that this article applies to.
This article was previously published under Q262625
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
Windows preserves the keyboard state when a user logs off. When a user logs off and then logs on again, the NUM LOCK state is set to "off."
There may be times when you want to set the NUM LOCK state to "on" when a user logs on. You can accomplish this using a script file that you can distribute at startup or through Group Policy. NOTE: This article relies on the use of Microsoft Windows Script Host. Windows 2000 and Windows 98 clients properly run .vbs scripts. To run .vbs scripts on Microsoft Windows NT 4.0 and Microsoft Windows 95 clients, you can install Windows Script Host on those clients.
If Windows Script Host is already installed, Microsoft strongly recommends that you download the latest version of this tool to ensure that it works properly. You can find the latest information about Windows scripting at the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/ms950396.aspxFor additional information, visit the following Microsoft Group Policy White Paper Web site:
To configure a script to change the NUM LOCK state, use the following steps:
Running the Script at StartupTo configure the script to run locally using the Startup folder, copy the Numlock.vbs file to the user's startup folder that is normally found in the user's profile path. To configure the script to run for all users, put the script in the Startup folder in the All Users profile.
The following example shows the default path for this folder:
Documents and Settings\All Users\Start Menu\Programs\Startup
Running the Script Using Group PolicyTo configure the newly created script to run using Group Policy, you must first copy the Numlock.vbs script file into the Group Policy logon script folder.
The following example shows the default path for a local logon script:
%SystemRoot%\System32\GroupPolicy\[User|Machine]\Scripts\LogonThe following example shows the path for a domain logon script:
%SysVolFolder%\Sysvol\Sysvol\Domainname\ScriptsAfter you copy the script to the appropriate location, use the following steps:
Article ID: 262625 - Last Review: August 8, 2007 - Revision: 6.5