McAfee VSE is in an unstable state. On-acess scan and Acess Protection are disabled

We have 400 Windows server 2003 machines within a container in ePO. The policy is set so that Acess protection is enabled as well as on-access scan.  We found that the servers when you do a remote desktop into them on-acess scan and access protection are disabled. When we try to enable them it would not allow us to. We've come to the conclusion that VSE  is in a broken state. We cannot do anything from EPO to administer it and we are having a bunch of error message when trying to uninstall it locally from the machine.  We've contacted McAfee support and they mentioned that we need to uninstall and reinstall and gave us a ripper tool to do so. The only problem is we would have to manually re-install McAfee for 400 machines. Is there a simpler  process to resolve this from an EPO standpoint?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
Apoarently epo deployment task does not have a reinstall option. It simply has does an install or inplace upgrade. Looks like more of a batch job to do the removal..e.g. the batch script is maintained on the EPO server and shared out to the entire organization

The manual will not be an easy feat for huge deployment..
joukiejoukAuthor Commented:
Hello btan,

I like the first method you had mentioned, but I am not familiar with the process even after reading about it. Is there a video on this? I think that would help me more. Or maybe a reference with plenty of screenshot examples? I have some questions about it. Please see below.

btanExec ConsultantCommented:
No such video to my best knowledge. Will be clearer if you can see the cmd content.

There are three main folder to point to and also the common network share server ip address.
In that shared folder, just need to make the parent folder created store this cmd as well as its subscripts

 .. See those can manually (instead of clone) create the same structure under your main folder containing the cmd files. See all the structure in

For the admin right, when you run the cmd the account login tends to be your user which will not be able to run as lesser privileges in OS. So need to run in admin
..e.g. From GPO , has something like in the Computer Config -> Start up Scripts GPO to run the cmd and have it installed by the 'System' account. See the below
joukiejoukAuthor Commented:
I'd really like to get your method going because it sounds like a savior solution, and less stress. However, I am really confused by the github method. Is there another article (not using github) on this? Or maybe, some screenshots about this?

At the moment, seems like VSE is in a broken state and only happening to Windows Server 2003 Servers.
btanExec ConsultantCommented:
Best effort on those files as only means is to try out and pardon me not finding more sources. Another I saw on script based is below though I did not go further. For your info.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Anti-Virus Apps

From novice to tech pro — start learning today.