Does anyone have any ideas on how to install "HP Hotkey Support" silent? It currently requires admin permissions after rebooting.

It was exactly the same problem with Quick Launch Buttons earlier but there were at least "KbdHook" parameter that solved the problem.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1
When you run the exe, it extracts to C:\SWSetup\SP47618 (or something like this) which contains an MSI. I don't have and HP machine to test with so I can't help you much from that point, but you should be able to use something like the following command to install.

msiexec.exe /i HPHKS.msi ALLUSERS=1 REBOOT="ReallySuppress" /qn

I also wasn't able to open the MSI to look inside or to make an MST.
Answered 07/07/2011 by: jmaclaurin
Third Degree Blue Belt

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
I usually deploy it through SCCM task sequence, it took me a while to figure it out, but after reboot you need to set a registry key, I do that with (hmm) a vbscript which will be fround upon here, because it´s not considered a good one (no error trapping). The program adds a new hardware (sigh) which is only found after reboot (sigh no.2), "Keyboard filter", the value has to be set by administrator. I am not at work but If you want I can post the min required regkey that has to be set later.
I personally would love to see a better solution, so if anyone else has one please share.
Answered 07/07/2011 by: admaai
Orange Senior Belt

Please log in to comment
0
admaai:
Any chance you can post that vbscript or regkey.

I have been able to semi-automate the installation by using a similar command line like jmaclaurin posted.

HPHKS.EXE /q /l*v "%windir%\system32\logfiles\HPHKS.log" REBOOT=REALLYSUPPRESS

That command worked for a silent install, but it doesn't fix the new hardware prompt upon reboot.

I am using Altirs not SCCM, but none the less we are running into the same problem. I was going to run a job that would temporarily login with local admin credentials so that the software would install properly after reboot, wait 30 seconds, then logoff. However that seems kind of sloppy.


Thanks in advance for any help!
Answered 07/07/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
I presume, since you're trying to package this, that you're installing to multiple machines? That implies a corporate environment, which begs the question: Does anyone really install this junk for real?

If you have to install it, surely it belongs in the build?
Answered 07/08/2011 by: VBScab
Red Belt

Please log in to comment
0
VBScab:
In my case, yes I am installing this in a corporate environment for a new model of HP laptop that will be our new standard going forward. I do not have the option available to crack open my image and apply the driver/software, that's why I am trying to install this application after the fact. Unfortunately in order to get some of the functionality like adjusting brightness / contrast, volume up/down, we need this piece of garbage software installed.
Answered 07/08/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
FYI:
I have a case open with HP Support. If they provide me a fix I will be sure to share the information here.
Answered 07/08/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
Sorry for late response, the reason it is needed is because it controls a lot of features, like changing the screen mode from laptop to external on the fly (with Fn keys).
Although SCCM restart the computer many times after installation and installs other programs, if I do not add the reg entry it still comes out with missing driver in the end.
I got so swamped at work today that I totally forgot to check the reg entry, sorry for that too:). But here is the method to find it, i used it for xp, since we have not yet migrated, download Regshot [link]http://sourceforge.net/projects/regshot/[/link], put it somewhere you can find it, install the hotkey software on a new laptop, and reboot when it prompts, login as a restricted user, you get the admin popup to install a new hardware, fire up regshot as local admin, take 1st snapshot, insert localadmin credentials in the popup for installing new hardware and let it get installed, then take your second snapshot.
I actually found this when quicklaunch started playing its song and dance, amazingly the exact same registry script works for Hp hotkey.
BTW I opened the msi in wise, at a fast glance, it had nothing except properties. Everything else was done in mst.
Answered 07/08/2011 by: admaai
Orange Senior Belt

Please log in to comment
3
Hey guys,

I think I figured this one out.

You have to install the "HP Software Framework" first.

I used the following commands in SCCM.

HP Software Framework: HPSWF.EXE /qn
HP Hotkey Support: HPHKS.exe /qn

You might want to add /norestart (but I never tested it for hotkey support. tested it for the framework though.)
Answered 07/08/2011 by: hpsux
Yellow Belt

