Endpoint Protection

 View Only
  • 1.  Endpoint Conflict w/ Batch File

    Posted Jun 19, 2011 11:51 PM

    I am using Symantec Endpoint Protection Version 11.0.6200.754 on a Windows 7 platform.  I have created a batch file that runs when the computer boots up and proceeds to save the contents of my drive to an external drive.  Enpoint conflicts with the batch file.  The result of this is that the batch file does not run to completion and becomes inoperable i.e. I can't clos the file and stop it from running.  The only way to close the batch file is to shut down.  When I shut down, the computer says "Logging Off" and just continues to spin around logging off until I hold the power button and manually force shut down which then results in having to boot up again in safe mode, etc. etc. etc.  The batch file, frankly is more important to me than whatever protection I'm supposedly getting from Endpoint.  However, I would like to find a way for these two things to make nice and get along.  Otherwise I'mm have to uninstall Endpoint and use another product.  Any ideas how to solve this problem?



  • 2.  RE: Endpoint Conflict w/ Batch File

    Posted Jun 20, 2011 03:11 PM

    where is the batch file ? can u create an exception and try if thats working.

    there is an option in AV policy, that says to start sep, when computer starts, try that option, might work.



  • 3.  RE: Endpoint Conflict w/ Batch File

    Posted Jun 20, 2011 04:16 PM

    Try using ROBOCOPY instead of using regular copy or xcopy. 

    I have seen Windows 7 hang because of the extra overhead when using the "graphical" copy.

    Or, if you are unsure of what is blocking, you can try HOBOCOPY.  That's not a typo.  It's almost exactly like Robocopy except it will allow you to copy files even if they are in use.

    Both are command line and should not be affected from SEP.

    Robocopy is built into System32 on Windows 7.