cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

ePO 4.6 deploys failing with expired

I recently installed ePO 4.6 (our previous server with V3.6 died) . I am trying to deploy the MA 4.6.0 on the PCs and servers that already have VS and whatever else would have been installed under V3.6 and also to install it on our one new server that doesnt have anything McAfee installed. Every Task dies with an "Expired" error. I did some research and in the serevr.log did find an error about SQL server - failed to connect .

I did do  the https://your_epo_server:8443/core/config test and it worked. I even changed values to make sure. I also checked under the server registration that the right SQL server info was there. Then I rebooted the server. Now I get no errors in the server log. But I'm getting the same problem. No matter whether I run 1 deploy task on an unmanaged machine or 21 they all fail. Anyone have any ideas in what I might have missed?

I have attached the orion log related to my last 1 system deploy task.

8 Replies
Highlighted
Level 14
Report Inappropriate Content
Message 2 of 9

Re: ePO 4.6 deploys failing with expired

Remove the present client task.

Go into your Software manger in epo and update your repository with latest package of MA 4.6 and update its extensions.

Creat client task again.

Push the task to your clients and see what happens?

Highlighted

Re: ePO 4.6 deploys failing with expired

That didnt work.

I removed all of  MA 4.6. Re-downloaded and installed and registered.

Ran the deploy on a server and got the same error.

Then I uninstalled the MA and VS on my personal PC and tried a push and that didnt work. Then I ran FramePkg.exe on my PC to get the Agent and tried doing a wake up call of that Agent and got the Expired message. No matter what I do I can't get past Expired. Any ideas anyone?

Highlighted
Level 14
Report Inappropriate Content
Message 4 of 9

Re: ePO 4.6 deploys failing with expired

Are you deploying via same deployment task which was created earlier ?

Highlighted

Re: ePO 4.6 deploys failing with expired

Ahhhh the system lied to me. It said it failed yet when I went to look at the System Tree my PC is now managed with all  the PC's info and I was able to create a new task to load VS 8.8 on my PC and it looks like it works. So I'm thinking I will need to go to every PC with MA and uninstall and manually install and then I should be able to depoy the VS upgrades where necessary.

Thanks for the suggestions. Will add more info if/when it works or doesnt.

Of course that still doesnt answer why I cant get the system that doesnt have old software to work ....

Message was edited by: bonniebeth on 5/1/13 1:46:13 PM GMT-06:00
Highlighted
Level 14
Report Inappropriate Content
Message 6 of 9

Re: ePO 4.6 deploys failing with expired

Creat a MA removel task and push to machines in question and see if it removes agent?

use frminst/forceuninstall  under the task creation wizard in command line section.Once it finishes try installing again.

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 7 of 9

Re: ePO 4.6 deploys failing with expired

This won't work - the agent will explicitly ignore this command. (If you think about it you're trying to run a task that is trying to remove the process that is running the task.)

Instead of using a task, what happens if you send an agent install to a machine using the Send Agent Install wizard?

Thanks -

Joe

Highlighted
Level 14
Report Inappropriate Content
Message 8 of 9

Re: ePO 4.6 deploys failing with expired

 (If you think about it you're trying to run a task that is trying to remove the process that is running the task.)

OOOO, gotcha.

Highlighted

Re: ePO 4.6 deploys failing with expired

Well for some inexplicable reason my systems are mostly managed. First there was the one I was able to get done yesterday by manually deleteing and insalling MA 4.6 and then able to deploy VS 8.8 to. Then there was the machine I did today followng those same steps. Then miracoulously 2 more systems resolved themselves. Then I tried the wake up call to all the agents and almost all came back as managed and then I deployed to all but 2 machines.

The ONLY thing I can think of is the server that the db resided on was rebooted today. I did reboot the server the epo is on several times yesterday.

So my problem seems to be resolved. I've been able to update several machines to the latest VS using ePO tasks and I just have a few machines I'll need to wrestle with.

So thanks to you both for your suggestions. I was working my way through them when this all happened.

Just to correct this reply:

I realized later that the SQL Server used by the ePO is on the same machine as the ePO so that reboot couldn't have effected this. Also I realized the two machines that were the first to automatically change to managed had not been turned on the previous day when I had been working on the problem.

Anyways everything seems to be going OK and I'm down to one stubborn machine.

Message was edited by: bonniebeth on 5/3/13 11:10:57 AM GMT-06:00
You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community