I'm setting up SCS with Remotly configuration. Now I want to configure a client but get the following error. I didn't have installed a PKI cert, don't know if that is the issue.
I'm not sure if this is the bet place to post this, so forgive me if this belongs elsewhere. I did actually find similar issues mentioned in this forum, but none of the solutions suggested seemed to work for me. Rather than bump an old thread, I thought it best to start a new one.
I'm just trying to create Alarm Clock with wsman utility, but I couldn't figure out how to do it, can somebody help me?
Trying to execute this command:
root$ wsman put -k ElementName"DefAlert" -k StartTime="2014-07-15T22:00:00Z"-k Interval="PT12M" -k DeleteOnCompletion="true" http://intel.com/wbem/wscim/1/ips-schema/1/IPS_AlarmClockOccurrence?Inst..."DefAlert" --port 16992 -h 192.168.0.14 --username admin -p "Admin44$" -V -v
I get such response:
we are a physics department at a large German university where we deploy several hundred desktop PCs running both Windows and Linux. We use Intel AMT to perform maintenance and administration of these computers since it helps to minimize the amount of sneaker networking we have to do.
All desktop PCs are DELL OptiPlex machines, ranging from 745 series machine through 755, 760, 760, 780 and up to current machines like the OptiPlex 9080, all these machines support Intel AMT.
can someone please explain me, how to do remote configuration of Intel AMT PC, integrating it into Active Directory?
Is it possible to do such a configuration with Intel SCS or Open MDTK?
Thank you in advance!
Today I installed vPSM_184.108.40.20634 and tried to connect to a vPro 9 client. I got the following error:
I am trying to use the Intel® vPro™ Platform Solution Manager to connect to a machine.
I enter all the machine data including IP address, username, and password, but when I press connect(or let it autoconnect) I see the following error and the program crashes.
I'm confused about this mysterious port that isn't open after I provision a computer into CCM. In my provisioning profile, I enable KVM and all the other redirection options, and set an RFB password but apparently this is still half-baked after a provision. For example, if I try to connect to the machine via UltraVNC I get this:
I don't get a prompt for a password or anything. Just a failed to connect error.
But here's the thing. If I go into the Manageability Commander, I see this: