I have an inventory login script that is apparently causing some issues.
Although the first 20 PCs I tested on worked fine, I am now being told that some users are getting an error "invalid file path Line 51".
line 51 has "If (objFSO.FileExists(strFullName)) Then WScript.Quit"
what this script does is write inventory information to a file that resides in a public folder when they login, unless the file already exists, then it skipsthe entire process.
these PCs already have the file existing.
what I am being told (I havent seen this for myself yet) is that the users have login issues when this happens.
they try to open Outlook and it prompts them for domain, username, password as if they were not logged in at all.
it has been suggested that I move this to a logOFF script.
I guess my question is: can a script like this keep someone from logging onto the network? or at least slow down the process?
what is strange is this is only happening to maybe a handful of PCs out of all we have.
Although the first 20 PCs I tested on worked fine, I am now being told that some users are getting an error "invalid file path Line 51".
line 51 has "If (objFSO.FileExists(strFullName)) Then WScript.Quit"
what this script does is write inventory information to a file that resides in a public folder when they login, unless the file already exists, then it skipsthe entire process.
these PCs already have the file existing.
what I am being told (I havent seen this for myself yet) is that the users have login issues when this happens.
they try to open Outlook and it prompts them for domain, username, password as if they were not logged in at all.
it has been suggested that I move this to a logOFF script.
I guess my question is: can a script like this keep someone from logging onto the network? or at least slow down the process?
what is strange is this is only happening to maybe a handful of PCs out of all we have.
