I have seen once before if the scripts.ini file for a policy is missing, it
can cause startup/logon script not to run. Are you getting any events in
the Application event log? If so what are they? A userenv.log file can be
helpful in troubleshooting this as well.
221833 How to Enable User Environment Debug Logging in Retail Builds of
Windows
http://support.microsoft.com/?id=221833
You might consider editing the local computer policy through gpedit.msc and
give it a startup/logon script. in case there is a problem with the local
policy.
--
--
Gary Mudgett, MCSE, MCSA
Windows 2000 Directory Services
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.