Does anyone know if it is possible to add latest DATs/content updates etc., to packages created with ENS Package Designer? I'm sure you could do this with the VSE Installation Designer, but I can see it with the ENS version. Maybe there's some fancy command line or something...
Solved! Go to Solution.
Thanks for replying Yaz! I'd already seen that article, but it only provides basic information. Having gone through the ENSPD wizard, I'm not sure what I want to do can be done with this iteration of the product
I downloaded the source package from EPO McAfee_Endpoint_Security_10_5_3_3152_11_patch_stand_alone_client_install" and unzip to a folder. Then I used the zip file point to the ENS Package Designer and I keep getting the error "the installatino file for "Mcafee Endpoint Security Installer must be verion or later is invalid"
I am getting similar to the above when trying to use Package Creator (installation file is invalid). What package are we meant to be using as the source? I have noted recently that there are a number of issues trying to find packages on the mcafee download sites (public and support site), and also that the standard of documentation appears to have slipped - I am spending a great amount of time trying to figure out exactly what I am meant to be downloading and using... I am starting to wonder if any of this documentation has been through any form of QA whatsoever...
I tried with the following (non patch version) and it appears to be working:
The KB article is fairly high level. Example "On the Modify Package screen, click Edit Settings and change the settings if needed, and then click Next." - in reality, this opens the local ENS client console. After I have made the relevant adjustments, I have then just closed the console - there is no confirmation that the changes have been noted. Also although I am wanting specific settings in the package, I did not really want to change settings on the host itself - this seems to not be an option.
The package does seem to be created fine, although I have not tested this end to end yet. I was hoping to add it into a EUA custom package, however none of the packages created with EUA package creator appear to be checking into ePO...