cancel
Showing results for 
Search instead for 
Did you mean: 

ePO Endpoint Deployment Kit 9.6.1 - Enterprise Edition

UPDATE:

Version 9.6.1 - 08/08/2016

Inhibited entry of comma in description field due to a ePO bug that splits it into 2 packages.

Fixed issue with overwriting of package if it already exists.

UPDATE:

Version 9.6.0.

Updated to .NET 4.5.

Removed third-party DotNetZip Library, replaced with native .NET 4.5 functions.

Removed third-party HTTPUploadHelper for MultipartFormData processing, replaced with native .NET 4.5 functions.

Changed background color of dialogs.

UPDATE:

Version 9.2.5.  Updated error handling for product detecion key parsing.

UPDATE:

Version 9.2.4.  This version set default values for the product detection key and product detection value.

I am very pleased to post the Community Edition of the ePO Endpoint Deployment Kit (EEDK).  This tool is designed to allow ePO  users to build and deploy their own custom software packages using ePO. This can included other software, hotfixes, scripts etc.  Inside the attached .zip files we have included a Product Guide along with  examples of building your own software packages.  If you have any question please use this community site for support.

UPDATE:

Version 9.4.  This version adds Windows 8 and Windows 2012 platform support.

UPDATE:

Version 9.5.2  This version adds Windows 10 platform support.

UPDATE:

Providing Enterprise Edition to the community. This will be the only version maintained going forward.

Labels (2)
Tags (1)
Attachments
Comments

Cool. Now I can take over for SCCM.

Now link your tool with PA so I can automatically deploy missing patches to systems that PA finds.

You should have your own blog called "Fun with Torry"

Below are main limitations I found by playing with the tool :

1) Uninstall option is not working (documentation says that option is availble but not implemented ) I was able to perform install and uninstall by changing batch file and playing with input parameters in product deployment task...

2) Deployed package is not detected as installed in ePO (nothing is added under HKLM\SOFTWARE\...\Network Associates\ePolicy Orchestrator\Application Plugins ... it was working in the past when we have to use command line tool to create Safeboot agent package) which is very pity as I would love to get this information in a compliance dashboard.

Anyway thanks a lot for this wonderful tool !

remi,

The uninstall command not working is a known issue and we hope to have that addressed in a future releases of the McAfee agent.  There are several workaround techniques to handle uninstallation.  A separate removal package, use of command line options in your deployment script thatallow you to pass the remove/uninstall command to your software are jsut some of the options.

To have the agent report back properties about an installed product you must also provide a plugin.dll file that the McAfee agent can call to retrieve and populate the product properties.  The reason the 5.x Safeboot package reportsback product properties is the Dev team created their own plugin.dll for that purpose and get deplyed and install during the install set instalaltion.

Given the fact we’ll not know what software or scripts you’re deploying, I decided to keep this tool simple and not the build plugin.dll for this release.

There are alternatives. You can use the ePO agent custom properties field to report back any details on your custom package.  McAfee System Information Reporter,McAfee Policy Auditor, McAfee Risk Advisor or McAfee Application Control all have the ability to report back on all installed software on a system.

Can you tell me what software you are trying to deploy and I see ifI can provide you some recommendations for reporting?

Thank you again for the feedback .

Hi Torry,

Thanks for your answer.

About the uninstall command, I understand the issue is coming from the ePO agent ? BTW, I was able to uninstall the software by modifying the batch file.

I have deployed a software which monitor desktops behavior (www.nexthink.com) and I would extend the use of your tool's capabilities to deploy almost every standard products we have and by extension products which our customers can have (as we are a VAR).

I don't know how complicated it is to develop requested .dll but, we could make effort if it is not so hard.

Regards

Hi Remi,

Can you share the changes at the batch file?

Regards

Daniel

Hello Torry,

I have read the MSA example deployment guide.and  it is not clear to me how did you create the bat file from the msi and if it necessary.

Regards,

Yossi Mor

Hi Yossim,

The bat file was necessary as an MSI file cannot successfully be called from the tool. As you will see in the example BAT file, it is necessary to call MSIEXEC and then specify the MSI to be launched along with the various install parameters.

-Stuart

Hi Daniel,

Please find the modified version of batched file proposed here. Also consider that I'm not a batch specialist !

To uninstall you just have to create a deployment task in ePO and pass "uninstall" (without quotes) as parameter and action must be "install".

Hope this help.

Regards

@echo off

