Discussion Locked

Win 9x operating and a W2K environment

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Where can I find information on how Windows 9x machines operate in a Windows 2000 environment? I am running logon scripts and my Windows 9x machines are not running the scripts.

9 replies

by awilliam3

I've already been to Microsoft'w knowledge Base and there is not much iformation that pertains to Windows 9x operating in Windows 2000 environment. I already know about the active directory client but that is about all they have that is helpful. There is very little there about logon scripts.

by michael modarelli

I have had a similar situation with clients not running the logon scripts. Once I networked all clients using static IP addresses, scripts started running more reliably. (great for a smaller network)

Worth a try.

by vgilcrease

9x clients do not support %username%. Any logon scripts with that in it will not run on a 9x box. Also to have a logon script run on a 9x box from a 2K server you must put the logon script in the netlogon share and give it a *.bat extension. It will not run if it is has a *.cmd extension. Go into AD users and computers and go to the properties of a user. Then go to the profile tab. On the profile tab put in the name of the logon script where it says logon script. However, the login scriptmust already exist in the netlogon share of 2K server before you do this. Also make sure paths and access rights are correct. Create a test account and logon script with a pause statement in it. Then go and logon with this account and study any error messages that pop up when the script runs. This will help you troubleshoot the problem and this is how I found out my solution to the problem.

by jmstitt

Hi. for a script to run from a Win2K server to a Win98 or Win95 machine, it must have the bat extension. IE lablogin.bat.

If you try to run the script with a cmd extension, Win9x doesn't know what a cmd file is.

Just change all scripts to the bat extension. Bat files run slightly slower than cmd files, but they work for all machines (win9x, NT, 2000). Here is a sample. I push this to all lab machines running win9x

This is one script stored in *\winnt\sysvol
script name: lablogin.bat

net time \\ksd-bdc /set -y *sets time/date
net use p: \\ksd-public\public *sets pub dir
net use s: /home *maps users home dir

*the home directory is set in active directory in the profile for each user

This discussion is closed to new replies.