DOCUMENT:Q102907  01-SEP-1993  [W_NT]
TITLE   :How to Troubleshoot Local Logon Scripts with Windows NT
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:

----------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Windows NT operating system version 3.1
 - Microsoft Windows NT Advanced Server version 3.1
----------------------------------------------------------------------

SUMMARY
=======
 
This article contains a checklist of potential problems with local
logon scripts. A logon script is similar to a batch file because it 
performs a series of commands when a user logs in to his or her
account.

MORE INFORMATION
================
 
If problems arise with a logon scripts, use the following list to
troubleshoot the problem:

NOTE: If the logon script is to be set up for a Windows for Workgroups
computer, the Windows for Workgroups computer must have the Windows NT
domain specified in the LAN Manager domain portion of Control Panel
networks, rather than just assigned to that workgroup.
 
 - Make sure the logon script is in the following directory:
 
      \winnt\system32\repl\import\scripts
 
   The only valid path option is a subdirectory of the default logon
   script directory. A path to any other directory or using the
   environment variable %HOMEPATH% will cause the logon script to
   fail.
 
 - If the file system on the partition containing the logon script
   directory is NTFS, make sure the user has read rights to the logon
   script directory. If no rights have been explicitly assigned, the
   logon script may fail without providing an error message.
 
 - Make sure the logon script has a filename extension of either 
   "CMD" and "BAT." A script with any other extension will fail. The
   "EXE" extension is also supported, but only for genuine executable
   programs.
 
   Attempting to use the .EXE extension for a script file will result
   in the following error message:
 
      NTVDM CPU has encountered an illegal instruction.
 
   To remove the error, terminate the application or the virtual
   MS-DOS machine (VDM).
 
Additional reference words: 3.10 tshoot
KBCategory:
KBSubcategory: winnt

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1993.