Logon script policy help

[Steve Gould]

I just upgraded my NT4 PDC to Windows 2000/AD today. I have/had a major
logon script failure. Windows 95 and 98 workstations could still launch
their logon script files, but 2000 and XP workstations couldn't. Finally I
went into the default domain policy, added copies of the script files to the
directory, and added this item to the "logon" policy: %username%.bat

Now I have Windows 95/98 workstations launching the old logon batch files
and 2000/XP machines launching the scripts through the default policy. All
seems well for tonight, but is this correct? Windows help files are pretty
bland on this area. This also has a problem because now I have multiple
script files in different directories. What am I missing here? I made sure
the sysvol directories and shares had "everyone" read, but that didn't help.


--
Steve Gould
Network Administrator
APA - The Engineered Wood Association
253-620-7454
(e-mail address removed)

 

[Klaas J.M. Langhout [MS]]

If you were running logon scripts before, they should exist in the
\\<dc-name>\netlogon directory and, after the upgrade of the NT4 pdc to W2K,
you should be able to view the properties on a user object to see what the
script path is, it should be the same as a file or path in the \netlogon
share and, that file (batch or cmd) should still be there as well.

e.g.

user 'foo' has a scriptPath of "runme.bat" and, the dc "bar" has the file
\\bar\netlogon\runme.bat

Hope this helps a bit,

Klaas,
This posting is provided "AS IS" with no warranties, and confers no rights.