Using Microsoft BDD/MDT (LTI) to deploy Mcafee Agent (CMA)?
Is anyone using Microsoft BDD/MDT (LTI) to deploy CMA?
I have created an application in BDD for installing CMA (FramePkg.exe). The problem is that when agent installation package (FramePkg.exe) runs as part of LTI it can't install and stops the whole process. No matter how I run it, it stops and FrmInst_xxx.log shows only two lines:
20080905153041 I #3320 Stub Pkg
20080905153041 I #3320 Stub Pkg START [FramePkg.exe /install=agent /silent]
20080905153041 I #3320 Common Pkg CreateDirectory (C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\unz238.tmp)
When installing manually, it installs no problem.
Has anyone encountered this problem.
I have created an application in BDD for installing CMA (FramePkg.exe). The problem is that when agent installation package (FramePkg.exe) runs as part of LTI it can't install and stops the whole process. No matter how I run it, it stops and FrmInst_xxx.log shows only two lines:
20080905153041 I #3320 Stub Pkg
20080905153041 I #3320 Stub Pkg START [FramePkg.exe /install=agent /silent]
20080905153041 I #3320 Common Pkg CreateDirectory (C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\unz238.tmp)
When installing manually, it installs no problem.
Has anyone encountered this problem.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
kiptek
16 years ago
Try & specify an install directory...
"FramePkg.exe" /INSTALL=AGENT /SILENT /INSTDIR="%PROGRAMFILES%\MyCMADir\"
"FramePkg.exe" /INSTALL=AGENT /SILENT /INSTDIR="%PROGRAMFILES%\MyCMADir\"
Posted by:
davidpyu
16 years ago
No luck - same thing.
When installed manually the install log file looks something like this:
20080506173917 I #3624 Stub Pkg START [FramePkg.exe" /install=agent /silent]
20080506173917 I #3624 Common Pkg CreateDirectory (C:\WINDOWS\TEMP\unz2BE.tmp)
20080506173923 I #3624 Stub Pkg System=0
20080506173923 I #3624 Common Pkg CreateProcess (C:\WINDOWS\TEMP\unz2BE.tmp\FrmInst.exe, ...
So I wonder whether maybe the installer is having a problem determining the context or starting the frminst.exe process when running under BDD/LTI.
When installed manually the install log file looks something like this:
20080506173917 I #3624 Stub Pkg START [FramePkg.exe" /install=agent /silent]
20080506173917 I #3624 Common Pkg CreateDirectory (C:\WINDOWS\TEMP\unz2BE.tmp)
20080506173923 I #3624 Common Pkg CreateProcess (C:\WINDOWS\TEMP\unz2BE.tmp\FrmInst.exe, ...
So I wonder whether maybe the installer is having a problem determining the context or starting the frminst.exe process when running under BDD/LTI.
Posted by:
t9803013
15 years ago
Had the same issue.
1. I ended up placing the command line in a batch file and calling that. Seems to work OK.
2. My next task sequence installed the Viruscan Application. (setup.exe PROTECTION=Maximum /q)
3. My next task sequence does a Mcupdate (mcupdate.exe /update /quiet)
I need to do the update to retrieve the McAfee policies from the EPO server, otherwise any subsequence tasks will be blocked.
many regards
Sanj
1. I ended up placing the command line in a batch file and calling that. Seems to work OK.
2. My next task sequence installed the Viruscan Application. (setup.exe PROTECTION=Maximum /q)
3. My next task sequence does a Mcupdate (mcupdate.exe /update /quiet)
I need to do the update to retrieve the McAfee policies from the EPO server, otherwise any subsequence tasks will be blocked.
many regards
Sanj
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.