I am trying to understand why VLAN is no longer a supported feature in AMT 4, 6 and greater.
We wanted to deploy several 1000 (!!) desktops with AMT version 7 and in our prototype we found out that these boards no longer support vlans.
From a management perspective those boards have become useless without being able to use a tagged vlan for maintenances, deployments, etc...
Is there any workaround for this?
- Andy
I am currently implementing vPro in my organization and could use some assistance. I used a USB Drive to set the Mebx password initially. I used the default password of admin, and then the usb key changed the password to my 32 bit string. That worked well. I now have setup profiles in the SCS console to my liking, and everything is working correctly. However, I still have not found a way to change the mebx password since then. I can change the password if I create a new USB key, or if I manually enter the new password into the mebx, but how is this accomplished using either ACUConfig or with a profile? Is this even possible? I have done a ton of searching and have not yet found an answer to my question.
Thanks,
Alex
I'm trying to find the proper client needed to connect to the Q87 AMT desktops I have built for our company. I've found the Intel Platform Solution Manager and that appears to be the only program out there (after I found a bunch of open source programs that do the same thing).
However there seem to be some quarks with it.
1) Is there a better program than the Platform Solution Manager?
2) How can I tell if the network connection is 1Gb and not 10Mbps? It appears to only connect at 10Mbps.
3) If I create a partition (IE: Z:\) and load it with the ISO's I would typically need on that hard drive to do a reformat or troubleshoot (Like hirons, or WinPE, or Trinity, or the Windows install disk) how can I get the computer to boot to those local iso files?
Thanks.
We are currently using AMT alarm clocks to wake up computers nightly. We have computers with Version 5, 7 and 8. We set the same alarm clock on all PC's through PowerShell and have some interesting results. AMT version 7 and 8 PC wake at the set time. Version 5 machines will wake about 3 hours later. I was wondering if anyone else was able to successfully set and wake AMT version 5 machines or if you were experiencing the same results. I should note that the AMT clock was set to be synced with the OS on provisioning.
When accessing a v
Pro enabled workstation, how are the identity of the remote workstation and the client making the remote access call positively authenticated? What prevents anyone with the proper password from accessing the remote client?
Hit everyone.
AMTAlarmClock Feature via Powershell. When i try to use the code with a AMT 5.2.7.0 machine it Fails. A 8.0 Version works great.
The PDF documentation Shows that it should support machines over 5.1.
Is there something else i have to do with the 5.2.7.0 machines?
Atm i use the following code
Set-AMTAlarmClock-ComputerName$Compi-Credential$a-TLS-AlarmTime:2014-09-10T11:00:00
The credentials are stored in a variable.
Thank's for the help.
AMT SDK 8.0 のサンプルソース(root\Windows\Intel_AMT\Samples\WS-Management\RemoteControl\RemoteControlTyped\C++)
を参考にし、AMTによるリモートPCの起動状態の参照機能を実装することを考えています。
サンプルから抜き出した以下の処理について質問があります。
------------------------------------------
CimOpenWsmanClient wsmanClient(,,,,,,,);
CIM_AssociatedPowerManagementService associatedPowerManagement;
std::vector<shared_ptr<CIM_AssociatedPowerManagementService> > apmVec = associatedPowerManagement.Enumerate(wsmanClient);
associatedPowerManagement = (*apmVec[0].get());
PowerState currentPowerState = (PowerState)associatedPowerManagement.PowerState();
------------------------------------------
リモートPCの電源が通電していない場合や断線している状態のときには、
CIM_AssociatedPowerManagementService.Enumerate() がタイムアウトする
までに約２０秒を要してしまいますが、これをもっと短い時間にする
ことは可能でしょうか？
当方の推測ですが、WS-Managementは下位プロトコルにhttpやhttpsを利用
している関係上、タイムアウトはOSのTCPのコネクションのタイムアウトに
依存してしまうたため、このタイムアウト時間を変更することはできな
いのではないかと思っています。
Hi everyone. Could you please help to solve issue with time sync.? I'm trying to use Kerberos authentication, but it failed, because I cannot sync time at client amt firmware and DC(difference - 3 hours).
I tried to use maintenance in SCS console and in logs says that it was successful(but time is still not synchronized).
Also, at profile I mark point - Synchronize intel AMT clock with operation system - no results
Server - windows 2008,R2. RCS server version 9.1.0
Client - laptop HP 640, AMT version 9.0.22
Any suggestions?
Regards, Ivan.
When I remote control a HP 800 G1 with AMT9 and I use an IDE redirected boot CD image, once the OS boots, it can't find any local hard drives. Therefore I can't copy an image to said missing local hard drive, which is what I'd normally do next.
If I boot that machine with a physical CD and it works fine.
I get the same result using Manageability Commander Tool and Intel Vpro platform solution manager.
I am trying to deploy the AMT ME software for Lenovo M93p models using SCCM 2012 and the suggested commandline - SetupME.exe -s. It is failing with the general error code 1603. I am able to successfully deploy to Lenovo X1 Gen 2 models. Although, with the X1, the commandline is Setup.exe -s.
Has anyone else successfully deployed the SetupME.exe software? I need this to complete configuration for Out Of Band Management.
Hi!
I work as a sysadmin for my company. Some time ago we decided to switch to Intel NUC systems for our workstations. They're small, affordable and fast. What's there not to like.
We also have an SCCM 2012 R2 in place and for the past few days I've been trying to get vPro/AMT/Out of Band management to work. To no great success I might add.
I followed Microsoft's howto on OoB that can be found here: http://technet.microsoft.com/en-us/library/gg712319.aspx
I was able to setup and configure the the OoB managment point but the provisioning isn't happening.
This is an excerpt from my atmopmgr.log on the SCCM machine.
| >>>>>>>>>>>>>>>Provision task (In Band Provision) begin<<<<<<<<<<<<<<< | 6684 (0x1A1C) |
| Provision target is indicated with SMS resource id. (MachineId = 16777232 W0009.my.company.com) | 6684 (0x1A1C) |
| Found valid basic machine property for machine id = 16777232. | 6684 (0x1A1C) |
| Warning: Currently we don't support mutual auth. Change to TLS server auth mode. | 6684 (0x1A1C) |
| The provision mode for device W0009.my.company.com is 1. | 6684 (0x1A1C) |
| AMT Provision Worker: 1 task(s) are in the pending list. | 7360 (0x1CC0) |
| The IP addresses of the host W0009.my.company.com are 10.1.1.21. | 6684 (0x1A1C) |
| Root hash of provisioning certificate is MYROOTPROVHASH. | 6684 (0x1A1C) |
| Attempting to establish connection with target device using SOAP. | 6684 (0x1A1C) |
| Create provisionHelper with (Hash: MYROOTPROVHELPERHASH) | 6684 (0x1A1C) |
| Set credential on provisionHelper... | 6684 (0x1A1C) |
| Try to use provisioning account to connect target machine 10.1.1.21... | 6684 (0x1A1C) |
| Failed to create SSPI credential with error=0x8009030E by AcquireCredentialsHandle. | 6684 (0x1A1C) |
| Fail to connect and get core version of machine 10.1.1.21 using provisioning account #0. | 6684 (0x1A1C) |
| Try to use default factory account to connect target machine 10.1.1.21... | 6684 (0x1A1C) |
| Failed to create SSPI credential with error=0x8009030E by AcquireCredentialsHandle. | 6684 (0x1A1C) |
| Fail to connect and get core version of machine 10.1.1.21 using default factory account. | 6684 (0x1A1C) |
| Try to use provisioned account (random generated password) to connect target machine 10.1.1.21... | 6684 (0x1A1C) |
| AMT Provision Worker: There are 2 tasks in pending list | 7360 (0x1CC0) |
| AMT Provision Worker: Wait 15 seconds... | 7360 (0x1CC0) |
| Failed to create SSPI credential with error=0x8009030E by AcquireCredentialsHandle. | 6684 (0x1A1C) |
| Fail to connect and get core version of machine 10.1.1.21 using provisioned account (random generated password). | 6684 (0x1A1C) |
| Error: Device internal error. This may be caused by: 1. Incorrect network configuration(DHCP option 6 and 15 required for AMT firmware). 2. Provisioning certificate's root hash is not in AMT firmware's root certificate trust list. 3. Provisioning certificate is not configured with SHA1RSA as signature algorithm or 1024 or 2048 bits as public key length. It might not be able to provision some versions of AMT machine. 4. AMT firmware self signed certificate issue(date zero). 5. AMT firmware is not ready for PKI provisioning. Check network interface is opening and AMT is in PKI mode. 6. Service point is trying to establish connection with wireless IP address of AMT firmware but wireless management has NOT enabled yet. AMT firmware doesn't support provision through wireless connection. (MachineId = 16777232) | 6684 (0x1A1C) |
| Error: Can NOT establish connection with target device. (MachineId = 16777232) | 6684 (0x1A1C) |
| Use FQDN to try again | 6684 (0x1A1C) |
| Root hash of provisioning certificate is MYROOTPROVHASH. | 6684 (0x1A1C) |
| Attempting to establish connection with target device using SOAP. | 6684 (0x1A1C) |
| Create provisionHelper with (Hash: MYROOTPROVHELPERHASH) | 6684 (0x1A1C) |
| Set credential on provisionHelper... | 6684 (0x1A1C) |
| Try to use provisioning account to connect target machine W0009.my.company.com... | 6684 (0x1A1C) |
| Failed to create SSPI credential with error=0x8009030E by AcquireCredentialsHandle. | 6684 (0x1A1C) |
| Fail to connect and get core version of machine W0009.my.company.com using provisioning account #0. | 6684 (0x1A1C) |
| Try to use default factory account to connect target machine W0009.my.company.com... | 6684 (0x1A1C) |
| Failed to create SSPI credential with error=0x8009030E by AcquireCredentialsHandle. | 6684 (0x1A1C) |
| Fail to connect and get core version of machine W0009.my.company.com using default factory account. | 6684 (0x1A1C) |
| Try to use provisioned account (random generated password) to connect target machine W0009.my.company.com... | 6684 (0x1A1C) |
| Failed to create SSPI credential with error=0x8009030E by AcquireCredentialsHandle. | 6684 (0x1A1C) |
| Fail to connect and get core version of machine W0009.my.company.com using provisioned account (random generated password). | 6684 (0x1A1C) |
| Error: Device internal error. This may be caused by: 1. Incorrect network configuration(DHCP option 6 and 15 required for AMT firmware). 2. Provisioning certificate's root hash is not in AMT firmware's root certificate trust list. 3. Provisioning certificate is not configured with SHA1RSA as signature algorithm or 1024 or 2048 bits as public key length. It might not be able to provision some versions of AMT machine. 4. AMT firmware self signed certificate issue(date zero). 5. AMT firmware is not ready for PKI provisioning. Check network interface is opening and AMT is in PKI mode. 6. Service point is trying to establish connection with wireless IP address of AMT firmware but wireless management has NOT enabled yet. AMT firmware doesn't support provision through wireless connection. (MachineId = 16777232) | 6684 (0x1A1C) |
| Error: Can NOT establish connection with target device. (MachineId = 16777232) | 6684 (0x1A1C) |
| CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=13 MUF=0 PCNT=1, P1='W0009.my.company.com' P2='' P3='' P4='' P5='' | 6684 (0x1A1C) |
| CStateMsgReporter::DeliverMessages - Created state message file: D:\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\f4jqjxf1.SMX | 6684 (0x1A1C) |
| >>>>>>>>>>>>>>>Provision task (In Band Provision) end<<<<<<<<<<<<<<< | 6684 (0x1A1C) |
The created AD OU is being filled with <COMPUTERNAME>$iME objects.
The clients are in my normal DHCP scopes and these have options 6 and 15 configured.
I'm using a certificate issued by DigiCert as AMT Provisioning certificate. According to DigiCert their root CA's are in the store. How can I verify this?
The AMT Provisioning certificate was signed using these parameters: Intel(R) AMT SDK Implementation and Reference Guide
This is the first time the machines will be provisioned. I haven't the MEBx before.
I'm fresh out of ideas right now. What can I do to make work?
Any help would be greatly appreciated!
I have multiple client machines(HP DC8100 and DELL 790) with AMT 6.2 and above. I'm getting the following failures when trying to use host based configuration on both the 6.2 and 7.0 firmwares. My command line is \\ti-amt-01\amtconfig\acuconfig.exe /output console /verbose /lowsecurity configamt \\ti-amt-01\amtconfig\amtconfig.xml /decryptionpassword ****
I have also included my unecrypted xml file that I am using to load. I have starred out the password. My guess is that some of the options selected are admin mode only? I need to push this out to a few thousand machines so any help would be great!
2014-02-26 17:20:10: Thread:2724(ERROR) : ACU Configurator , Category: ConnectServer Source: Src\WMIAccess.cpp : ConnectToNamespace Line: 129: A call to this function has failed - (0xc000278b) (Invalid namespace -2147217394)
2014-02-26 17:20:10: Thread:2724(DETAIL) : ACU Configurator , Category: WMI_GetRequiredRealms Source: Src\SBAWMIMethods.cpp : SBAWMIMethods::WMI_GetRequiredRealms Line: 259: A call to this function has failed - (0xc000278b) ((ExecMethod WMI_GetRequiredRealms) Failed to connect to the RCS. Invalid namespace (0xc0002779). )
2014-02-26 17:20:10: Thread:2724(ERROR) : ACU Configurator , Category: ConfigAMT failed Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3279: A call to this function has failed - (0xc000278b) (Connection to the Remote Configuration Service is necessary, but the RCSParameters tag is missing in the profile. (RCSAddress))
2014-02-26 17:20:10: Thread:2724(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3281: ***** END ClientControlConfiguration ******
2014-02-26 17:20:10: Thread:2724(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3387: ***** END ClientControlConfiguration ******
2014-02-26 17:20:10: Thread:2724(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : wmain Line: 1223: ***********Exit with code 68. Details: Invalid parameter was found. (RCSAddress)
Hi there,
I plan toinstall theIntelSCStoolandServices on adifferent server thanourSCCM2012R2Primary Sitedue to performanceproblems.
Theinstructions for theSCCM2012Addonsshowsin section2.6.3.1ofPDF'S the installiation of theOOBService Pointrole. Hereisapparentlyassumedthat the role is installed on the Primary Siteandthe certificate was issuedfor this site Site.
Canitcause problemsif this role isinstalled onthe server thatis not theprimarysiteinour case? OurVerisigncertificate is issuedonlyforthe outsourcedserverandnotforthePrimary Site.
We are using Sccm 2012 R2 and want to implement Oobm. So we followed this guide in our test environment: Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU
Provisioning is working fine on Fujitsu computers with AMT version 7 and 9. But on older hardware with version 5 and 6 there is an error during configuration of the profile.
exit with code 68. Details: invalid parameter was found. (RCSAAddress) is found in the Windows event viewer.
and in the Sccm console AMT Status is Not Supported (version 6) and Detected (version 5).
Version 7 and 9 are having the status Provisioned and the out of the band management console is working.
I have intel DH67CL motherboard. I am planning to purchase home theater system. DH67CL has 1 HDMI port. Can I use this HDMI port as audio input for my home theater? Does this port supports for listening audio?
Hi everyone,
I'm in a project to implement the Out of band Management in SCCM 2012 R2. The client PC's are some kind of HP boxes with Intel AMT version 7.1.
I followed this guide: Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU
The configuration and installation fine but I have problem with the Discovery's.
there is the 4th steps:
"If you now refresh your AMT Collections you will see that the Intel AMT Systems: Not Configured now includes the machines where the Intel AMT Discovery Task Sequence where run."
The TS on my test PC run succesfully but the PC not shows up in the Not Configured collection.
I noticed that the membership rule of this Not Configured collection says: if AMT is supported and the isAMTConfigured parameter is 0 then the client will be member of this collection. My main problem is this isAMTConfigured parameter I think.
If I browse the SCCM Server WMI store I see that this parameter is empty in the test client's hardware inventory data, so HW inventory does not / could not collect this parameter.
If I check the mof file (what I imported) it says the this isAMTConfigured comes from the \root\cimv2\SMS namespace Intel_AMT_ManageabilityInfo_ManagementSettings class. If I browse the WMI store on the client I can't find this class in the \root\cimv2\SMS namespace.
But if I browse the \root\cimv2 namespace (without \SMS in the end) I can see this class and isAMTConfigured parameter appear in the list with the correct value.
I downloaded 1-2 older mof file but it also says that the correct namespace is \root\cimv2\SMS.
Has anybody experienced the same issue? Or anybody integrated succesfully SCCM 2012 R2 with AMT 7?
Please if you have any idea or solution don't hasitate to write down.
Thanks.
Sincerely,
Zsolti.
Hi Guys
what is the Max Hard drive Size I can use in the SS4200-E running Device Software Version: 1.0.8.29352 ?
Hi guys.
I hope someone can enlighten me with this. I've new to this company of mine and is still quite unfamiliar with most of their IT SOPs here. Please mind that I'm also quite new to implementation of Intel AMT/ vpro Recently my manager asked me if I could help him find a solution to the question below:
We have a SCCM system and it used to be able to remotely provision Intel AMT / vPro clients. Our system is running with a internal name(mydomain.local), but as SSL certificates does not allow renewal of internal names anymore, we were unable to do purchase of new certificates.
Does anyone have a solution for this?
Thanks in advance!
Sebas
Environment:
when I run "acuconfig.exe /output console ConfigViaRCSOnly {SCSServer.Domain} {my profile}"
on Some workstations (most) it returns exit code 110 and never shows in the SCS console.
So I am wondering where I start troubleshooting.
Hello,
I am trying to add the SCCM addon for AMT but in resource explorer it says RegKeytoMO_32 on all AMT items. and it seems to be aknown issue. most forums says that it will be solved by having latest the SW, which i have.
any help would be appreciated for pointing me in the right direction.
Info about the addon:
Intel SCS addon: 2.1 for SCCM 2.1.5
Intel SCS: 9.1.2.74
Many thanks in advance,
Per