I am baffled by the following and hope someone might be able to point me in the right direction. I have a Domain startup script that points to a network folder .bat file. Within this bat file is the following script at this time.
echo %DATE% %TIME% %COMPUTERNAME% %systemroot% access>>\\dclib3\MaintScript\log\maint_log.txt
echo %COMPUTERNAME%>>\\dclib3\MaintScript\log\syslog.txt
What baffles me is that it always logs the computer name in maint_log.txt but it only sometimes logs correctly in syslog.txt.
My theory is this....we have domain computers spread across an entire county with various bandwidth back to the domain controllers. My theory is that sometimes when a computer startsup, it checks for the domain controller, but if it is a little slow connecting, it logs on with a cached username and password. My theory is that something similiar is happening with the startup script. It tries to connect to the domain controller and run the current startup script, the connection is a little slow, so it runs the last known startup script it has cached, which might not be the up to date one (for example, the second echo command was added several weeks after). Does anybody know if this is correct? Does a domain computer cache a startup script similiar to caching a domain username and password in the absence of a domain controller?
echo %DATE% %TIME% %COMPUTERNAME% %systemroot% access>>\\dclib3\MaintScript\log\maint_log.txt
echo %COMPUTERNAME%>>\\dclib3\MaintScript\log\syslog.txt
What baffles me is that it always logs the computer name in maint_log.txt but it only sometimes logs correctly in syslog.txt.
My theory is this....we have domain computers spread across an entire county with various bandwidth back to the domain controllers. My theory is that sometimes when a computer startsup, it checks for the domain controller, but if it is a little slow connecting, it logs on with a cached username and password. My theory is that something similiar is happening with the startup script. It tries to connect to the domain controller and run the current startup script, the connection is a little slow, so it runs the last known startup script it has cached, which might not be the up to date one (for example, the second echo command was added several weeks after). Does anybody know if this is correct? Does a domain computer cache a startup script similiar to caching a domain username and password in the absence of a domain controller?