:: Remi Clavel E-Secure
::
:: Modification was done to install or uninstall a msi depending of input parameter:
:: - if input parameter is "uninstall" then launch uninstall command
:: - if there is no input parameter or if it is anything else than "uninstall" launch install command
::

:: Get number of input parameters
set argC=0
for %%x in (%*) do Set /A argC+=1

:: Stuart Avery McAfee, Inc. 2011
:: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:: Confirm x86 Architecture and exit if not found
If %PROCESSOR_ARCHITECTURE% == x86 (
GOTO START
) ELSE (
Exit /B 1
)
:START
:: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:: Torry Campbell McAfee, Inc. 2011
:: ################################################
:: Set environment to current product folder
pushd "%~dp0"
:: Get software package source directory and set as variable SRCDIR
SET SRCDIR=
for /f "delims=" %%a in ('cd') do @set SRCDIR=%%a

if %argC%==0 GOTO INSTALL
if %1==uninstall GOTO UNINSTALL
:INSTALL
%comspec% /c %systemroot%\system32\msiexec.exe /i "%SRCDIR%\<REPLACE BY MSI FILENAME>" /quiet
GOTO END
:UNINSTALL
%comspec% /c %systemroot%\system32\MsiExec.exe /X{<REPLACE BY APPROPRIATE VALUE>} /quiet
:END

goto EOF
:: Exit and pass proper exit to agent
:: ################################################
:EOF
Exit /B 0

This is a great tool.  We have been using version 9.0 since September and have used it several times.  Great utility Torry.

Great tool - thanks !

BUT! !! I am trying to get a batch file working and it just fails and fails.

This is my code:

@echo off

:INSTALL
program.EXE"/12345

GOTO END

:END

Exit /B 0

Very simple. I have packaged it up wit the .exe file using eedk, but when trying to deploy to a machine it just fails

af77,

I think you have several issues to resolve so I'll try and work through them.  One item that is noted in the product documentation for the MBSA package is the batch file example.  In the batch file you'll find a line that has the following:

pushd "%~dp0"

This is critical because of a behavior with the McAfee Agent that it resets its current working directory to the "Current" directory like in this path off of a Windows 7 x64 system: "C:\ProgramData\McAfee\Common Framework\Current". 

By using the pushd command you are setting the current working directory to the location where the McAfee Agent has downloaded your script files.  Now it can find the script to execute.

The next thing I commonly do is create a temporary variable to hold that path information.  To do this is use the following commands.

SET SRCDIR=

for /f "delims=" %%a in ('cd') do @set SRCDIR=%%a

The set command clears any previous value and then I take the output from the 'cd' command and assign it to the SRCDIR variable. 

At this point you are ready to call your program.  If you've deployed a setup program as part of your package then you would cal it like this

%comspec% /c "%SRCDIR%\yourprogram.exe"

You'll notice I've enclosed it in quotes incase there are any spaces in the path.  This would happen on any Windows XP or 2003 systems.

If the program already exists on a system then do the same thing but change the path like this:

%comspec% /c %systemroot%\system32\msiexec.exe /i "%SRCDIR%\MBSASetup-x86-EN.msi" /quiet

I hope this clear up some of your questions. 

I always make sure the path is included.

Also in your example you are not calling the install subroutine so your program will never get called.  Also you have not provided a path to the program so the McAfee Agent will not be able to execute it. Here is an example of your program. You'll have to put the proper path where noted:

@echo off

:: Set path to current product folder

pushd "%~dp0"

:: Get software package source directory and set as variable SRCDIR

SET SRCDIR=

for /f "delims=" %%a in ('cd') do @set SRCDIR=%%a

%compsec% /c "<YOUR PATH HERE>\program.EXE" /12345

Exit /B 0

Sample from MBSA example.

:: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

:: Torry Campbell McAfee, Inc. 2011

:: ################################################

:: Set path to current product folder

pushd "%~dp0"

:: Get software package source directory and set as variable SRCDIR

SET SRCDIR=

for /f "delims=" %%a in ('cd') do @set SRCDIR=%%a

:: Execute msiexec.exe in a separate CMD process and install specified package from source dir with no user interaction

%comspec% /c %systemroot%\system32\msiexec.exe /i "%SRCDIR%\MBSASetup-x86-EN.msi" /quiet

goto EOF

:: Exit and pass proper exit to agent

:: ################################################

:EOF

Exit /B 0

Thanks for the reply.

Ok, so i have done as youve suggested, here is the code now:

@echo off

:: Set path to current product folder

