I am having some issues that I dont know if EndPoint is the cause, so I am throwing out some questions in hopes that someone has had similar problems and have solved them. These problems have come up around the same time we upgraded from SAV to SEP 11,, but not sure if they are related to the upgrade.
1. We have remote clients accessing our Terminal Server through RDP, we have setup in there startup programs to run when they connect to an RDP session, one program, which is a batch program that copies a database from there Local PC to our Terminal Server, this job relies on a mapped drive from the terminal server session to the local PC's hard drive folder location. the "CopyPhoenix bat", contains this one line Copy /Y Z:\P4w.mdb Q:\GJFuelData, the terminal server session mapped drive is "Z", mapped to the users local PC hard drive folder C:\Program Files\Phoenix\Data\ and the database P4w.mdb is in this folder, this database is copied through the RDP session to our server's Q: drive and put in the folder Q;\GJFuelData. This batch job has been running reliably and faithfully for years,, but since we have upgraded to Symantec Endpoint 11, we have had a rash of problems, some to do wiht EndPoint getting in the way of UPHClean and also with RTVscan.exe holding file handles and resources, we have excluded these issues. Anyway the issue I am seeing now is that when that batch job fires off on client login, it appears to me that the RDP session cannot see its mapped drive,, but when I remote into that PC and do the login, test the copy fails right away,, but if I stay in that seesion for a few minutes and also click on the mapped drive which shows and "X" on the mapped drive,, it refreashes the connection and I can run the batch file manually and the copy works fine,, kind of a timing issue???
I am wondering if Symantec EndPoint could possibly be the culpret,, maybe its holding up something that normally connects the RDP session mapped drives quickly and causes the inital client login batch program to fail, because the mapped drive is not available yet??? just grasping at straws here,, but it is quite coincidental to the time when we upgraded from Symantec SAV to SEP???
2. Another issue is the our Microsoft DPM (Data Protection Manager) backups have been coincidentall failing to run since about the same time we upgraded from SAV to SEP and I am wondering if there could be an issue here. Could this be a possibility also???
Any help or confirmation of SEP being in the middle of these issue's would be appreciated.
Thanx
-TheCoop