I have a network of mostly version 5 MebX and am using the remotecontrol.exe utility to power the PCs on and off. However, on one Dell model in particular (960) the powerdown command is the equivalent of pulling the plug, so the PC cannot re-cycle it's power as it does during a normal shutdown. Therefore the NIC doesn't stay live so I can't send a powerup command. Is there any way in vPro to send a Windows shutdown command instead of poweroff? Thank you.
↧
Using remotecontrol.exe
↧
AMT configuration pre-os
My company is buying several Dell AIO Optiples 9010 which will be running moka5.We want to configure these with the full AMT features.
How does one configure AMT preos?
↧
↧
Intel MB with core i3, 2gb ddr3 ram, is getting delayed to start. 15mins delay.
Intel MB with core i3, 2gb ddr3 ram, is getting delayed to start. Minimum of 15mins delay. As soon as the power is switched on a light glows in the MBoard but the system doesnt startup while pressing the power button. First the LAN light glows as soon as we press the power button later after 15 to 20 mins if we press the power button then the system starts.
↧
Problems setting up Intel AMT
I am trying to configure Intel AMT for remote KVM access on a SuperMicro MBD-X9SCV-Q-O motherboard with an Intel Core i5-2520M processor, both of which claim to support Intel vPro.
The BIOS provides three settings that seem related to AMT/ME:
- AMT: ENABLE/disable
- Unconfigure AMT/ME: enable/DISABLE
- Set ME to disable Mode: enable/DISABLE
(the capitalized option is the one I have chosen currently, but I've tried going through all combinations with no real difference in resultacu)
I've tried several approaches:
- Enter MEBx tool during POST using Ctrl-P:
The tool does not prompt me for a (new) password, when it opens as I would expect and provides only the following menu structure:
- Intel(R) ME General Settings
- FW Update Settings
- Local FW Update: disabled/ENABLED/password protected
- Set PRTC
- Power Control
- Intel(R) ME ON in Host Sleep States: mobile: on in s0/MOBILE: ON IN S0, ME WAKE IN S4, S4-5 (AC ONLY)
- Idle Timeout: 65535
- FW Update Settings
- Exit
No mention of AMT anywhere or a Supported Features setting.
The version of the tool is "Intel(R) Management Engine BIOS Extension v7.0.0053/Intel(R) ME v7.1.40.1161
- Use the Intel ACU Wizard:
The tool loads correctly and shows the following system information:
Intel(R) AMT State
Intel AMT on this system: Supported
System configuration state: Not configured
Intel(R) AMT Information:
Release: 7.1.40
UUID: 000000000-0000-0000-0000-0025907CEF18
Client Control Mode: Supported
The tool allows me to enter all configuration settings, but when I click "Configure", it fails with this error message:
Failed to complete the Setup operation on this Intel(R) AMT device. Unknown error 1Intel(R) AMT configuration failed. The caller is unauthorized. Valid password for the default admin user not found. Verify the password. AMT Status code - Invalid AMT mode. The SKU version is not supported.
- Attempt to provision the server form a USB drive:
If I boot with the USB stick inserted, the MEBx tool prompts me with "Found USB Key for provisioning. Continue with Auto Provisioning (Y/N)?"
If I answer "Y", it displays the following error message:
Intel(R) AMT is disabled and USB data missing Manageability Feature Selection
Network and provisioning settings will not be applied.
Configuration Settings from the USB file were successfully applied
Press any key to continue with system boot...
Any ideas what I might be missing?
↧
Vpro on intranet FQDN
You know - luckyregister.com/support/article.php?aid=6935&locale=en
So how can i use vpro in intranet if i have FQDN of sccm like this sccm.moscow.mycompany.holding? Godaddy (or others) can't give me cert on this fqdn.
↧
↧
KVM and Active Directory
Is there posibility to use Active Directory authentication to access to KVM?
↧
Ways of getting Admin Control Mode.
After reading info and documentation it seems to me that these are the ways of setting a remote computer in "Admin Control Mode":
- Going phisically and make a "ctrl-p" bios setup.
- Purchasing a valid certificate and configure remotely via RC server
- Sending a usb key with PID-PPS pair and then configure remotely
It's that correct? are there any other methods?
Thank you!
↧
Understanding ME's role on systems that do not implement MEBx
Greetings.
What purpose does Intel AMT stuff serve, imbedded into system BIOSes, when the OEM decides not to fully implement? Why do they bother putting ME firmware on their chips at all? Why do they bother offering updated drivers and sometimes updated ME versions via a BIOS upgrade?
I was initially curious about two Asus and MicroStar based systems I had to work on, but in researching this, apparently there are plenty of vendors who decide to not provide the MEBx interface. There is no MEBx header upon booting, no Ctrl-P works, and trying to access tcp/19662 gets no response. I have no idea why they decide to not implement the MEBx interface, when they integrate ME into their system BIOS packages, and continue to provide updates to both the drivers and firmware! I have gotten half-assed answers from both vendors, so I decided to come here and ask.
Again, I am confused beyond the ability to ask a questions correctly. Please bear with my rambling.
Since in modern EFI BIOS setups allocated on your common 8Mbit SPI Flash ICs, this is all very structured. A block for the system BIOS, a block for the GbE firmware, and so forth. And a specific address range associated with ME firmware. I have flashed different versions into a running system BIOS by only flashing that range, probably the same way the proper Intel FWUpdLcl utility works. If I run MeInfoWin, it identifies the version I just flashed, and my system still operates correctly. (Granted, this is an OEM BIOS with that region extracted from the firmware BIN, not directly using an Intel ME firmware update image.)
I want to see if, without any assistance or approval from the vendor, if we can enable MEBx. I'm sure ME is already there. There's probably a single byte toggle or something equally easy to enable access. But I could be wrong, the vendors are only flashing it onto their BIOS chips because it's required due to chipset licensing and only enabling the parts necessary for compliance, and none of the code to hook to the hardware devices is there.
Also I understand Intel's position on information disclosure, so if this is something we don't discuss in public, please say so. Besides, reading compiled machine code isn't as difficult as it used to be. Although in paging through the ME firmware hex, I see embedded x86 executable code. No decoding necessary. I'll guess it's the html server and the various configuration utilities that a fully-deployed and activated MEBx uses. And that's my point. The firmware is there. I want to enable it. Why won't said vendor(s) enable it? Choice? Cost? Complexity? Customers? I really want to know.
Sidenote: in trying to research this, I found many, many posts by people that think AMT is bad/evil/wrong. Really?
I'm sure I just scared all the conspiracists: "He wants to voluntarily activate the Intel spyware!!? Is he crazy?!"
Yes. So thanks for reading the ramblings of a crazy person.
And thanks in advance for any illumination provided... it's dark over here.
↧
Difference between provisioning AMT computers with SCCM 2012 or Intel SCS?
Hi all
I have just started looking into using Intel vPro with our SCCM infrastructure and wondering about what the difference is between provisioning AMT computers with SCCM 2012 or Intel SCS?
Which is best? Which is simplest? Are there any benefits with choosing one over the other? Which is best supported?
/B
↧
↧
Intel Active Management Technology (AMT) requirements
Looking to build a system I can remotely power cycle.
Intel AMT seems to be the thing I need to this, which requires a VPRO-enabled cpu and a Q87 chipset.
Does it also require any else on the mobo or is that sufficient? ie are all systems with a vpro cpu and a q87 chipset enabled for AMT? The manuals and spec sheets I'm seeing for Q87 boards are very non-specific about this, Asus, for example saying about their Q87M board bios settings:
iAMT H/W is always enabled. This option just controls the BIOS extension execution. If
enabled, this requires additional firmware in the SPI device.
As, as far as I can tell, the SPI device is the q87 itself, this seems out of place.
↧
Using remotecontrol.exe
I have a network of mostly version 5 MebX and am using the remotecontrol.exe utility to power the PCs on and off. However, on one Dell model in particular (960) the powerdown command is the equivalent of pulling the plug, so the PC cannot re-cycle it's power as it does during a normal shutdown. Therefore the NIC doesn't stay live so I can't send a powerup command. Is there any way in vPro to send a Windows shutdown command instead of poweroff? Thank you.
↧
AMT configuration pre-os
My company is buying several Dell AIO Optiples 9010 which will be running moka5.We want to configure these with the full AMT features.
How does one configure AMT preos?
↧
Intel MB with core i3, 2gb ddr3 ram, is getting delayed to start. 15mins delay.
Intel MB with core i3, 2gb ddr3 ram, is getting delayed to start. Minimum of 15mins delay. As soon as the power is switched on a light glows in the MBoard but the system doesnt startup while pressing the power button. First the LAN light glows as soon as we press the power button later after 15 to 20 mins if we press the power button then the system starts.
↧
↧
Problems setting up Intel AMT
I am trying to configure Intel AMT for remote KVM access on a SuperMicro MBD-X9SCV-Q-O motherboard with an Intel Core i5-2520M processor, both of which claim to support Intel vPro.
The BIOS provides three settings that seem related to AMT/ME:
- AMT: ENABLE/disable
- Unconfigure AMT/ME: enable/DISABLE
- Set ME to disable Mode: enable/DISABLE
(the capitalized option is the one I have chosen currently, but I've tried going through all combinations with no real difference in resultacu)
I've tried several approaches:
- Enter MEBx tool during POST using Ctrl-P:
The tool does not prompt me for a (new) password, when it opens as I would expect and provides only the following menu structure:
- Intel(R) ME General Settings
- FW Update Settings
- Local FW Update: disabled/ENABLED/password protected
- Set PRTC
- Power Control
- Intel(R) ME ON in Host Sleep States: mobile: on in s0/MOBILE: ON IN S0, ME WAKE IN S4, S4-5 (AC ONLY)
- Idle Timeout: 65535
- FW Update Settings
- Exit
No mention of AMT anywhere or a Supported Features setting.
The version of the tool is "Intel(R) Management Engine BIOS Extension v7.0.0053/Intel(R) ME v7.1.40.1161
- Use the Intel ACU Wizard:
The tool loads correctly and shows the following system information:
Intel(R) AMT State
Intel AMT on this system: Supported
System configuration state: Not configured
Intel(R) AMT Information:
Release: 7.1.40
UUID: 000000000-0000-0000-0000-0025907CEF18
Client Control Mode: Supported
The tool allows me to enter all configuration settings, but when I click "Configure", it fails with this error message:
Failed to complete the Setup operation on this Intel(R) AMT device. Unknown error 1Intel(R) AMT configuration failed. The caller is unauthorized. Valid password for the default admin user not found. Verify the password. AMT Status code - Invalid AMT mode. The SKU version is not supported.
- Attempt to provision the server form a USB drive:
If I boot with the USB stick inserted, the MEBx tool prompts me with "Found USB Key for provisioning. Continue with Auto Provisioning (Y/N)?"
If I answer "Y", it displays the following error message:
Intel(R) AMT is disabled and USB data missing Manageability Feature Selection
Network and provisioning settings will not be applied.
Configuration Settings from the USB file were successfully applied
Press any key to continue with system boot...
Any ideas what I might be missing?
↧
Vpro on intranet FQDN
You know - luckyregister.com/support/article.php?aid=6935&locale=en
So how can i use vpro in intranet if i have FQDN of sccm like this sccm.moscow.mycompany.holding? Godaddy (or others) can't give me cert on this fqdn.
↧
KVM and Active Directory
Is there posibility to use Active Directory authentication to access to KVM?
↧
Ways of getting Admin Control Mode.
After reading info and documentation it seems to me that these are the ways of setting a remote computer in "Admin Control Mode":
- Going phisically and make a "ctrl-p" bios setup.
- Purchasing a valid certificate and configure remotely via RC server
- Sending a usb key with PID-PPS pair and then configure remotely
It's that correct? are there any other methods?
Thank you!
↧
↧
Understanding ME's role on systems that do not implement MEBx
Greetings.
What purpose does Intel AMT stuff serve, imbedded into system BIOSes, when the OEM decides not to fully implement? Why do they bother putting ME firmware on their chips at all? Why do they bother offering updated drivers and sometimes updated ME versions via a BIOS upgrade?
I was initially curious about two Asus and MicroStar based systems I had to work on, but in researching this, apparently there are plenty of vendors who decide to not provide the MEBx interface. There is no MEBx header upon booting, no Ctrl-P works, and trying to access tcp/19662 gets no response. I have no idea why they decide to not implement the MEBx interface, when they integrate ME into their system BIOS packages, and continue to provide updates to both the drivers and firmware! I have gotten half-assed answers from both vendors, so I decided to come here and ask.
Again, I am confused beyond the ability to ask a questions correctly. Please bear with my rambling.
Since in modern EFI BIOS setups allocated on your common 8Mbit SPI Flash ICs, this is all very structured. A block for the system BIOS, a block for the GbE firmware, and so forth. And a specific address range associated with ME firmware. I have flashed different versions into a running system BIOS by only flashing that range, probably the same way the proper Intel FWUpdLcl utility works. If I run MeInfoWin, it identifies the version I just flashed, and my system still operates correctly. (Granted, this is an OEM BIOS with that region extracted from the firmware BIN, not directly using an Intel ME firmware update image.)
I want to see if, without any assistance or approval from the vendor, if we can enable MEBx. I'm sure ME is already there. There's probably a single byte toggle or something equally easy to enable access. But I could be wrong, the vendors are only flashing it onto their BIOS chips because it's required due to chipset licensing and only enabling the parts necessary for compliance, and none of the code to hook to the hardware devices is there.
Also I understand Intel's position on information disclosure, so if this is something we don't discuss in public, please say so. Besides, reading compiled machine code isn't as difficult as it used to be. Although in paging through the ME firmware hex, I see embedded x86 executable code. No decoding necessary. I'll guess it's the html server and the various configuration utilities that a fully-deployed and activated MEBx uses. And that's my point. The firmware is there. I want to enable it. Why won't said vendor(s) enable it? Choice? Cost? Complexity? Customers? I really want to know.
Sidenote: in trying to research this, I found many, many posts by people that think AMT is bad/evil/wrong. Really?
I'm sure I just scared all the conspiracists: "He wants to voluntarily activate the Intel spyware!!? Is he crazy?!"
Yes. So thanks for reading the ramblings of a crazy person.
And thanks in advance for any illumination provided... it's dark over here.
↧
Difference between provisioning AMT computers with SCCM 2012 or Intel SCS?
Hi all
I have just started looking into using Intel vPro with our SCCM infrastructure and wondering about what the difference is between provisioning AMT computers with SCCM 2012 or Intel SCS?
Which is best? Which is simplest? Are there any benefits with choosing one over the other? Which is best supported?
/B
↧
Intel Active Management Technology (AMT) requirements
Looking to build a system I can remotely power cycle.
Intel AMT seems to be the thing I need to this, which requires a VPRO-enabled cpu and a Q87 chipset.
Does it also require any else on the mobo or is that sufficient? ie are all systems with a vpro cpu and a q87 chipset enabled for AMT? The manuals and spec sheets I'm seeing for Q87 boards are very non-specific about this, Asus, for example saying about their Q87M board bios settings:
iAMT H/W is always enabled. This option just controls the BIOS extension execution. If
enabled, this requires additional firmware in the SPI device.
As, as far as I can tell, the SPI device is the q87 itself, this seems out of place.
↧