Please log in to comment
0
admaai:
I have tried to identify the reg key by using Regshot, but that did not work. I identified a couple of keys under HKLM\System\Control\CurrentControlSet and ControlSet001 \Enum\{Some guid for the HP Keyboardfilter}. I then exported those keys to a .reg file and ran a batch file that would import that reg file after HPHKS.exe was installed. I rebooted and logged in with an account that did not have admin rights. I was still prompted for admin credentials to install the keyboard filter driver :(

hpsux:
I tried your suggestion as well by installing the HP Software Framework followed by Hotkey Support with no luck :(

Meanwhile, HP Support called me back today and basically provided me the silent install command that we already know not to be working. I had to provide the symptom again and clarify that we know how to silently install this silly driver, but need to know how to prevent the computer from prompting us for admin credentials the first time a user logs on. We will have to wait and see.

For a workaround, I have implemented a script where I move this computer to a temporary OU which allows me to AutoAdminLogon, lock the workstation right away, wait 60 seconds for the computer to recognize that new hardware is installed, move back to the standard OU where GP is applied, remove autoadmin logon, and reboot. Not exactly pretty, but it works. I really hope that HP comes back with a better solution.
Answered 07/11/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
as a general rule HP always puts the silent install instructions in the .CVA file that is in the spxxxx.exe
Answered 07/12/2011 by: sbequette
Orange Belt

Please log in to comment
0
Thanks sbequette!

I didn't realise what the .cva file was for. Unfortunately in this case the instructions in the .cva file do not fix my issue. The .CVA file simply references the install instruction similar to jmaclaurin's post.

However, it is good to know what that .cva file is used for future use.
Answered 07/12/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
jstorino: you have to apply the registry fix after reboot, that is why I do it with os deployment as one of the tasks, I´ll post the script tomorrow.
On another note, now I´m stuck @ Ericsson Mobile Broadband Drivers.
And for anyone who doesnt want the fingerprint crap to be installed, the drivers are in merge modules.
To tell the truth I do not know why corporates buy HP.
Answered 07/12/2011 by: admaai
Orange Senior Belt

Please log in to comment
0
Admaii:
Thanks for the info. I look forward to your reply tomorrow. Good luck with your Ericcson issue
Answered 07/12/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
Ok here it goes, please do not laugh at my scripting, I know there is a lot of stuff wrong with it. I am not going to spend time on it, but if someone wishes to improve, it´s definately appreciated.
jstorino: Check that you have the same keys/values in your envirement, and run this script after install and reboot.
'On Error Resume Next
const HKEY_LOCAL_MACHINE = &H80000002

strComputer = "."

Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv")

strKeyPath = "SYSTEM\ControlSet001\Enum\{A87C2E0F-9A46-46b8-8EC4-E33355FBE1F7}\KeyboardFilter"
oReg.EnumKey HKEY_LOCAL_MACHINE, strKeyPath, arrSubKeys
For Each subkey In arrSubKeys
strValueName = "ConfigFlags"
strNewValue = 0
STRNewPath = strKeyPath & "\" & subkey
oReg.setDWORDValue HKEY_LOCAL_MACHINE,STRNewPath,strValueName,strNewValue
' msgbox dwValue

Next

strKeyPath = "SYSTEM\CurrentControlSet\Enum\{A87C2E0F-9A46-46b8-8EC4-E33355FBE1F7}\KeyboardFilter"
oReg.EnumKey HKEY_LOCAL_MACHINE, strKeyPath, arrSubKeys
For Each subkey In arrSubKeys
strValueName = "ConfigFlags"
strNewValue = 0
STRNewPath = strKeyPath & "\" & subkey
oReg.setDWORDValue HKEY_LOCAL_MACHINE,STRNewPath,strValueName,strNewValue
' msgbox dwValue

Next
Answered 07/13/2011 by: admaai
Orange Senior Belt

Please log in to comment
0
All:
HP contacted me last week and provided a beta version of the driver that will officially released in an updated Softpaq "shortly". I tested their driver and it resolved the issue.

Below is a snipet I took from HP's release notes

Version 4.0.21.1 A1 (7/12/11)
Build process uses HP CASL SDK 4.1.8.1 in this release.

NOTE: This version is a point solution, intended to be distributed to customers via 3LS on an as-needed basis. It is intended only for Windows XP, non-Tablet HP notebooks. It addresses an issue seen by customers who remotely deploy Hotkey Support to XP systems which are used only by limited users, namely that a “Found New Hardware” dialog is presented after the post-installation reboot which requires admin privileges. The root cause of this issue is the way XP handles the installation of filter drivers.

Adds support for the INSTALL_DRIVERS installation command-line MSI property. The default is “Yes” – which results in same behavior as prior versions. However, when INSTALL_DRIVERS=No is specified on the installation command-line, then the installation bypasses the installation of drivers and uses a keyboard hook instead.
Answered 07/22/2011 by: jstorino
Senior Yellow Belt

Please log in to comment
0
Thanks jstorino, nice of HP:) But I got a lot of gripes with that company: Why hardwares gets detected after you install their programs(mobile broadband), why their software insist on creating logs with no possibility of redirecting (mobile broadband), so that you are unable to deploy from network, Why they just don´t create drivers without bundling everything, secrecy about commandlines(Roxio secure burn), No silent uninstalls (Roxio secure burn) etc, etc, etc.Those are just the newest addtions.
Answered 07/22/2011 by: admaai
Orange Senior Belt

Please log in to comment
0
I can confirm that the following commands in SCCM work:

HP Software Framework: HPSWF.EXE /qn
HP Hotkey Support: HPHKS.exe /qn

All I did at the end of the install in the task sequence was add a 'Restart Computer' step.

I also logged onto the deployed machine (HP 6450b) as a standard user & didnt experience the 'Add New Hardware' Prompt. Also, there was no need to add any registry entries etc. All the Function keys work perfectly!! [:D]
Answered 08/21/2011 by: Adz
Yellow Belt

Please log in to comment
0
Just to add my two bits, I was able to deploy the HP HotKey Support SoftPaq via SCCM using the following steps
  1. Download the SoftPaq herehttp://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=ca&prodTypeId=321957&prodSeriesId=5060942&swItem=ob-95315-1&prodNameId=5060944&swEnvOID=4060&swLang=13&taskId=135&mode=5
  2. From the sp53547.exe I used WinRAR to extract the source files
  3. Run the following command in the SCCM program HPHKS.exe /qn /norestart

I've been able to test this via Run Advertised Programs on both x86 & x64 Windows 7 8460p & 8460w machines. Because to package does require a reboot and rebooting is unexceptable when in the TS I added the /norestart and add a reboot task immediatly aftward. I did notice that during testing it would install but I couldn't use the Fn keys for brightness right away. The following services should be started automatically but don't start right away.
hpHotKeyMonitor
HP Software Framework Service
HP Service

Hope this helps someone else, and thank you to everyone who has already left comments on this topic, I wouldn't have been able to get this otherwise.
Answered 09/21/2011 by: Arcuss88
Senior Yellow Belt

Please log in to comment
0

Hi guys, i had to deploy this piece of junk garbage software through many deployment systems.

Symptomes:


 The hotkey utility is installed from Empirum(SW distribution system like SCCM), after restart when the user logs in,
the hotkey 'device' is recognized and admin password requested.

 The registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\{A87C2E0F-9A46-46b8-8EC4-E33355FBE1F7}\KeyboardFilter\5&3a7b2914&0&01]  -> "ConfigFlags"=dword:00000000
this key prevents hotkey from bringing the admin password dialog up for the user,
and the method i used installs the key after reboot but before the user logs on
However in most cases the hotkey utility is not working, but the service is installed and running, the device is present in device manager, and the utility itself is installed as a program.

The only working solution i found was this:

-Install the software silent (setup.exe /s /v"/qn REBOOT=REALLYSUPPRESS")

-run a small script that schedules a script for running after restart:
schtasks /create /tn "HPHKFIX" /tr "c:\temp\startfix.cmd" /sc ONSTART /ru "System" >>c:\temp\hkfix.log 2>&1

-in that script, (patch the registry with the few keys i found to be responsible, delete the task of running again, and waiting a bit):
REG IMPORT hkfix.reg >>c:\temp\hkfix.log
schtasks /delete /tn "HPHKFIX" /f >>c:\temp\hkfix.log 2>&1
ping 127.0.0.1 -n 60

-the contents of the regfile hkfix.reg:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\{A87C2E0F-9A46-46b8-8EC4-E33355FBE1F7}\KeyboardFilter\5&3a7b2914&0&01]
"ConfigFlags"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HPHOTKEYMONITOR\0000\Control]
"*NewlyCreated*"=-
"ActiveService"="hpHotkeyMonitor"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WDF01000\0000]
"Service"="Wdf01000"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="Kernel Mode Driver Frameworks service"
"Capabilities"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WDF01000\0000\Control]
"*NewlyCreated*"=-
"ActiveService"="Wdf01000"

-MOST IMPORTANT !!!!!! the hotkey will ONLY work after 2 REBOOTS! (first to instert/erase the keys, second to activate them)

Maybe the first key is enough, who knows, it was in the previous version of the software, but i spent too much time trying to fix this, so i just post what works, and you figure out the rest...

Also, my real scripts do time and other logging too, and not located in c:\temp... but i omitted those for shortness sake...

I hope this helps!

Csaba

Answered 01/25/2013 by: Edocecrous
White Belt

Please log in to comment
0

Thanks for the info Edocecrous.  Hopefully I am done trying to deploy this piece of garbage software on Windows XP systems.  Going forward our new deployments will all be Win 7.  However, if the need should arise, I will try your workaround.

Answered 01/28/2013 by: jstorino
Senior Yellow Belt

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