Intel SCS not provisiong/configuring Vpro Clients using Profiles

thanks cdpiper for your response, the reason am sticking to version 5.4.0 of intel scs is that, it is bundled with HPCA, i am trying to actually deploy HP Client Automation and that has capability to integrate with Intel SCS. So for that reason, i have to stick to this version.

my main concern was since i was getting this error over and over again, so is it due to the fact that i am using Standard version and not enterprise version?

thanks

fahad

thanks for the reply.....

what i have done is that i created two profiles, one with TLS and one without TLS.

I have observed that the clients get provisioned in both the cases but there are SOAP errors of different nature as mentioned previously in the Intel SCS logs, however using the non-TLS profile, things work smooth, so for now i am sticking to non-tls provisioning.

I have attached screenshots of what i have achieved, However.....now i am trying to use HPCA OOBM agent, in that agent we need to put AMT parameters as well which i have done but i am constantly getting error messages, SOAP ERROR 21 & SOAP ERROR 22 etc .... and i am unable to get information on these errors, even i have tried to install OOBM agent on Intel HPCA system so that the agent doesnt need to connect to the server over the network but even then am getting this error....

please advice where i might be wrong?? Please see screenshots as well.....

thanks

fahad

hello,

i have moved further and installed HP OOBM client even on the server where HPCA itself is installed, please see the screenshots,

ERROR # 1

the SOAP Error 22 means that No user with this profile    name can be found.

ERROR # 2

HPCA-OOBM error: 0
Error calling method: RegisterWatchdog, Error code: 22

please see the screenshots, i have listed my users and profiles i am unable to understand why this SOAP Error is coming.

kindly help am drained out why its not connecting

thanks

fahad

ok guys i have got it all working....... i was actually trying to intall HPCA OOBM agent on the client computer to connect to the HPCA server the reason why this error was coming was due to the fact that i was not associating the watch dog policy with the Vpro Client.

What i did is:

Simply install the HPCA OOBM agent on the client computer, it started giving the errors mentioned earlier in the event logs.

Next i went to the HPCA server and in the Operations Tab , Device Management, I selected the Vpro Client and deployed watch dog policy on the system

The HPCA OOBM agent then got connected with the watchdog and things started working.

Thanks all for your help. Please see the screenshots, so it might help someone.

Another Issue

Also the only error i see now is that i have a Vpro Client that is not part of domain and thus not showing in the Active Directory OU.

I installed the HPCA OOBM agent on it and applied the same Watch Dog policy but it showed in HPCA that the agent has expired

On other forums i have read that i need to adjust starttime and heartbeat interval, which i think is not  required since these parameters are adjusted in the watch dog policy or directly in the config.properties file but since the same policy is working fine for the other system so this is not the issue

What i have observed is that in the HPCA OOBM agent install directory there is Activator.exe and that requires the paramters OU as well

Since my system is not in the OU so it might be the reason why the agent is set to be expired.

Will put my system in domain and move it in the OU to test if this is the issue...... any ideas in this regard are most welcome

thanks

fahad