A Check if msiexec.exe is running before running install script

[Beekman]

Hello,

Can anybody help me. I am very new at this.

We have a situation that our company is using two distribution channels.

Wintel group is using SCCM and we are using Autoit scripts.

Because Msiexec.exe only can runnig ones on a computer our installations are getting interrupted.

So therefore I want to put a check in the autoit script that checks if the msiexec.exe is runing and if it is running then wait until this process is done or stopt and then starts our installation.

Our script :

$cmd1 = 'c:\temp\mcupgrade\install\setup /s /v"/qb-"'
$cmd2 = 'c:\temp\mcupgrade\elevate c:\temp\mcupgrade\fixpack\setup /s /v"/qb+"'

Local $size1 = FileGetSize("c:\temp\mcupgrade\install\setup.exe")
Local $size2 = FileGetSize("c:\temp\mcupgrade\fixpack\setup.exe")

If $size1 = 173408 And $size2 = 7219000 Then

Local $pid = RunAsWait("administrator account",<password>,"",'"' & @ComSpec & '" /c ' & $CMD1, @SystemDir)
ProcessWaitClose($pid)
RunAsWait("administrator account",<password>,"",'"' & @ComSpec & '" /c ' & $CMD2, @SystemDir)

EndIf

Edited February 16, 2013 by Melba23
Added code tags

[Melba23]

Beekman,

Welcome to the AutoIt forum.

ProcessExists would seem to be the answer to your problem:

While 1
    ; If the process is not running
    If Not ProcessExists("msiexec.exe") 
        ; Break out of the loop
        ExitLoop
    EndIf
    ; Wait a second
    Sleep(1000)
WEnd
; We get here if msiexec is not running

All clear?

M23

Edit: When you post code please use Code tags - put [autoit] before and [/autoit] after your posted code. Then you get a scrolling box and syntax colouring as you can see above now I have added the tags.

Edited February 16, 2013 by Melba23

[Beekman]

Hello Melba23,

Many thanks for the quick response.

But I have still 2 question.

1. You do a check if the process not exists, but what happens in this script if the process exists?

Is this going to wait until the process stops?

2. Is there a possiblility to suppress the UAC from Windows 7 with a autoit command or parameter?

Edited February 16, 2013 by Beekman

[Melba23]

Beekman,

1. You stay in the While...WEnd loop if the process exists - that is why we have the Sleep in there so you do not check too often.

2. Adding #RequireAdmin to your script will force admin credentials to be entered at the start of the script. You will understand that simply suppressing UAC from a script is not something that can (or indeed should) be done. Search the forum and you will find plenty of tips on how to make UAC as inobtrusive as possible.

M23

[JLogan3o13]

As the msiexec process can continue within Task Manager after an installation is run (even if it is not chewing up any CPU), and you mention you have SCCM in the environment, I would suggest a different method. I would check on the CPU usage of the CCMExec process to determine whether SCCM is installing anything. Something like this should work:

$wbemFlagReturnImmediately = "&h10"
$wbemFlagForwardOnly = "&h20"
$PC = "PCName"

$WMI = ObjGet("winmgmts:\\" & $PC & "\root\CIMV2")
$aProcess = $WMI.ExecQuery("SELECT * FROM Win32_PerfFormattedData_PerfProc_Process", "WQL", $wbemFlagReturnImmediately + $wbemFlagForwardOnly)

 For $element in $aProcess
  If $element.Name = "CCMExec" Then MsgBox(0, $element.Name, $element.PercentProcessorTime & "%")
 Next

[Beekman]

Thxx Jlogan, I'am going to try both solutions

[Beekman]

Hi Melba23,

What will the statement be if I want to exit script if process msiexe.exe exist and if not contineu script.

Is that.

if ProcessExists("msiexec.exe") Then
Msgbox(0,"Information","Notes wordt niet geupdate omdat, er een ander programma wordt geinstalleerd")
Exit
endif

Edited March 5, 2013 by Beekman

[Melba23]

Beekman,

As you have it, but without the trailing "." after Exit.

M23

[Tripredacus]

As the msiexec process can continue within Task Manager after an installation is run (even if it is not chewing up any CPU)

It will continue for approximately 10 minutes. I ran into this problem with msiexec staying resident in my installer script. The problem is that if you use RunWait on something that launches the msiexec as a child, then exits, if you don't wait for msiexec to exit normally and reboot, the installation can fail. The Infineon TPM installer is one example of this problem. You can find some details of this if interested:

http://www.msfn.org/board/topic/151373-msiexec-taking-a-long-time-to-complete/page__view__findpost__p__971399

[JLogan3o13]

It will continue for approximately 10 minutes. I ran into this problem with msiexec staying resident in my installer script. The problem is that if you use RunWait on something that launches the msiexec as a child, then exits, if you don't wait for msiexec to exit normally and reboot, the installation can fail. The Infineon TPM installer is one example of this problem. You can find some details of this if interested:

http://www.msfn.org/board/topic/151373-msiexec-taking-a-long-time-to-complete/page__view__findpost__p__971399

That is why, as the OP is using SCCM, I suggested looking at the CCMExec process, rather than msiexec.

Edit: spell check

Edited March 6, 2013 by JLogan3o13

[LarryDalooza]

I believe there will be two msiexec.exe processes. One that is the installation (msiexec.exe) in the users context and one that is the installer service (msiexec.exe) in the SYSTEM context. Also, I believe there may be a registry key that is set while the install is running. That key is cleared by the installer when it is finished. I used to use it, I will try to dig it up.

Lar.

edit: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerInProgress

Edited March 6, 2013 by LarryDalooza