OK, here we go
Were running ePo 2.5 on a Win2k server.
Now then, the main problem is simply that the enforcement of policies seems completely random and inconsistent.
An example,
we have 2 XP machines, both of which HAD version 4.5 of VScan. Now, straight from the kick off there was no policy for any version of virus scan available in the policies pane for each of these computers. We successfully installed the agent however.
Meaning any polices we tried to enforce were not picked up by these machines.
We added them to a seperate site of thier own.
After much searching through the NAI support we discovered that 4.5.1 sp1 was required for XP management via ePo. Fair enough, we downloaded 4.5.1 sp1 , added it to the repository and applied it to both machines via a force install policy.....NOTHING HAPPENED. STILL no policy available in the details pane.
We repeated the above after manually removing Vscan from both machines. STILL unable to apply an install of both 4.5 and 4.5.1.
So we installed 4.5.1 sp1 manually on one of the machines, and 4.5 manually on another, sent the agent no problems as usual, STILL no policy available to each machine. The agent has determined that the machine has VScan (looking in the properties tab confims this) but there is NO POLICY available in the policy tab ---WHY!!!!!
Inevitably we are therefore uable to apply any policies to either machine - we tried to force an uninstall of 4.5 from the machine we manually loaded with 4.5 and then force an install of 4.5.1 on it. The agent simply does not pick up policies for Vscan for either machine.
We were under the illusion that this was an XP problem only, and then low and behold it begins to affect an NT machine running 4.5. This time, whilst being able to configure a policy for this machine, the policy simply was not being enforced for Vscan, again, the agent simply was not picking any Vscan policies up..WE ARE UNABLE TO UNINSTALL Vscan from this machine via ePo.
Curently we have deleted all agent and Vscan software from both XP machines and are unable to install agents on these machines.
we are also unable to run scheduled tasks on most machines, as I have described in my post in the previous thread (epo tasks).
BRING BACK MCON!
Were running ePo 2.5 on a Win2k server.
Now then, the main problem is simply that the enforcement of policies seems completely random and inconsistent.
An example,
we have 2 XP machines, both of which HAD version 4.5 of VScan. Now, straight from the kick off there was no policy for any version of virus scan available in the policies pane for each of these computers. We successfully installed the agent however.
Meaning any polices we tried to enforce were not picked up by these machines.
We added them to a seperate site of thier own.
After much searching through the NAI support we discovered that 4.5.1 sp1 was required for XP management via ePo. Fair enough, we downloaded 4.5.1 sp1 , added it to the repository and applied it to both machines via a force install policy.....NOTHING HAPPENED. STILL no policy available in the details pane.
We repeated the above after manually removing Vscan from both machines. STILL unable to apply an install of both 4.5 and 4.5.1.
So we installed 4.5.1 sp1 manually on one of the machines, and 4.5 manually on another, sent the agent no problems as usual, STILL no policy available to each machine. The agent has determined that the machine has VScan (looking in the properties tab confims this) but there is NO POLICY available in the policy tab ---WHY!!!!!
Inevitably we are therefore uable to apply any policies to either machine - we tried to force an uninstall of 4.5 from the machine we manually loaded with 4.5 and then force an install of 4.5.1 on it. The agent simply does not pick up policies for Vscan for either machine.
We were under the illusion that this was an XP problem only, and then low and behold it begins to affect an NT machine running 4.5. This time, whilst being able to configure a policy for this machine, the policy simply was not being enforced for Vscan, again, the agent simply was not picking any Vscan policies up..WE ARE UNABLE TO UNINSTALL Vscan from this machine via ePo.
Curently we have deleted all agent and Vscan software from both XP machines and are unable to install agents on these machines.
we are also unable to run scheduled tasks on most machines, as I have described in my post in the previous thread (epo tasks).
BRING BACK MCON!
