- Have the Visual C 2005 Runtime available as a separate
package and install it before QuickTest Pro 9.5.
- Install the vendor-supplied MSI.
- Start a new SetupCapture in Wise Package Studio. Capture
the status with QTP 9.5 installed.
- [Optional] Launch QTP 9.5. Apply all available patches to QTP.
Note: If you want QTP to recognize that the patches are installed,
make sure you capture the Registry key:
HKCR\Installer\Patches\...
These are something you might normally filter out.
- Launch Component Services (dcomcnfg) and make the
following changes, per HP's documentation:
Under Computers -> My Computer:
- Enable Distributed COM
- Set Default Impersonation Level to "Identify"
Under COM Security:
- Under Access Permissions -> Edit Limits
Give Local and Remote access to:
Administrator
Administrators
Everyone
Interactive Users
Network
System
Authenticated Users
Anonymous Logon
- Under Launch & Activation Permissions -> Edit Limits
Give Local and Remote Launch/Activation access to:
Administrator
Administrators
Everyone
Interactive Users
Network
System
Authenticated Users
Anonymous Logon
Under DCOM Configuration -> AQTRMTAGENT -> Properties:
- Identity -> The Interactive User
- Security -> Launch and Activation Permissions ->
Customize -> Edit -> Add:
Administrator
Administrators
Everyone
Interactive Users
Network
System
Authenticated Users
Anonymous Logon
- Give the above users/groups "Allow" for all the
launch and activation Permissions.
- Under Launch & Activation Permissions -> Edit Limits
Give Local and Remote Launch/Activation access to:
Administrator
Administrators
Everyone
Interactive Users
Network
System
Authenticated Users
Anonymous Logon
- Under Access Permissions, give access to:
Administrator
Administrators
Everyone
Interactive Users
Network
System
Authenticated Users
Anonymous Logon
- [Recommended] Launch QTP and under Tools -> Options ->
General -> Uncheck "Check for Updates"
(This, BTW, is stored in the Registry under:
HKLM\SOFTWARE\Mercury Interactive\QuickTest Pro\MicTest:
CheckForUpdates
and
HKCU\Software\Mercury Interactive\QuickTest Pro\MicTest)
- [If using Quality Center or other HP/Mercury products
with Quick Test Pro] Under Tools -> Options -> Run ->
check "Allow other HP products..."
(This, BTW, is stored in the Registry under:
HKLM\SOFTWARE\Mercury Interactive\QuickTest Pro\MicTest:
AllowTDConnect
and
HKCU\Software\Mercury Interactive\QuickTest Pro\MicTest)
- Complete the SetupCapture to create a WSI of the above
changes.
- Edit the WSI to open Port 135 in the firewall for DCOM,
and to create an exception for the program:
\QuickTest\bin\AQTRMTAGENT.EXE
- [If your QuickTest users will not have Administrator
access to the machines they'll be running QTP on, the
following changes are needed]
Add an Embedded VBScript to the Execute Immediate tab
of the Windows Installer Editor's MSI Script editor,
in the location just after "InstallFinalize"
that provides users with read/write access to:
c:\Program Files\Common Files\Mercury Interactive
C:\Program Files\HP\QuickTest Professional
[If you use Quality Center:]
C:\Program Files\HP\QuickTest Addin for Quality Center
Add an Embedded VBScript after the one above to give
the users read/write access to:
C:\Windows\Mercury.INI
[and if you want them to be able to delete the desktop
icon...]
C:\Documents and Settings\All Users\Desktop QuickTest Professional.lnk
The above can be done by calling the CACLS utility
from your VBScript.
- In the Installation Expert's Target System ->
System Search function, add a search for the key:
SOFTWARE\Mercury Interactive\QuickTest Professional\CurrentVersion
and assign it to the REGVERSION property.
- In the MSI Script editor, just below "CostFinalize",
Add the code:
If REGVERSION <> "QuickTest Professional 9.5" then
Cancel Installation Could not find QTP 9.5
End
- Compile the MSI. After pushing both MSIs (the original
and this new one) to a machine, it should allow the
product to run and be controlled by Quality Center (if
appropriate).
When I read the poster above me I was like "Hmm.. I just got a complex package" I try installing the software with the .msi with ISSETUPDRIVEN=1 but the software wasn't completly installed, the software won't start. After that, I look at the installation manual (yeah, the manual no one read :P) and you can read this Setup can be record (like any other InstallShield Setup). I don't like that method because if you have different PC in the field, you will have different installation windows and your setup.iss will not have the information and installation will fail. But, I still prefer use that method than repackage an .msi. (*shiver*)
I create an answer file, test it on a prod PC and it works like a charm.
Record : setup.exe -r (once the installation is complete, the setup.iss will be in WindowsFolder)
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
