cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot Deploy/Update VSE

Jump to solution

Hello,

I've searched quite a bit for a solution to a problem (Google, McAfee materials, forums, etc.) that I just started running into and I've had no luck thus far in figuring out; I'm hoping that someone else might be able to recommend some steps to try or perhaps have run into the same issue.  A little bit of background, I did not architect the ePO solution (currently on 4.6.4) that we use, but I have inherited it.  Previously I have had minimal issues deploying/updating products from ePO in our environment.  I first ran into this issue when trying to deploy an updated version of VSE (8.8 P4) and MOVE AV OSS to our secondary OSS.  I had to install these manually on the host to get them operate properly.

Now unfortunately I am running into the same issue when trying to Deploy/Upgrade VSE.  When trying to update VSE 8.8 P2 > P4 it fails and so does installing VSE 8.8.0.1247 on a system that does not have AV through the Run Client Task Now.  This has worked well for me in the past with both of these specific tasks.

task.JPG

It clearly shows the task failing in ePO, however, the agent log tells a different story (from the best I can tell at least).  This is to a standard non-virtualized workstation.

Friday, November 14, 2014 12:14:07 PM

Info

Scheduler

Added a new task Install VSE 8.8.0.1247 to Scheduler's task list

2014-10-14-12-14-07-
Friday, November 14, 2014 12:14:07 PM

Info

Management

Enforcing Policies for EPOAGENT3000META

2014-10-14-12-14-07-
Friday, November 14, 2014 12:14:07 PM

Info

Management

Enforcing Policies for EPOAGENT3000

2014-10-14-12-14-07-
Friday, November 14, 2014 12:14:07 PM

Info

Agent

Agent finished Enforcing policies

2014-10-14-12-14-07-
Friday, November 14, 2014 12:14:07 PM

Info

Agent

Next policy enforcement in 20 minutes

2014-10-14-12-14-07-
Friday, November 14, 2014 12:14:09 PM

Info

Agent

Sending the next batch of 1 data channel items

2014-10-14-12-14-09-
Friday, November 14, 2014 12:14:09 PM

Info

Agent

Agent communication session started

2014-10-14-12-14-09-
Friday, November 14, 2014 12:14:09 PM

Info

Agent

Agent is connecting to ePO server

2014-10-14-12-14-09-
Friday, November 14, 2014 12:14:09 PM

Info

Agent

No package received from ePO Server

2014-10-14-12-14-09-
Friday, November 14, 2014 12:14:09 PM

Info

Agent

Agent communication session closed

2014-10-14-12-14-09-
Friday, November 14, 2014 12:14:22 PM

Info

Scheduler

Scheduler: Invoking task [Install VSE 8.8.0.1247]...

2014-10-14-12-14-22-
Friday, November 14, 2014 12:14:22 PM

Info

Updater

Checking update packages from repository <redacted>.

2014-10-14-12-14-22-
Friday, November 14, 2014 12:14:22 PM

Info

Updater

Initializing update...

2014-10-14-12-14-22-
Friday, November 14, 2014 12:14:22 PM

Info

Updater

Verifying catalog.z.

2014-10-14-12-14-22-
Friday, November 14, 2014 12:14:22 PM

Info

Updater

Extracting catalog.z.

2014-10-14-12-14-22-
Friday, November 14, 2014 12:14:22 PM

Info

Updater

Loading update configuration from: catalog.xml

2014-10-14-12-14-22-
Friday, November 14, 2014 12:14:23 PM

Info

Updater

Verifying VSE880Det.mcs.

2014-10-14-12-14-23-
Friday, November 14, 2014 12:14:24 PM

Info

Updater

Verifying VSE880Det.mcs.

2014-10-14-12-14-24-
Friday, November 14, 2014 12:14:24 PM

Info

Updater

Update Finished

2014-10-14-12-14-24-
Friday, November 14, 2014 12:14:37 PM

Info

Scheduler

The task Install VSE 8.8.0.1247 is successful

2014-10-14-12-14-37-
Friday, November 14, 2014 12:14:37 PM

Info

Scheduler

Scheduler: Task [Install VSE 8.8.0.1247] is finished

2014-10-14-12-14-37-
Friday, November 14, 2014 12:14:39 PM

Info

Agent

Sending the next batch of 1 data channel items

2014-10-14-12-14-39-
Friday, November 14, 2014 12:14:39 PM

Info

Agent

Agent communication session started

2014-10-14-12-14-39-
Friday, November 14, 2014 12:14:39 PM

Info

Agent

Agent is connecting to ePO server

2014-10-14-12-14-39-
Friday, November 14, 2014 12:14:39 PM

Info

Agent

No package received from ePO Server

2014-10-14-12-14-39-
Friday, November 14, 2014 12:14:39 PM

Info

Agent

Agent communication session closed

I have a primary and secondary (UNC) repository, both appear to be updating correctly and have the corresponding products checked into the current branch. I have tried pushing products to systems reporting to each repository to see if it was specific to one or the other. This is also appears to be true in regards to agent handlers (one internal and one external). Maybe I'm just missing something simple that someone will pick up on.

Hopefully that all makes sense and I appreciate any help I can get!

1 Solution

Accepted Solutions

Re: Cannot Deploy/Update VSE

Jump to solution

Couple of things:

1. When you do a run client task, it will create a log within C:\Windows\Temp\McAfeeLogs; should start with VSE88_Patch4, open that and see why it is failing.

2. When upgrading from p2 -> p4 you don't need to run a product deployment task. If the machines already have p2 on them, create a Product Update task for VSE and select VSE 8.8 under patches. Remeber that the McAfee Agent > General policy - "Updates" tab - controls what branch from the master repository that the agent will pull the patch from. So make sure your agent policy is set to pull VSE p4 from the branch it is checked into. Then from there, if you have the product update task set at the correct node, on the next asci, the agent will update from p2 -> p4.

2 Replies

Re: Cannot Deploy/Update VSE

Jump to solution

Couple of things:

1. When you do a run client task, it will create a log within C:\Windows\Temp\McAfeeLogs; should start with VSE88_Patch4, open that and see why it is failing.

2. When upgrading from p2 -> p4 you don't need to run a product deployment task. If the machines already have p2 on them, create a Product Update task for VSE and select VSE 8.8 under patches. Remeber that the McAfee Agent > General policy - "Updates" tab - controls what branch from the master repository that the agent will pull the patch from. So make sure your agent policy is set to pull VSE p4 from the branch it is checked into. Then from there, if you have the product update task set at the correct node, on the next asci, the agent will update from p2 -> p4.

Re: Cannot Deploy/Update VSE

Jump to solution

Fitch,

Thanks for your reply.

1. I will look into this particular log and see what is has to show me thank you for pointing it out.

2. I actually have been using the product update task (which I was able to use successfully in the past) for patch upgrades, sorry if I hadn't made that clear.  I'll be sure to double-check the repository as well, but I am fairly certain I have that hammered out.