ePO 3.0 SP2a - Input?

[bfralia]

ePO 3.0 SP2a has been out for a little while and hasn't been pulled.

How's everyone's experience going with this?

 

[epochap]

You have to manually download the file and install it in your epo server.The agents will be automatically upgraded after installing as supposed to be.

 

[qtin]

I think they mean removed from the download site like 3.0.2 was.

I've been running it and haven't really seen any issues. Of course I really didn't see too many issues w/ 3.0.2 so I guess I'm lucky

 

[bfralia]

I just wanted to know what people using SP2a think of it so far. I already have it downloaded but haven't installed yet.

 

[simonjcook]

We're upgraded to SP2a on two out of three servers. All seems to be fine at the moment. It fixed a major issue we had with Naimserv.exe running at 100% cpu on one server. Waiting for a rollout of VSE to finish on the remaining server before applying SP2a on it. Would recommend backing up your database and server before applying it though just in case.

 

[f3rrar1az]

Pretty good, We had the run time unknown issue with repository pulls and replications. A reboot was required though once the patch was applied.

 

[cottonpants]

I took the plunge last week and so far so good (knock on wood). I'm still in the middle of upgrading everyone's agent but that is going smoothly as well.

The actual upgrade process was pretty clean for McAfee standards. The 'Finishing Installation' stage took a bit longer than I expected, but it looks like it did a lot of stuff (new package checkins and a bunch of sql stuff). I didn't need to reboot which was a pleasant surprise.

 

[chiefsmt123]

I just installed a new ePO server and patched it to SP2a. I grabbed the agent of the server and installed it on a box running VSEN7.0. The repository list never populated properly and all DAT updates would fail with "unable to find a valid repository". I can't push changes in the Repository list OR to proxy settings to these boxes via the ePO console. More testing revealed that boxes running VSEN7.0 are the only ones seeing this problem. I'm experiencing 100% failure with boxes running 7.0 with a "manual" install of the agent. BTW - the agent package has all the valid repositories.

What does work:
If you import the workstation or server into ePO and push the agent.
If you use the OLD agent first, then deploy the updated agent via ePO deployment task.
If you import the sitelist.xml file manually at the workstation.

I'm going to post the details soon. NAI is looking into it after a spent a few days proving that a problem exists.

 

[JimmyZ1]

Thanks for the heads up.... I've seen this problem around, but couldn't duplicate it. Let me know what NAI says

If I had a penny for every framework issue i'd have alot of pennies....

 

[bfralia]

Thanks for all the input.

I had trouble going back to ePO 3.0.1 after I rebuilt the server to remove the first service pack 2. It only occurred on Windows 2K Pro computers. They seemed to drop the GUID and I had to send out a batch file to uninstall the agent and reinstall to re-establish the GUID.