pushd "%~dp0"

:: Get software package source directory and set as variable SRCDIR

SET SRCDIR=

for /f "delims=" %%a in ('cd') do @set SRCDIR=%%a

%compsec%  "%SRCDIR%\program.exe" /12345

Exit /B 0

When packaged, and i run it via epo, it seems to run but the exe never runs on the target

Af77,

A reminder that when the agent executes a script or program that it does not run interactively.  This means that if you are expecting the program to interact with the enduser it will not.  To confirm the program is running you'll have to check taskmgr for running process. 

Can you tell what the program does?  Is it intended to run silently or interactively?

Thanks Torry

the program is just a compiled batch file to delete some registry entries.

if i run the script from a command prompt it works fine, but via epo the .exe never runs at all

af77,

Can you post or send me you pacakge with the .eedk file?  Many of the batch file compilers launch a splash screen which requires user acknowledgemetn to run.   Email me directly.

I ran into a similiar issue with this solution when I was running a batch file that did a simple uninstall.  I found out the issue was that I didn't add anything under (Product Detection Key) and (Product Detection Key Value).  I added entried into those fields and it worked... I just made it up.   

This is a neat tool. I can think of a bunch of uses already. Is there any information on delimiters and escape characters that can be parsed in the command line ?  I saw some examples where the command line parameters were surrounded by double quotes (e.g. CommandName "parameter1 parameter2 parameterN"). I have a program I'd like to package which itself requires double quotes to avoid embedded spaces being treated as a delimiter. For example, to invoke my program from a console I'd type CommandName /DN "CN=Some AD Container,DC=mydomain,DC=com" and I need double quotes to ensure the string with embedded spaces following /DN is treated as a single parameter. Can I use escape characters to ensure the embedded double quotes are passed to my program for interpretation rather than being intepreted by the agent parser

Do you mean on the command line of EEDK?

Hmm, I could see a problem with  a command line this:

eedk.exe -Install:"CommandName /DN "CN=Some AD Container,DC=mydomain,DC=com""

EEDK uses the outer double quotes to parse it's own command line. It should work in the GUI version of EEDK, but you would have to do one of 2 things for the inner command.

