Novell Home

Pushing out McAfee Virus Scan 8.0

Novell Cool Solutions: Trench

Digg This - Slashdot This

Updated: 11 May 2005
 

Q: Has anyone been able to push McAfee Virus Scan 8.0 out using ZENworks? I have Virus Scan 7.1 and I am having a hard time pushing 8.0 out. I am also using the Installer 8.0.

A: One expert in the forums reports that he successfully did more than 1000 workstations by making two objects as follows.

net.exe start "network associates McShield"
which was dependent on the other
setup /s

So first setup, and then start Mcafee again without rebooting.

Anyone else got other suggestions? Let us know.

Suggestions

jharting

The installation of McAfee Virus scan Enterprise consists of one batchfile which first uninstalls our previous version (4.5.1), then restart the Installer Service and then Installs McAfee Virusscan using a transformfile which forces the systray icon to appear with limited options.

To get a hold of the proper files (the .msi package) I performed the installation clicking <Next> until the wizard was ready and <Finish> was the last option. Then I searched %winsysdir%\Cache and %Temp%.

In %TEMP% I found a directory called "McAfee VirusScan Enterprise 80" containing the installation files (including the desired msi).

After that I tried to install directly from the msi (msiexec /i package.msi /q) which worked.

What I needed now was a snappshot of some desired changes like the update time, OnDemand settings, etc., and to make sure the update task is launched after install. The snappshot caused no big problems, and to run the update task I just needed to run mcupdate.exe.

With Adminstudio ZENworks I made a transform file (for the systray-icon to appear with minimal options).

After that I copied the files to a folder the WorkstationObjects have rights to and made a simple (AOT) object.

Pre-distribution script launches (with #) a command file containing:
        
REM Uninstall of McAfee Virusscan 4.5.1 
        msiexec /x {87AEFD84-BC0D-11D4-B885-00508B022A51} /q 

        net stop "windows installer" 
        net start "windows installer" 

        msiexec /i \\server\volume\Install\McAfee\VSE800\ClInstall\vse800.msi TRANSFORMS=\\server\volume\Install\McAfee\VSE800\ClInstall\vse800.mst /q 
        exit 

The distribution consists of some registry settings and C:\Documents and Settings\All Users\Network Associates\Common Framework\Sitelist.xml which configures the auto update repository and order.

Post-distribution script:

#C:\Program Files\Network Associates\VirusScan\mcupdate.exe 

PS: The Product key of 4.5.1 I found by editing the .msi-file with packaging software.

In Short:

  1. Perform the setup.exe until <Install>, copy the "McAfee VirusScan Enterprise 80" folder to a location you workstations/users have access to.
  2. Make (if desired) a .mst file using Adminstudio
  3. OR - Make a snappshot of desired settings or options and configure auto update if you plan to auto-download the updates and place them centrally.
  4. Make an AOT Application Object with this snappshot and use the distribution scripts as above.
  5. TEST IT ! ! ! ! ! ! !

Mark Lewis

I downloaded the McAfee 8.0 Installation designer which creates an MSI. When you use the designer you can take all your custom settings from a PC that you have already installed V8.0 too.

Then use ZENworks to deliver the MSI app to your remaining PC's.

Roy Erez

If you intend to use ePolicy Orchestrator (McAfee's enterprise management tool) take the following steps:

1. Install the agent prior to the anti-virus by running FramePkg /forceinstall /install=Agent
If running on XP with SP2 the firewall has to be configured to allow ePO connection:
netsh firewall set allowedprogram program ="%ProgramFiles%\Network
Associates\Common Framework\FrameworkService.exe" name = "ePO Agent"
mode = ENABLE scope = CUSTOM addresses = [ePO Server IP]/32

2. Install VirusScan using a pre-configured quiet install package created with installation designer.

3. Run an rchestrator policy refresh:
%ProgramFiles%\Network Associates\Common Framework\cmdagent /e /c /p

This installation order can be configured through ZENworks dependencies as follows:
Agent refresh depends on McAfee installation that depends on agent installation.

Phil Gates

I tried a few ways of getting this out and this was far and away the simplest.

If you download the McAfee 8.0 Installation designer, and don't create as MSI, but let it create an Optimised Installation Package, then effectively what you get is a fully wrapped-up executable.

The benefit of doing it this is that to install McAfee 8, you need to uninstall all previous versions. The Optimised Installation Package will do this automatically for you. You can do this using an MSI, but it will require a lot more tweaking (see above!).

From this package, simply point a ZENworks application object at the executable, et voila.

One thing I would say though is to check all the settings very, very carefully as there are loads of firewall settings in there including setting to stop remote transfer, execute, and control, which could mess with ZENworks.

Dwayne Watkins

At my location, we took a slightly different approach. We have a copy of Install shield Admin Studio. Once you make the changes to the msi and create the mst, you can have C1 pull the MSI, and reference the transform. We've been running it with WINXP pro for about 2 months. Still waiting for any major issues to show up.

Update: What I accidentally left out about McAfee 8.0 is that in Windows XP with an automated build, after it is installed, the virus scan icon that normally sits in the taskbar doesn't show. In order to make it show again, you can reinstall on top of it (which takes about 1 min.), OR you can change the user interface options under tools.
-dw

Matt Kehler

Here is a solution, rather than hearing about 'how to install Mcafee' every couple weeks in this forum....I have a better solution. Use a better product such as TrendMicro Officescan. Put its main .exe in the users login script, and that's IT. If it's not there, it will install it. If it is there, it will update. If another product is installed such as Mcafee, it will uninstall and install itself.

Rather than spend countless hours on a less then stellar product trying to figure out how to get it installed...save yourself time, money and frustration by doing your homework, and buying a REAL product such as TrendMicro OfficeScan.

Honestly, reading about Mcafee install issues every other week makes me wonder if people are just plain ignorant, or if everyone is a glutton for punishment.

Rant over.

Matt Merrell

The easiest solution...

Download McAfee's Installation Designer for 8.0i Enterprise VirusScan. Custom config 8.0i the way you want it.

Once the Installation has generated the custom setup.exe file, put it in a common location on your network. Go into ConsoleOne, and create a NAL object. Select the "A Simple Application" option, and point it to the network location you copied the custom install setup.exe file.

NOW here is the important step...

Set a Distribution rule to the following:

Registry data(HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Application Plugins\VIRUSCAN8000:) not exist

Then finally, set the Application Object to FORCE RUN and associate with all your OUs / Os whatever.

Now, any time anyone logs on, NAL looks for the registry key, and if it doesn't find it, that computer gets 8.0i installed on the fly.

I hope this is a better solution.

Rick Darter

I don't know about McAfee 8.0 but we recently "migrated" from McAfee 4.5x to Symantec Enterprise and here is what we did.

We uninstalled the old version of McAfee with a ZENworks app (ZfD 4) that was running as a secure system user with the following Run Options:

\\SRVRNAME\VOLUME\Path to Original McAfee Install CD\Setup.exe
 
 REMOVE=ALL /q /i

NOTE: Leading space on the parameters line is VERY important!

We just copied the McAfee Install to a volume on the server that the workstations had R&F rights to. Then used McAfee command line options to uninstall (REMOVE) the product. This ran VERY fast and was over 98% effective.

We then used ZEN Application Dependencies (Daisy Chaining) on the Symantec install. Which of course was another ZEN app that used the Symantec MSI install structure.

I know this isn't an exact fit but maybe it will be of some use.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell