Have you checked whether the embedded credentials file works yet?
Creating the 2 files results in the same file size seeing as they both include credentials, only the one has blank credentials. The files are exactly the same size but the way to check if your 2 files are different is to look at the hash.
You might find that the embedded credentials does actually contain the credentials. Try it, you might get another error message complaining about the embedded credentials but that's a separate issue that crops up some times.
Let me know how you get on.
I did thought that the file with embedded credentials should be larger than the other one. But you showed me it is not.
Just checked the md5 codes:
- bfffb0c963044c9d7a4dcdfeebd78612 *FramePkg.exe
- 8364418ff4755330fffad7b066db6603 *FramePkgEmb.exe
So it looks like they are different....
But when running the EC file, i get the message:
After pressing OK, the setup does not continue
If you check under your epo repository how many mcafee agents appear there? If you have both embedded and not embedded agents then try to delete the non-embedded agent and create again a new framepkg with your credetials to see if it works this time
That's the other error I was talking about, I got it too, but never found a solution to why that happened and got around it another way.
Using GP and Scheduler I managed to deploy the agents without adding the creds to the package but through AD instead. It didn't seem to hamper the install in any way and the Agent installed with SYSTEM level privileges through the GP.
Might be a better (and safer) option than embedding credentials anyway. If anyone managed to open and somehow (not sure if possible) decrypt the creds inside the package it could compromise your network.