Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 4725 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

scanning network drives, datestamps

jjohnson1980

Greetings,

When setting up a sheduled scan there is the option for scanning local hard disks, now does this include network drives mapped to a drive letter or simply hard drives attached to the client only? Also when scanning does it modify any datestamp on a scanned file?  

Many thanks

James

:40883


This thread was automatically locked due to age.
  • 0

    Hi James,

    You can select the mapping drive, or the sharing folder from the networks

    And I've test that the scanning didn't change the timestamp of the files (cmiiw).

    For schedule scanning  files on the networks, i think you should make sure that the user running the scheduled scan have the right permission to access the share folders and files.

    Regards,

    Antonius

    :40949
  • 0

    Hello James and Antonius,

    a scan (any type) will be transparent and not modify timestamps or flags (I know this is still being mentioned as potential issue by backup software vendors).

    Now to the first question: (@James - you are talking about scheduled scans set up from SEC, aren't you?) You have to keep in mind that mapping is done in a user's context. For scans scheduled from the console this is SYSTEM. Thus drives mapped/shares accessed by the currently logged on user(s) can't be scanned as they don't "exist". Antonius is correct that you can additionally select locations on the network for a scan started or scheduled locally. Scans initiated/scheduled from SEC act only on local devices though (otherwise you'd have - similar to the on-access settings - an option to exclude remote files).

    Christian     

    :40955
  • 0

    HI Christian,

    Thats correct that im referring to scheduled scan as setup through SEC. From what you have said it looks like I can assume that  where i have setup in the policy for local drive scan that  it will only be scanning the local c & d drives of each client  (the d drive being one windows creates during setup). All the other drives, bar optical drives and memory sticks, are mapped network drives and would be ignored? Plus what you also said about not modifying date stamps pretty much rules out sophos being the cause. Thats been most helpful.

    Thanks for both of your replies,

    James

    :40961