One machine unable to run logon scripts

  • Thread starter Thread starter Andy B
  • Start date Start date
A

Andy B

Hopefully someone here can help with this predicament, I have a 450
workstation network, with 2 DC's using Win 2k Active Directory, I
recently experimented with splitting our large Student OU into
classroom OU's, which seems to work fine (after I applied the logon
scripts), there is one machine on the network which will point blank
refuse to run the logon script for it's OU, I have removed it from the
domain by forcing it into a workgroup, rebooting, then adding it back
to the domain which succeeds, this was a trial and error after 2 other
machines displayed the same behaviour, which incidentally were in the
same OU.

.. However it will not run the script (Batch file which then launches a
kixtart script), located in the OU for the classroom. Every other
machine works fine except for this one, there are 22 machines on the
segment. I can ping the machine just fine, it can ping anyother
machine, I can browse it's c$ share with no problem, I can use VNC no
problem on it, pathping reports no packetloss, so I don't think
there's a connectivity problem.

I have checked permissions on the scripts, I can log in on other
machines in the concerned OU as either an Admin or a normal user
account and the script runs, all except for this one machine.

Has anyone else experienced the same problem ?

Hope someone can help before I go mad and rebuild the machine.
 
Check the application log and system log on the client for errors. Have you
verified that the computer is receiving the group policy that logon script
is in? You can run GPresult.exe /v to determine if the policies are
received. You can also enable debugging of the scripts client side
extension.

To create the log add the following registry value:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Name: GPTextDebugLevel
Type: REG_DWORD
Data (Hex): 10002

The file is \winnt\debug\usermode\gptext.log
Review the log and post any errors in the group.


--
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.
 
Check the application log and system log on the client for errors. Have you
verified that the computer is receiving the group policy that logon script
is in? You can run GPresult.exe /v to determine if the policies are
received. You can also enable debugging of the scripts client side
extension.
Click to expand...

Sorry, I forgot to mention that the machines within that OU are
recieving the policies, such as proxy settings, home page etc. However
I will try your method and post back the results (Monday).
To create the log add the following registry value:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Name: GPTextDebugLevel
Type: REG_DWORD
Data (Hex): 10002

The file is \winnt\debug\usermode\gptext.log
Review the log and post any errors in the group.
Click to expand...

Thank you for your response
 
Check the application log and system log on the client for errors. Have you
verified that the computer is receiving the group policy that logon script
is in? You can run GPresult.exe /v to determine if the policies are
received. You can also enable debugging of the scripts client side
extension.
Click to expand...

Tried the gpresult /v and analyzed the results, there were a few
errors about something to do with 1789 and SIDs (can't remember off
hand as I'm now at home)

The end result was we ended up reformatting the workstation as it was
needed (quite urgently), and a new installation fixed everything.

Thank you for your response and time
 
Back
Top