Tech Support > Microsoft Windows > Windows Server > logon script location - 9x clients to 2k3 server
logon script location - 9x clients to 2k3 server
Posted by dmini on May 1st, 2005


I am trying to help users on a very locked down network in a school. They
need logon scripts from 9x to their 2k3 server. Is this still possible? - Ive
done it on 2k. I am assuming it should be on the netlogon share, as in
previous versions, but I cannot see the share- I have seem some hints it
doesn't exist by default - but I can see almost no shares at all on the
server, so am working blind. The support company say they will not support,
unless the workstations are XP, the school cannot afford to upgrade all
workstations! Does it still work with 9x, where should it be? Is there
anything else I need to look out for?
Sorry to be asking stupid questions like this, but I cannot find the answer
outright, and havent had much experience of w2k3.

Posted by Pegasus \(MVP\) on May 1st, 2005



"dmini" <dmini@discussions.microsoft.com> wrote in message
news:474BEE13-A846-4DC5-80BA-34417B5F1DEE@microsoft.com...
Start a Command Prompt on the Win2003 server, then type this command:

net share

Can you see a share called "netlogon"? If you can't, create it like so:

md c:\Windows\Netlogon
cacls c:\Windows\Netlogon /t /e /g everyone:r
net share netlogon=c:\windows\netlogon

The physical location of the "netlogon" share is not all that important -
it's the share name "netlogon" that counts.

You can now place a batch file called "netlogon.bat" (or
any other name) into the netlogon share. Lastly, you must
place the name "netlogon.bat" as the logon script name
into the user's account profile.

If your Win9x clients' network settings are set to get validated
by a WinNT domain then the logon script should execute at
logon time. However . . . I have come across a number of
Win9x clients that refused to play the game. In such cases
I walk around the problem: I place the following batch file
into the startup folder of the Win9x PCs:

@echo off
\\YourServer\NetLogon\netlogon.bat

This works quite nicely, because the logon script is still centrally
controlled from the domain controller.