This content has been marked as final. Show 27 replies
Same here. Will be contacting Mcafee tomorrow
Guess I'm glad I haven't added deployed this patch yet.
Don't forget writting (here) their answer grin Thanks happy
So am I :P
Have you tried using a VERY simple name and password for the crededntials ? (e.g Freddyboy/Freddyboy) - ePO used to be a bit fussy about certain characters etc. in usernames and passwords or paths etc.
Username/ Password does not contain any special characters, again it worked with patch 1.
Thought the password fussiness was with the DB.
It works fine as long as you push it from the server.
Recall there being a similar issue with a previous version.
Agent 4 patch 2 doesnt support embedded user credentials as part of the framepkg.exe now.
7. Issue: The McAfee Agent no longer provided an embedded credential installation package option.
Release Notes for McAfee Agent 4.0.0 Patch 2 (Windows)
Resolution: An embedded credential installation package is now available through McAfee Tier III
Support. For information on obtaining this package, see KB article KB59954.
As far as I can make out, currently (with patch 1) you have the opition to either put credentials in, or have a package with no credentials. You have the choice to make.
That seems fine to me, so I don't understand why it would be a good idea to take this option away with patch 2?
What am I missing?
Also, I was thinking that this would now mean that the user of the PC must have administrator rights to be able to install the agent, is that correct?
We have had loads of problems since deploying patch 2 - 'unable to find valid repository', repositories in the list being ignored, updates only working from the ePO server repository, errors with the catalog.z file......