Hi,

I'm in the unenviable position of having to deploy Avaya Phone Manager 4.2.12 across our user base of around 300 people. I've run an administrative install, and unpacked the pmpsetup.exe to a network source, created a package in SMS 2003 and have successfully deployed this to a test group of clean machines.

Unfortunately, I have to uninstall our previous version 3.1.12 before rolling this out to our users. Has anyone any experience with Avaya IP Office Phone Manager deployments and uninstallations prior to 3.2?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
What is it you need help with?

- The uninstall command?
If the application appears in Add/Remove Programs, there ought to be an entry called 'UninstallString' somewhere in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode or ProductName].

- Command line switches to the setup EXE, maybe?
If the vendor doesn't document them (no surprise there, of course...) you can sometimes get lucky by executing it with a nonsense switch, e.g., SETUP /FORGODSSAKEHELPME.
Answered 01/22/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

What is it you need help with?


That would have been more helpful, wouldn't it?

What I was after was how to uninstall the software, starting from first principles. Never actually ran an automatic removal before.

ORIGINAL: VBScab

- The uninstall command?
If the application appears in Add/Remove Programs, there ought to be an entry called 'UninstallString' somewhere in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode or ProductName].


UninstallString is listed as RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{20D9E71A-F736-494E-873B-4DD644894A97}\setup.exe"


ORIGINAL: VBScab

- Command line switches to the setup EXE, maybe?
If the vendor doesn't document them (no surprise there, of course...) you can sometimes get lucky by executing it with a nonsense switch, e.g., SETUP /FORGODSSAKEHELPME.



No, I've noticed no information on the vendor's site about this, which is as you say, not surprising, seeing as it's meant to be used as a client installation in small-medium sized companies.

I'll have a look at the switches for the uninstall setup.exe and see what I get.

Thanks for your help so far.
Answered 01/22/2009 by: rwb_deploy
Yellow Belt

Please log in to comment
0
UninstallString is listed as RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{20D9E71A-F736-494E-873B-4DD644894A97}\setup.exe" Nice and easy...this entry identifies the original installer as having been authored in InstallShield (and driven by InstallScript rather than MSI) so you can - if required - look up the switches for silent/unattended uninstallation. IIRC, there are differences between engine/driver versions (this particular app was installed by a v6 engine, as you can see).
Answered 01/22/2009 by: VBScab
Red Belt

Please log in to comment
0
thanks for your help so far!

Hope you can help me out a bit further. I've run the uninstallstring and recorded a response file, and the removal routine works correctly from the commandline, so I'm nearly there. One thing though, is a pop-up confirmation box (received after removing one of the components) runs as a different process: it.exe ('install TAPI', possibly). I need to figure out how to OK this box or kill the process before the removal can proceed, but this is not recorded as part of the response file.


[InstallShield Silent]
Version=v6.00.000
File=Response File
[File Transfer]
OverwrittenReadOnly=NoToAll
[{20D9E71A-F736-494E-873B-4DD644894A97}-DlgOrder]
Dlg0={20D9E71A-F736-494E-873B-4DD644894A97}-SdWelcomeMaint-0
Count=3
Dlg1={20D9E71A-F736-494E-873B-4DD644894A97}-SprintfBox-0
Dlg2={20D9E71A-F736-494E-873B-4DD644894A97}-SdFinish-0
[{20D9E71A-F736-494E-873B-4DD644894A97}-SdWelcomeMaint-0]
Result=303
[{20D9E71A-F736-494E-873B-4DD644894A97}-SprintfBox-0]
Result=1
[{20D9E71A-F736-494E-873B-4DD644894A97}-SdFinish-0]
Result=1
bOpt1=0
bOpt2=0
Any pointers?
Answered 01/26/2009 by: rwb_deploy
Yellow Belt

Please log in to comment
0
Hmmm...there are 2 options, I suppose. One, use something like AutoIt to "press" the 'OK' button [shudder...] or something PSKill to kill the process. PSKill has taken over from TaskKill in my armoury as it's somewhat more aggressive about processes it can tackle. You would probably need to script either of those actions. There are many, many samples available for download concerning task detection and killing.
Answered 01/27/2009 by: VBScab
Red Belt

Please log in to comment
0

Hope you can help me out a bit further. I've run the uninstallstring and recorded a response file, and the removal routine works correctly from the commandline, so I'm nearly there. One thing though, is a pop-up confirmation box (received after removing one of the components) runs as a different process: it.exe ('install TAPI', possibly). I need to figure out how to OK this box or kill the process before the removal can proceed, but this is not recorded as part of the response file.

[InstallShield Silent]
Version=v6.00.000
File=Response File
[File Transfer]
OverwrittenReadOnly=NoToAll
[{20D9E71A-F736-494E-873B-4DD644894A97}-DlgOrder]
Dlg0={20D9E71A-F736-494E-873B-4DD644894A97}-SdWelcomeMaint-0
Count=3
Dlg1={20D9E71A-F736-494E-873B-4DD644894A97}-SprintfBox-0
Dlg2={20D9E71A-F736-494E-873B-4DD644894A97}-SdFinish-0
[{20D9E71A-F736-494E-873B-4DD644894A97}-SdWelcomeMaint-0]
Result=303
[{20D9E71A-F736-494E-873B-4DD644894A97}-SprintfBox-0]
Result=1
[{20D9E71A-F736-494E-873B-4DD644894A97}-SdFinish-0]
Result=1
bOpt1=0
bOpt2=0
Any pointers?


This whole exchange shows how much isscript sucks. You could use Ian's suggestion and try pskill/autoit, or just repackage. I would favor repackaging.
Answered 01/27/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
I would favor repackaging. Hmmm...there are 3 options, I suppose. LOL. Yeh, I'd agree.

(Owen, you did mean re-package the uninstall, right?)
Answered 01/27/2009 by: VBScab
Red Belt

Please log in to comment
0
This isn't really isscript's fault, it's the @sshat who wrote the code.

I'd use a vbscript to wait for it.exe to appear, then kill it.

I used to repackage these types of apps as a rule, but lately I've found it's much less work to make the native installer silent. So much can go wrong repackaging a complicated app.
Answered 01/27/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity