This content has been marked as final. Show 5 replies
Question update: Is anyone using Microsoft BDD/MDT (LTI) to deploy CMA?
Since I cannot install CMA (in managed mode) with VSE package, I have created two separate applications in BDDnull - one for VSE and one for CMA. The problem is that when CMA 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.
have you tried using the force install switch?
FramePkg.exe /FORCEINSTALL /INSTALL=AGENT /Silent
we use this on manually applied batches and unattended VBS scripts and it works for us (also make sure your script has admin rights)
Yes, I tried using FORCEINSTALL switch and get the 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.
I'm experiencing a similar issue, did you find a solution?
No, but it works from a batch file.