Printable View
Got this IBM XP machine that is running in the lab. The lab software is incompatible with McAfee Enterprise v7 antivirus. Is it possible to disable the software for one user and then create another account that would run the antivirus after the lab application is done. Should I create a group policy?
Why is it necessary to run McAfee at all? Why don't you just disable it all together and run a free version or 30 trial of another brand of software?
also, I having a bit of trouble understanding this sentence:
Is it possible to disable the software for one user and then create another account that would run the antivirus after the lab application is done.
Which software are you going to disable, Mcafee or the lab software? Also I don't understand the purpose in creating another McAfee account.
Thanks,
Orangeman
Sorry, alot is going on. Anyway, I meant to say disable the antivirus software. To answer the second question:I mean have a user account so that the antivirus will then be able to run. I hate to have a machine vulnerable to attack by all the "crap" that is out there. Plus, what if a free version is also incompatible with the lab software..?Quote:
Originally Posted by Orangeman
Not really a solution, but a thought or two...if the lab software (are you keeping a trade secret or will you be able to divulge the package) is incompatible with this version of AV, contact the maker, and find out what Virus protection does work…
What symptoms are you receiving? I don’t know Mcaffee, but I presume that by simply turning off the real time monitoring isn’t providing the desired results…I also presume that you are looking for an automated setup, hence the two profiles…perhaps use of the KILL command line utility in a script in the startup of the one user, one designed to shutdown the AV…like I said, just thoughts…
Sounds like a lot to ask but you never know, a solution may be out there…
Something else, most Virus software out now allows you to assign directories that are exempt from scanning during realtime or system scans, perhaps making that programs folder exempt might do the trick…
Doh! That could be it! I'll try the last solution and see if that works.Quote:
Originally Posted by Ya_know
Reinstalled and then excluded the MassLynx directories from being scanned at any time.
Did that solve your issue? If so, let Gollo know that I helped out around here this week, and I should be allowed to play! :D