domain logon script problem for medium scale network

[L Smith]

Anyone have any idea what the following problem could be?

Computers when logging onto the domain server at a medium
sized network of one of our clients (approx 70 computers)
fail to execute any logon scripts designated to either
the entire domain or individual organisational units.

The scripts are stored as (example) mapdrive.bat and
accounting.bat in the winnt\sysvol\domain\scripts folder
(and have been saved as ansi standard as unicode causes
problems) and have added to the list of scripts to
execute on logon in the default domain policy section.

Network is gigabit switched, and checking the 'scripts
fail to execute on a slow network' problem and policy
settings hasnt yielded any result yet. Anyone else had a
similar problem?

- L Smith

 

[Tim Hines [MSFT]]

Have you verified that clients are receiving the domain policy? Run
gpresult.exe to verify this. You should check the application log for
errors. Verify that you can run the script manually. If you are specifying
the script in a GPO, then the script needs to be placed in the scripts dir
of the group policy object, IE.
C:\WINNT\SYSVOL\sysvol\mydomain.com\Policies\{31B2F340-016D-11D2-945F-00C04F
B984F9}\User\Scripts.


--
--
Tim Hines, 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.





--
--
Tim Hines, 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.

 

[BP]

Due to lack of additional info a very wild guess (assuming poloicy and
client side extensions are being processed)...
Have you enabled a policy that prohibits access to the command prompt for
these users ?
That will disable the execution of those scripts also...
Regards,
BP