Upgrading to VSE 8.5 via ePO 3.6.1? 1

[zygar]

Howdy all. I've been researching for tutorials on a good way to upgrade our current VSE 8.0 to VSE 8.5. I'm using ePO 3.6.1.

I've read McAfee's documentation on using Installation Designer to ensure the current 8.0 policies are kept. I've created a "custom" 8.5. package based on the policies and successfully uploaded it to the ePO server.

Is there a way I can roll out 8.5 via ePO without manually visiting each workstation with the FramePkg application?

This is for a private school and we're starting to get an influx of Vista machines in which don't work very well with 8.0.

Thx much, in advance, for any insight!

Regards,
Kory

 

[LawnBoy]

EPO 3.6.1 comes with workstation agent 3.55. You must push out agent 3.6.0 to install or manage VSE 8.5.

Whether your policies will follow I don't know.

 

[zygar]

Yep, already found that out. The agents have been updated to 3.6 (can't remember the exact extension number as I'm not on the network right now). I successfully rolled out 8.5 to two workstations but now the DATs aren't updating. I've contacted McAfee about it.

Ran the policy application tool that came with 8.5 after running it through Installation Designer and confirmed that the policies followed. Once I figure out why the DATs aren't updating I'll be good to go.

Regards,
Kory

 

[bugguy51]

Known issue with ePO 3.6.1--I'm currently waiting for a resolution from 3rd Level Support. After updating to 3.6.1, any 3.6.0.453 agents installed from that point forward will report in to the management server, but fail to merge any new policies or update existing policies, failing with a '1203--Internal error, object not valid' error as found in the agent log. Hoping I have a resolution to tell you about SOON!--The Bug Guy

 

[VictorySabre]

bugguy51,

Not sure if this is related to the problem you are having, but check out McAfee's Knowledge Base Article 5803947. I found some of my PCs on CMA 3.6.0.453 refused to work after I upgraded them from 3.5.5.

You can try the workaround of deleting the 3 registry values on a test PC to see if it fixes your problem or not.

At least on my PCs, this is what fixed it.

 

[bugguy51]

Thanks for the response, but that (and several other attempted fixes) didn't get it. McAfee 3rd Level has my database at the moment--am guessing it's either a private security keys issue or invalid application objects enumerated in the management agent .XML files. Interestingly, I've only got about 60 machines that won't update policies--all those that have installed an agent since the app was updated. The rest of my 4000+ platforms just keep chugging along--The Bug Guy

 

[bugguy51]

Issue was several database rows in several tables referring to an old (2.X!) version of the management agent. I FTP'ed McAfee the DB, 2nd Level tech walked me through a SQL script to remove the offending entries. All seems well now. If you're seeing 1203 errors at the client log, you've probably got a similar problem and need to open a service ticket. An additional issue--if you're deploying the 3.6.0.453 agent from the ePO Console (Send Agent Install), DO NOT check the 'Force install over existing version.' Known bug in the 3.6.0 agent, if you do that, you'll have to rip the agent out and reinstall it.--The Bug Guy