Escape the inner quotes (\"):

eedk.exe -Install:"CommandName /DN \"CN=Some AD Container,DC=mydomain,DC=com\""

or use Single Quotes (') if the application supports it:

eedk.exe -Install:"CommandName /DN 'CN=Some AD Container,DC=mydomain,DC=com'"

Looking through the code of EEDK, it appears that it should work, but I can't tell once a package is built and deployed with ePO if it will work at the endpoint.

Let me know if either of those methods works for you.

Having it run with the quoted arguments should work.  In batch using the "^" character escapes special characters.  In some instances when I've needed to run multiple commands i've had to use () to enclose a command set. such as (command.exe) && command2.

I would suggest you create the pacakge without embedding the arguments then use the product deployment task command line options to pass and test your syntax.  As far as I know the agent command parser doesn't strip of the quotes.  With that said i've run across some odd behavior every once and a while, so as alswys test.

Thanks for the tips. My package includes a batch file to parse arguments from the deployment task command line. From the replies above it seems like the carat (^) escape character is my best shot. I'll experiment with some options. Thanks again for the replies

You can send me your batch file and I can take a look if you need.

Actually, it is your batch file from ACUCONFG7150 package for use with Deep Command (see picture below)

ACUCONFIG.EXE needs to end up being invoked with at least one parameter that may contain spaces and therefore needs to be surrounded with double quotes to ensure spaces are not treated as delimiters by ACUCONFIG.EXE (e.g.  /DN "CN=Some AD Container,DC=mydomain,DC=com")

Embedding double quotes and surrounding the entire command line with single quotes in the client deployment task command line, or preceding the double quotes with backslash results in an error when the package is invoked (I do not think ACUCONFIG.EXE is actually invoked at all, so assume that parsing the command line passed to the batch file results in some error, but this is just my intuition)

So my question is what do I need to type on the command line of the client deployment task which will result in the batch file passing those double quotes through to ACUCONFIG.EXE so that ACUCONFIG.EXE does not treat embedded spaces as delimiters

Capture.JPG

Can you send me the exact command line you are passing?

The command I entered into the McAfee Agent: Product Deployment screen was...

"/LowSecurity /Verbose /KeepLogFile /Output File C:\Windows\Tempt\ACUConfig.Log ConfigViaRCSOnly EPO.vprolab.com "McAfee Profile" /AbortOnFailure"

The parameter with embedded spaces is McAfee Profile, so I have tried surrounding it with double quotes, double quotes preceded with \ and ^ and using single quotes at the outside. When executed, the log display from the McAfee agent says "Error occured while installing ACUCONFG7150" so I assume the batch file does not like the command line being passed to it and generates an error without ever calling my executable

In the example above, I can change McAfee Profile to McAfeeProfile (without spaces) to avoid using spaces, but there are some situations where an AD DN is required, and the AD structure is outside my control and I may need to pass DN containing embedded spaces in which I case I do need to use double quotes when the batch file invokes ACUCONFIG.EXE

Not sure if this is possible or not

sdavies,

A couple of questions/comments:

  • Have you taken that exact command string, inclusive of all the quotes, and passed it to acuconfig.exe locally on the system? if so, did it work?
  • Did the acuconfig.log ever get generated? If so ,what were the error messages?
  • Try  the string without the beginning and ending quotes.  They should not be needed as I take all arguments (using the %*) in the batch file and pass them to acuconfig.exe.  

Awesome Tool! Kudos!

Thanks for this tool.  I set an EXE to run from ePO.  It runs great on the client. However in ePO the status says failed.  How do I find out  why ePO thinks it failed? 

Did you run this as a "Run Now Client Task" or as a scheduled product deployment task?  Where are you seeing the error message?  What did the executalbe do? 

Yes, I ran it as a Run Client Task Now.  If I left the screen up it showed the status as red and showed failed.  I also see that in the server task log:

2/9/12 3:54:47 PM  Started: Sent Run now task "CustomApp" to "XP1"

2/9/12 3:54:53 PM  Run now task CustomApp received.

2/9/12 3:56:02 PM  Run now task CustomApp started.

2/9/12 3:56:02 PM  Run now task CustomApp failed.

                                   Details: CUST_APP1000 installation failed.

what did the agent log show? 

I didn't see any errors (I pulled the relevant information out of the log):

Thursday, February 09, 2012 3:54:59 PM

Info

Scheduler

Added a new task Custom App to Scheduler's task list

Thursday, February 09, 2012 3:55:14 PM

Info

Scheduler

Scheduler: Invoking task [Custom App]...

Thursday, February 09, 2012 3:55:20 PM

Updater

Info

Updater

Verifying CSTM_APP1000-det.mcs.

Thursday, February 09, 2012 3:55:23 PM

Info

Updater

Downloading CSTM_APP1000-det.mcs.

Thursday, February 09, 2012 3:55:24 PM

Info

Updater

Verifying CSTM_APP1000-det.mcs.

Thursday, February 09, 2012 3:55:24 PM

Info

Updater

Downloading PkgCatalog.z.

Thursday, February 09, 2012 3:55:25 PM

Info

Updater

Verifying PkgCatalog.z.

Thursday, February 09, 2012 3:55:25 PM

Info

Updater

Extracting PkgCatalog.z.

Thursday, February 09, 2012 3:55:25 PM

Info

Updater

Loading update configuration from: PkgCatalog.xml

Thursday, February 09, 2012 3:55:26 PM

Info

Updater

Installing CSTM_APP1000.

Thursday, February 09, 2012 3:55:26 PM

Info

Updater

Downloading Customapp.exe.

Thursday, February 09, 2012 3:55:28 PM

Info

Updater

Verifying Customapp.exe.

Thursday, February 09, 2012 3:55:39 PM

Info

Updater

Update succeeded to version 1.0.0.0.

Thursday, February 09, 2012 3:55:39 PM

Info

Updater

Update Finished

Thursday, February 09, 2012 3:55:42 PM

Info

Updater

Update Finished

Thursday, February 09, 2012 3:55:59 PM

Info

Scheduler

The task Custom App is successful

Thursday, February 09, 2012 3:56:00 PM

Info

Scheduler

Scheduler: Task [Custom App] is finished

Thursday, February 09, 2012 3:56:00 PM

Info

Scheduler

The task Custom App is deleted (ID={314F91A5-3D0D-4A2E-86AF-F42025B193F4})

I suspect that it has to do with the lack of data channel response on the completed task.  Let me see what I can find out.

Did your .exe terminate network commmunicaiton or shutdown the system?

No.  It just checks some files and does some file copying.  I'll test with a different EXE and see what the results are.

Not sure if a New thread needs to be started or not but...

Deployed stinger vs502 on a NON-infected node, packaged with EDK9.5, with the following commands via ePO --SILENT --ADL.  I noticed that it wouldn't run.  After investigating I figured out that prior to running the stinger checks in with the McAfee site to confirm that it's running the latest stinger version.  If it's not the latest version then a pop-up requesting if you would like to download the latest version.

So, I downloaded vs509, packaged with EDK9.5, and deployed with the same commands via ePO --SILENT --ADL and it has been running for the past 2 hrs.  Confirmed by launching taskmgr.

I have ran the stinger before but not for 2 hrs...what could I be missing (deployed to non-infected node to bench performance) and how can I tell with no logs??

I'm receiving an "ePOSign Error" when attempting to build a package for a VBScript. I believe i followed the guide correctly. I have pasted the log below

[2/15/2012 9:53 AM] Populating eedkSettings.

[2/15/2012 9:53 AM] eedkSettings Validated

[2/15/2012 9:53 AM] Building package.

[2/15/2012 9:53 AM] Creating Build Folder: "C:\Users\me\Desktop\EEDK9.2.5 Community Edition\Build\Build-EEPCSERV1001-1.0.0.1"

[2/15/2012 9:53 AM] Copying Source: "C:\Users\me\Desktop\EEDK9.2.5 Community Edition\Source\EEPCSERV\Restart_EEPC_and_Framework_Service.vbs"to Build: "C:\Users\me\Desktop\EEDK 9.2.5 CommunityEdition\Build\Build-EEPCSERV1001-1.0.0.1

[2/15/2012 9:53 AM] Creating PkgCatalog: "C:\Users\me\Desktop\EEDK9.2.5 Community Edition\Build\Build-EEPCSERV1001-1.0.0.1\PkgCatalog.xml"

[2/15/2012 9:53 AM] Creating MCS file: "C:\Users\me\Desktop\EEDK9.2.5 CommunityEdition\Build\Build-EEPCSERV1001-1.0.0.1\EEPCSERV1001-det.mcs"

[2/15/2012 9:53 AM] Running: C:\Users\me\Desktop\EEDK 9.2.5Community Edition\ePOSign.exe "C:\Users\me\Desktop\EEDK 9.2.5 CommunityEdition\Build\Build-EEPCSERV1001-1.0.0.1\PkgCatalog.xml" .mcs /a

[2/15/2012 9:53 AM] ePOSign Complete: Exit Code=-1073741515

[2/15/2012 9:53 AM] ePOSign Error:

Any help would be appreciated. Thanks

I have an update to this. I ran  ePOSign.exe manually and recieved an error. Please see below

ePOSign Error.jpg

This is really cool tool and we have been using it for a while now.  Any examples for Mac or Linux?

I too would like some Mac examples. I'm actually trying to get simiar functionality as "Collect Serial Number from Machines" but for Mac. I have the command:

ioreg -l | awk '/IOPlatformSerialNumber/ { split($0, line, "\""); printf("%s\n", line[4]); }'

but how do I implement this using EEDK?

Thanks!

Hey Torry,

   I am attempting to use this tool to push a package to a Win XP Embedded system, and it is not allowing it as the build manifest doesn't contain WXPE as a supported platform.  Anyway around this in a hurry?

Thanks,

Dave

There's an option to copy an entire folder. In the guide it says the destination folder is: %AllUsersProfile%\Application Data\McAfee\Common Framework\Current\<Product Code>\Install\0000\<File Name>. I have a script that needs to copy some included files from there.

1) Where do I determine <Product Code> ? (I'm looking for the source for my script. It rund from \McAfee\Common Framework)

2) On my win7 mahcine %AllUsersProfile%\Application Data\McAfee\Common Framework\Current has permissions locked down. Will the agent run at a high enough level to acces that folder?

Thanks

Have been given this tool by Platinum support so that I can issue a regfix to machines that tells them to read ASCI from the registry. Well, I can't get it working so ring them again, get another chap and he has nevere heard of it ! He has made me something that works in SuperDat manager, but that is a bit messy. SO, I want to fix this. I have the package all done and checked in. When I run a task that does it, all says OK locally, but it does not work and EPO says it failed. I can't find any logs that help. All I am doing is running a file called readreg1.bat that does

regedit /s bReadEngReg.reg

That reg key does this

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\DesktopProtection]
"bReadEngReg"=dword:00000001

