- #MC AFEE AGENT INSTALL#
- #MC AFEE AGENT ARCHIVE#
- #MC AFEE AGENT UPGRADE#
- #MC AFEE AGENT ZIP#
- #MC AFEE AGENT WINDOWS#
This is the simplest option, especially if you have a lot of client to deploy to.ġ. The McAfees GUID key needs to be deleted so the agent and can generate a new GUID and successfully connect to the EPO console. Set Firewall to Allow McAfee Agent deployment via Group Policy This is used when we deploy PCs that already have the McAfee Agent installed on them. Solutionīasically you need to to do two things with the firewall A quick Google turned up a myriad of suggestions for ports and services, and most of them were for older versions of ePO or were simply incorrect. Please visit this result for more detailed.
#MC AFEE AGENT WINDOWS#
As the prospective client is going to use Server 2012 and Windows 8, that’s what I tested it with.ĭespite my best efforts the the McAfee agent (8.6) refused to deploy to the clients as long as I had the windows firewall on. This entry has information about the startup entry named McAfee Network Agent that points to the mcnasvc.exe file. Sudo /usr/sbin/installer -pkg cma.It’s been a while, since I deployed ePO, and as I’ve got a big McAfee roll-out coming up I thought I’d better run it up on the test bench and see how much it’s changed since version 4. Sudo /usr/sbin/pkgutil -forget > /dev/null 2>&1 Pltvrsn=`/usr/bin/sw_vers | grep ProductVersion | cut -d: -f2` #The actual operations for copying the reqseckey and other files should already be there in the installerĮcho "IsLegacyEPO:N" > /etc/nfigĮcho "ConfigDirPath:/Volumes/MFECMA" > /etc/nfigĮcho "StartService:Y" > /etc/nfig
#MC AFEE AGENT UPGRADE#
#Now do the actual install/ upgrade stuff Hdiutil attach -nobrowse "$directory/MFEcma.dmg" If || || || || thenĮcho "Could not find key data files. If thenĮcho "Failed to create keydata directory.exiting"Ĭp -f "$directory"/sitelist.xml "$keydata_dir"/SiteList.xmlĬp -f "$directory"/srpubkey.bin "$keydata_dir"Ĭp -f "$directory"/reqseckey.bin "$keydata_dir"Ĭp -f "$directory"/sr2048pubkey.bin "$keydata_dir"Ĭp -f "$directory"/req2048seckey.bin "$keydata_dir"Ĭp -f "$directory"/agentfipsmode "$keydata_dir"/agentfipsmodeĬp -f "$directory"/RepoKeys.ini "$keydata_dir"/RepoKeys.ini Unzip -j -o $"$temp_directory"/package.zip -d "$directory" # /bin/sh "$temp_directory"/unz -j -o $"$temp_directory"/package.zip -d "$directory" Remainder=`expr $unzip_exe_size % $block_size`ĭd if="$temp_directory"/payload of="$temp_directory"/unz bs=$block_size count=$nblocksĭd if="$temp_directory"/payload of="$temp_directory"/package.zip bs=$block_size skip=$nblocks Nblocks=`expr $unzip_exe_size / $block_size` Tail +$SKIP "$command" > "$temp_directory"/payload
#MC AFEE AGENT ARCHIVE#
# take the archive portion of this file and pipe it to unzip
Required_space=`expr $required_space \* 2`Įcho space required to copy archive is $required_space bytesĪvailable_space=`df -k $temp_directory | tail -n -1 | awk '' "$0"` #this sfx itself.So havin enough space in $temp_dir to hold the sfx is good enough
#MC AFEE AGENT ZIP#
#Since the zip is appended to this file itself, it would never be larger that #So, all I care about is to have enough space for the zip itself.
#unzip will also complain is there isnt enough space for the extracted file #installer has checks for disk space, and so I wont bother about it. #For Agent installation through bootstrap.Įcho "Agent installation through bootstrap."Įcho "Cloud config path doesn't exist($cloud)."Įcho Output destination specified is a file which laready exists. #and then unzip it to the final destination #First we need to extract everything to a temp location, #Okay, now that everything has been checked, its time to get going
#MC AFEE AGENT INSTALL#
#Cannot have "neither install, nor upgrade"Įcho "Neither install nor upgrade has been specified in the options"Įcho /Volumes/MFECMA already exists.The agent disk image cannot be mountedĮcho Please move or rename /Volumes/MFECMA and then rerun this setup If & thenĮcho You cannot specify install and upgrade at the same time #Cannot have install and upgrade together If you dont stop this, all the services will reactive when it checks again. Keydata_dir=/Library/McAfee/cma/scratch/keydata One of those daemons is the McAfee agent, which is the daemon the listens to the enterprise server (if you have an enterprise deployment) and will restart everything according to the servers instructions. NATIVE_INSTALLER_FILE=MFEcma.dmg #NATIVE_INSTALL_PACKAGE_NAME_HEREĮcho "-b :Upgrade Agent only, no server info will be updated"Įcho "This package needs root authentication to install."Įcho "Detected presence of previous agent in /Library/NETAepoagt. # -c cloud config path (option for internal usage in bootstrap)