Page Last Updated: 21/02/2010
Testing the Login Script or Using the Script Locally

You should test the login script before you use it. You can also use the same technique if you want to use a login script on a machine or a user that isn't part of a domain.

This technique only works for local machines - if you want to test with a domain login you should follow the instructions for implementing the script here.

1. Create a new directory on your machine (location isn't important) called "Netlogon". The name must be as shown.
2. Share this new directory, also with the name "netlogon" and give the share Read only permissions to everyone.
3. Place your login script in to this new folder, along with any other executables you have used, such as "ifmember".
4. Open Computer Management (Control Panel, Administrative Tools) and click on the "User Manager" item.
5. Use this local User Manager to create a new local user for your machine.
6. Modify the properties of the user to add the login script. Just enter the name, for example "login.bat"
7. Logout and then then login to your machine with the new user to see if your script works correctly.

If you wish to record a log of the login script, then see Recording Login Scripts Results page - here.

About this site

This information originally started life as a page on amset.info, our community assistance site. However that site is targeted at Microsoft Exchange server, as Sembee Ltd. is a Microsoft Exchange consultancy. Therefore it was moved to its own domain in early 2010. Traffic from amset.info is directed here.

Other sites that are owned and operated by Sembee Ltd include kbsearch.info, certificatesforexchange.com, dosprompt.info, office-recovery.info, wuauclt.info, blog.sembee.co.uk, exbpa.com and amset.info.