cancel
Showing results for 
Search instead for 
Did you mean: 
kenobe
Level 10
Report Inappropriate Content
Message 1 of 4

Global Reviewer Can Edit Client Tasks - Not good!

Greetings,

We recently found that the Global Reviewer permission set - which has not been altered - now has the permission to edit Client Tasks as the top of our tree in ePO.

Anyone else seen this happen before?  We havent' changed any permissions for this permission set.

Not sure of the timing on this but Friday our server admin went to apply the McAfee Agent 4.8 to the ePO.  We're still trying to figure out how, but that Agent also got deployed to almost every system on our network.  That was not planned as we wanted to keep all our clients on 4.6.3122.  Would installing that 4.8 extension to the server mess up the permission set for Global Reviewer?

Thanks

Ken

Message was edited by: kenobe on 10/1/13 3:03:56 PM CDT
3 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Global Reviewer Can Edit Client Tasks - Not good!

It certainly shouldn't alter the permission sets at all. Can you clarify what "apply the McAfee Agent 4.8 to the ePO" means? Was the agent installed on the ePO server, or checked in to the master repository, for example?

Thanks -

Joe

kenobe
Level 10
Report Inappropriate Content
Message 3 of 4

Re: Global Reviewer Can Edit Client Tasks - Not good!

We were informed that McAfee Agent 4.8 had to be installed on the ePO only.  It was checked into the Repository in Evaluation but all our Agent poliicies say installl Current only, not Evaluation.

I suspect our admin made a booboo and pushed 4.8 out to everyone by mistake but he's not admitting it.

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 4

Re: Global Reviewer Can Edit Client Tasks - Not good!

That sounds like the correct procedure. If it was checked in to the Current branch, then it would be widely deployed (assuming the clients are running a deployment task to install the agent) - but if it was checked into Eval then it shouldn't have been.

If you check on a couple of clients that updated, can you see the deployment happening in the log files, or have the logs moved on?

Thanks -

Joe