J
Jordan
I have a pretty basic login script that clears old mapped drives, syncs the
time, then maps the current drives. Most days there is no problem with the
scripts, but I have just a few computers that at least once a week have a
problem mapping to the drives. The get these errors:
=====
"There are open files and/or incomplete directory searches pending on the
connection to O:"
"There are open files and/or incomplete directory searches pending on the
connection to P:"
"There are open files and/or incomplete directory searches pending on the
connection to Q:"
=====
This is the login script
=====
Net Use * /Delete /Yes
Net Time %LOGONSERVER% /set /y
Net Use O: "\\Files\O Drive" /YES
Net Use P: "\\Files\P Drive" /YES
Net Use Q: "\\Files\Q Drive" /YES
======
What I can't figure out is why these few computer have the problem, but no
one else does. If I run the login script manually
(\\domaincontroller\netlogon\logon.bat) after they have logged in for a
minute or two, the script runs fine even though it just failed at logon.
time, then maps the current drives. Most days there is no problem with the
scripts, but I have just a few computers that at least once a week have a
problem mapping to the drives. The get these errors:
=====
"There are open files and/or incomplete directory searches pending on the
connection to O:"
"There are open files and/or incomplete directory searches pending on the
connection to P:"
"There are open files and/or incomplete directory searches pending on the
connection to Q:"
=====
This is the login script
=====
Net Use * /Delete /Yes
Net Time %LOGONSERVER% /set /y
Net Use O: "\\Files\O Drive" /YES
Net Use P: "\\Files\P Drive" /YES
Net Use Q: "\\Files\Q Drive" /YES
======
What I can't figure out is why these few computer have the problem, but no
one else does. If I run the login script manually
(\\domaincontroller\netlogon\logon.bat) after they have logged in for a
minute or two, the script runs fine even though it just failed at logon.