Help with HP Openview install

Content Authoring
1

(imported topic written by tigger0191)

I’m used the Windows Software Deployment Wizard to create a task that installs HP Openview on Windows Server 2003 x64. I have a batch file that kicks off a .vbs script. Action script below.

download http://my.bigfix.server:52311/Uploads/e5614a85cbaf8621650d9194e6975acd870216eb/Win-64bit.tmp

continue if {(size of it = 83093688 AND sha1 of it = “e5614a85cbaf8621650d9194e6975acd870216eb”) of file “Win-64bit.tmp” of folder “__Download”}

extract Win-64bit.tmp

dos if not exist C:\OSS\hpov\Win-64bit mkdir C:\OSS\hpov\Win-64bit

dos move __Download*.* C:\OSS\hpov\Win-64bit

wait C:\OSS\hpov\Win-64bit\HPOVinstall.bat

All lines complete successfully in the BES client log. The log file below is from the HP Openview installer vbs itself. When I just double click on this .vbs, the install works fine. Below it can be seen that the first .msi gets installed, but then the .vbs fails after that. Its supposed to install several other .msi(s).

What is it about the environmental context in which the BES Client runs that is different than my interactive user environment context?

opc_inst Info: Packages successfully deinstalled.

opc_inst Info: Executing cmd /c change user /query > “C:\WINDOWS\Temp\radEB8A7.tmp” …

opc_inst Info: We have Terminal Server INSTALL mode (or compatible).

opc_inst Info: OVO (De-)Installation script starting at 1/11/2011 12:44:33 PM.

Log file: C:\WINDOWS\Temp\opc_inst.log

opc_inst Info: Executing cmd /c change user /query > “C:\WINDOWS\Temp\radF448D.tmp” …

opc_inst Info: We have Terminal Server INSTALL mode (or compatible).

opc_inst OvSystemComponent already exists, hence use the same value Warning

opc_inst Info: Testing MSI installer version. Need at least 2|6.*.

opc_inst Info: MSI installer version is 2.82.1830.0.

opc_inst Info: Testing for OVO 7.x agent …

opc_inst Info: Registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard\OpenView\ITO not set.

opc_inst Info: No OVO 7.x agent found.

opc_inst Info: Installing OVO agent …

opc_inst Info: Installing package HPOvXpl.msi …

=== Logging started: 1/11/2011 12:45:21 ===

=== Logging stopped: 1/11/2011 12:47:01 ===

opc_inst Error: Package HPOvXpl successfully installed but not found in inventory.

opc_inst Info: Executing cmd /c change user /query > “C:\WINDOWS\Temp\rad0FF6C.tmp” …

opc_inst Info: We have Terminal Server INSTALL mode (or compatible).

2

(imported comment written by JackCoates91)

it’s running as local system. Try runascurrentuser.exe… support.bigfix.com/cgi-bin/kbdirect.pl?id=392

3

(imported comment written by tigger0191)

The installations are all happening on servers. There will be no user logged on at the time when the task is run. Per the article, ““RunAsCurrentUser.exe” will not work unless a user is logged into the local computer”.

Back to the issue at hand, What is it about the environmental context in which the BES Client runs (local system) that is different than my interactive user environment context (current user)? Why does the script start and then fail when the BES agent runs it, but succeed when I double click the .bat?

Thanks for your help.

4

(imported comment written by MattBoyd)

I think it’s hard to say without seeing what’s in the bat file. Environment variables, such as the user profile folder, are different for SYSTEM than the current user. Also, the HKEY_CURRENTUSER context is different. I’m not sure why this would affect an installer though.

Did you try running it with this?

action uses wow64 redirection true

5

(imported comment written by JackCoates91)

Does it fail if you run it this way? http://support.bigfix.com/cgi-bin/kbdirect.pl?id=1681