I am wondering if it can'ät copy the files locally as I don't see them in the 'current' folder. But why it can't copy, I have no Idea. Thoughts ?

I'm having some issues trying to deploy a simple .msi package.

The command to execute is:

MSIEXEC /I AGENTSETUP.MSI /qn

When I try to run the task, I see:

Error occurred while installing Package100000

Do I need to do anything specific with msi packages?

Also, I tried to make a batch file, which initiated the above command; that also didn't work.

I have written a simple bat file that will copy over the contents of the quarantine folder to a network share.  When I run the bat file from my local system it works great and moves the quarantine files over just fine, so I went ahead and used the ePO Endpoint Deployment Kit to build the package and then checked it into epo, but when I run the task on a managed system it never collects the content of the quarantine folder.  Thanks in advanced for any help you can provide.

@echo off

                :: Map Network Drive

                                net use q: \\x.x.x.x\malware$ password /user:username > NUL 2>&1

                :: Create Folder

                                md "q:\Quarantine\%computername%" > NUL 2>&1

                :: Copy Files

                                echo No | copy/-Y C:\Quarantine q:\Quarantine\%computername% > NUL 2>&1

                :: Remove Network Drive

                                net use q: /delete /yes > NUL 2>&1

                :: Exit And Pass Proper Exit To Agent

                                Exit /B 0

