02-24-2006 01:24 PM - edited 03-10-2019 01:54 AM
Hello,
I seem to have a problem one of my clients has a CSA4.0 agent on a server which didn't recieve a final policy before they moved to CSA4.5 MC and then 5.0 MC.
Unfortunatly that final policy included a policy to allow them to disable the CSA client. Now that there on 5.0 they have no way to push to the client the new policys and no way to disable the 4.0 agent.
I am looking for a way to diable the 4.0 agent so that we can install a 5.0 agent. I was wondering if anyone else has encountered this problem and has a solve.
My guess is that I'm going to have to use some third party software/bootcd to start the server up and then either delete CSA or disable the service. So I ask now what everyone thinks of this idea/proposal.
Patrick
02-24-2006 02:55 PM
Net Stop csagent didn't work? I had trouble uninstalling 4.0.x on a machine that was in quarantine mode. I had to reimage it though. I believe there is a manual uninstallation method under bugfixes where you boot into safe mode and manually delete the registry keys.
Sorry I don't remember where it is...
Tom S
02-26-2006 02:24 AM
Tom,
I'll try to manually boot into Safe mode and see if that works other wise I'm going to try the Barts PE boot disk, rename the files and then rename them back when I get my system all the way up and uninstall.
Patrick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide