rct fails with heci handle error

[idata]

i am attempting to restart hello packets via the rct tool (version 3.3.1.0) and i get a "heci error: cannot establish a handle to the heci driver. (5): access is denied" message

i am using an hp dc7800 desktop with the latest bios and mebx f/w and have reprovisioned with a usb key from an intel scs console generated psk pair. i have also disabled the vista firewall and have reinstalled the heci driver off the hp web site.

the run string i use is"rct.exe /c /f /h /s https://hpopenview.vprodemo.com/amtscs"

any help or idea would be appreciated

dan felman

[JoshHilliker]

Are you logged in under an admin account on the box?

also what version of SCS are you running?

Here's my post on how to run the RCT tool - http://communities.intel.com/openport/blogs/proexpert/2008/04/03/remote-configuration-rctexe-how-tos Also there is a new version of it posted called the Activator which provides the same type of function.

J

[idata]

it seems as if every sample run has the /o option set... what if all i want is to just start sending packets again, what is the minimum number of runstring options i need to use?

[JoshHilliker]

rct /s http://provisionserver.yourenterprise.com/amtscs /t on /h

try this..

[Terry_C_Intel]

Hi Dan

On the vPro client - Do you have local admin access to execute the RCT.exe tool? Per your comment - sounds like the latest MEI\HECI driver was installed - was the LMS driver also installed?

The RCT.exe tool was recently updated to Intel vPro Activator Utility - available at http://www.intel.com/software/activator. That site also includes some user\administrator guides.

Per the command line and switches shown - you are trying to send hello packets while also synchronizing the FQDN of the client.

To initiate\send hello packets - Activator /s https://hpopenview.vprodemo.com/amtscs_rcfg /h /c

Other options\capabilities in the user docs are the Activator link above. Anything beyond sending hello packets and transitions to on (enabled AMT in the MEBx) requires a priviledge domain account to execute the command. The domain account is specified as a "Configuration Client" role in the SCS console.

Hope that helps