Like me, I think you need to read the previous posts and the documentation. You cannot just use a simple script due to the context that the command line runs in. My simple one line turned into the code below. I then used iexpress to turn it into an exe (negating the need to allow regedit.exe to break Access Protection) and packaged. All good.

pushd "%~dp0"

SET SRCDIR=

for /f "delims=" %%a in ('cd') do set SRCDIR=%%a

%comspec% /c %systemroot%\regedit.exe /s "%SRCDIR%\bReadEngReg.reg"

goto EOF

:EOF

Exit /B 0

Additional info

The regkey tells the local system to read ASCI data from the registry rather from the VSE data. You may need this if you find, like us, that certain systems do not report the dat level back correctly

[HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\DesktopProtection]

"bReadEngReg"=dword:00000001

Hey Torry,

we want use this tool to push a little application to clients. Pushing works fine but we have a problem with client task. When we push software by client task we get the following error:

Eigene Organisation > domain > xxx > Computers > xxx

Fehlgeschlagen

                            
                            
                            
                            
                

May the package was correctly installed on client.

I have been using this tool for while and it has helped out a bunch in making utilities of my own.  I do have one question though.  We have been trying to edit out current installations of virusscan 8.8 default scan tasks to up the artemis detection level and use a lower cpu priority as well as our own exclusions.  The scan tasks are just registry keys on the host so I made a package that would deploy the updated reg files.  This works fine, no problems, unless access protection rules to prevent modification of mcafee files and registry keys.  I thought that the epo agent deployed items with system privledges and thus these block would not occur.  Anyone got any ideas how to make an epo deployable package that will not be blocked by access protection rules?  I can exlcude, regedit32.exe, reg.exe but that is opening up a big hole until all hosts have ran the tool.

I got around the same problem by writing some VB and then converting to an EXE. That gave me an EXE that worked - you DO need to edit Access Protection rules to allow that EXE to run though, but at least you can call it a custom name. Sadly, I could not get it to work as a package within EPO though after converting with EEDK. I have a case open with McAfee for several weeks for that.

Another option is to use the Superdat manager for this work, but that has certain limitations - such as you can only use one package at a time.

I did this too,  I basically made a self extracting exe but the vbscript is blocked not by the exe name but by the wmi process.  I get

Blocked by Access Protection rule  NT AUTHORITY\SYSTEM C:\Windows\sysWOW64\wbem\wmiprvse.exe \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\McAfee\DesktopProtection\Tasks\{F1FEA6DD-4B4D-4A1D-8E31-1D1E2C39EA9F}\dwHeuristicNetCheckSensitivity Common Standard Protection:Prevent modification of McAfee files and settings Action blocked : Create

Ok I figured out how to get around this.  i created the script with the Autoit tool and that solved the issue.  This tool will make a true executable rather ran a self extracting zip/exe.  When the packages are made with autoit you can exclude the name of the app in access protection rules and everything is fine.

any plans on making this tool work with Windows 8 yet?  I noticed the packages I made for other os get an error when running on Windows 8.  Says not supported.  not sure if this is an agent issue, but my guess is you have to add the windows 8 to the options of OS in the tool.

Version history
Revision #:
1 of 1
Last update:
‎01-11-2012 08:24 AM
Updated by: