|
BackOffice
Book Reviews
Career Tools
MCSE Toolkit
Networking
Resource Centers
Scripting
Batch Files
Env.Variables
Command Line
Logon Scripts
Perl
Visual
Basic
WSH
Security
Utilities
Cybercheese
Administration
Batch Files
Command Line
Env Variable
Logon & Auth
Logon Scripts
MMC
Password Mgmt
Run As
Scheduling Service
Services
Telnet
Time Synch
|
|
 |
Logon
Scripts
|
| A logon
script is a small program that executes automatically when a user
logs on to a particular computer system. These scripts can use
system environment variables to set the client machine's time, map
drive letters to network resources, redirect printing to shared
network printers, and can also call other scripts or executable
programs. You can use a text editor to create logon scripts and then
use the User Properties page to assign different logon scripts to
different users, or assign the same logon script to multiple users,
sites, domains, and organizational units (OUs). |
| Where to start.. |
Environment
Variables in Windows NT/2000
Microsoft Knowledge Base Article: 100843 - Environment Variables in
Windows NT/2000. There are three levels of environment variables in
Windows NT; the system environment variables, the user environment
variables, and the environment variables that are set in the
AUTOEXEC.BAT file. There are also some predefined environment
variables that are set when the user logs on. This article discusses
the following topics: System environment variables, User environment
variables, AUTOEXEC.BAT environment variables, how environment
variables are set, how the path is built, and changing user
environment variables using control panel.
Logon
Script Replication
Logon Script Replication Because Windows 2000
(Win2K) no longer supports the directory replication service, you must
develop an alternative method to replicate logon scripts among Win2K
domain controllers. Microsoft uses the automated File Replication
Service (FRS), which is a key Dfs component, to synchronize file
directories across servers on a Win2K network. You can therefore put
your logon scripts within the SYSVOL directory structure to replicate
them throughout your Win2K network. Source: Windows & .NET Magazine
(Feb 2000)
Simplifying
Network Options Through Logon Scripts
Whether your network consists of a few PCs or thousands of
computers, your workload will be a lot lighter if you standardize
things as much as possible. This process can mean using a standard
format for such items as paths and drive mappings. One easy way of
setting parameters is through logon scripts. In this article, we'll
show you how to create logon scripts and we'll explain the various
options you can use with them. We'll also explain how to replicate
logon scripts. Source: Microsoft TechNet Online
Using
Logon Scripts to configure user work environments
A brief overview of logon
scripts and a few system variables. Source: Windows 2000 Advanced
Server Online Documentation
WSH
Logon Scripts
A look at Windows Scripting Host, how to deploy it, modify
existing scripts, and create powerful logon scripts. Source: Windows
2000 Magazine (Feb 1999)
|
| How
to.... |
Assigning
Scripts Using Group Policy in Windows 2000
In a Windows NT 4.0 domain environment, assigning
scripts to users was more or less restricted to
simple logon scripts. In a Windows 2000 domain,
however, the power of Group Policy unleashes script
deployment capabilities that make NT 4.0 pale in
comparison. Source: Swynk.com
Group
Aware Logon Scripts
The basic problem with batch scripts
is that they're only batch files and are no more capable than batch
files. If you are an old-time NT, Windows, or DOS batch expert, you'll
appreciate the resource kit's Ifmember. @echo off ifmember
"domain admins" if not errorlevel 1 goto user echo you're an
admin! Source: Windows
2000 Magazine (August 1999)
How to Assign a Logon Script to a Profile for a Local User
Microsoft Knowledge Base Article: 258286 - This article describes how to assign a logon script to a profile for a local user's account on a Windows 2000 Professional workstation or a Windows 2000 Server. This logon script runs when the local user logs on locally to the computer.
How to Determine the OS Type in a Logon Script
Microsoft Knowledge Base Article: 190899 - Often, administrators would
like to run software on only their Windows 95 or Windows 98 clients,
or their Windows NT Workstation clients. They may not want to run some
logon script commands on their Windows NT Server computers or domain
controller.
How
to Hide the Logon Script Dialog Box on a Windows NT Client
Microsoft Knowledge Base Article: 176197 - When the logon script runs,
a dialog box is presented until the script finishes. Many
administrators want a way to minimize this dialog box while it is
running, or have it perform in the background so users aren't aware of
the logon script. (updated 1/18/2000)
How to Run a Domain Logon Script in the Foreground with the Start.exe Command-Line Tool
Microsoft Knowledge Base Article: 265016 - By default, logon scripts run in the background. You can use the Start.exe
command-line tool to run local and domain logon scripts on computers
that are running Microsoft Windows 95, Microsoft Windows 98, Microsoft
Windows NT 4.0, and Windows 2000.
HOW TO: Run a Logon Script Once When a New User Logs On
Microsoft Knowledge Base Article: 284193 - This article describes how
to configure a logon script, or program to run one time. These steps
apply only to new users who have never logged on to the computer. If a
user already has a local user profile, or a roaming profile, the
script will run
How to Set the NUM LOCK State at Logon Using a Logon Script
Microsoft Knowledge Base Article: 262625 - 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."
Replicating Logon Scripts and the Directory Replicator Service
Microsoft Knowledge Base Article: 271650 - In the Help files for
Microsoft Windows 2000 Server and Microsoft Advanced Server, the
"Setting up replication of logon scripts" topic refers to the
Directory Replicator service and gives information about placing logon
scripts into an export directory for replication.
|
| Troubleshooting:
Known Bugs and Issues |
Access to the Desktop Is Granted Before Logon Scripts Complete
Microsoft Knowledge Base Article: 275506 - When you configure logon
scripts, there are settings that allow an administrator to control the
maximum time the logon script is allowed to run, and whether to run
the logon script synchronously. When a logon script is run
synchronously, the user does not have access to the desktop until the
logon script terminates.
Client Services for NetWare Does Not Run Logon Script After Initial Boot
Microsoft Knowledge Base Article: 260206 - If a user that has Client Services for NetWare (CSNW) or Gateway Service for Netware (GSNW)
installed on a Windows 2000-based computer attempts to log on
immediately after boot, the NetWare logon scripts do not run. If the
client logs off a and then logs back on, or waits for a few minutes
before logging on, the scripts run as expected.
Domain Logon Script Fails to Run
Microsoft Knowledge Base Article: 142672 - When you log on to a
Windows NT domain from a computer running Windows 95, your logon
script may not run, you may get no indication of the error, and none
of the logon script gets processed.
Logon Script Does Not Run If a User Belongs to a Large Number of Groups
Microsoft Knowledge Base Article: 310930 - When you try to log on to a Windows 2000 domain, your logon script may not run.
%OS and
%OS_VERSION Reported Incorrectly
Microsoft Knowledge Base Article: 160476 - When you run your Novell NetWare login script from Client Services for NetWare (CSNW) or Gateway Services for NetWare (GSNW), the %OS_VERSION
variable is set to MS-DOS V5.00.
Use of "&" Symbol in Server Names Causes Logon Scripts to Fail
Microsoft Knowledge Base Article: 142691 - When you install a Domain Controller with the ampersand character (&) in the server name, Microsoft Windows NT clients cannot process logon scripts. You may see a command shell opened with an error message that the specified file was not found.
|
|
|
|

|
This site and its contents are Copyright
1999-2003 by LabMice.net.
Microsoft, NT,
BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is
affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be
directed to the appropriate manufacturer or vendor. |