HowTo Headless Intel NUC vPro AMT - Revision history

Rwh: /* WS Management Command Line Interface */

2020-06-14T18:23:06Z

WS Management Command Line Interface

← Older revision		Revision as of 14:23, 14 June 2020
Line 270:		Line 270:
	</a:Envelope>		</a:Envelope>
	[pkb@refritos ~]$		[pkb@refritos ~]$

			==Intel vPro Wireless Support==
			Intel vPro devices (version 2.5 and later) with wireless capabilities can be managed out-of-band via a wireless LAN connection when they are powered on and the wireless interface is active. If a notebook is in sleep mode, it can be managed out-of-band only if it is connected to a wired LAN and to AC power.

			When the notebook is powered up, the Intel Active Management Technology (Intel AMT) chip on the notebook communicates with the wireless LAN driver. If Intel AMT finds a matching profile, the driver will route traffic addressed to the Intel AMT device. Even if there is a problem with the driver, Intel AMT can receive out-of-band management traffic from the wireless network interface.

			For wireless management, Intel vPro uses the device's Windows wireless profile.

			For Intel AMT to work with a wireless LAN connection, it must share IP addresses with the notebook. To do this, Intel AMT must be configured to use DHCP and there must be a DHCP server available to allocate IP addresses. If Intel AMT is configured to use static IP addresses, wireless connectivity will be disabled.

			When a notebook has been discovered and provisioned while connected to a wired network, it can be managed through the wired network immediately. However, when the notebook switches to a wireless connection there can be a delay before Intel vPro management is enabled for the notebook. This is due to a change in how the computer name is resolved in DNS on the network. The wireless IP address for the notebook is different than the IP address on the wired network, so there is a delay before the new IP address for the notebook matches the computer name.

Rwh: /* Linux / maxOS / Windows Tools */

2019-09-15T12:07:24Z

Linux / maxOS / Windows Tools

← Older revision		Revision as of 08:07, 15 September 2019
Line 189:		Line 189:
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).
	* Using the web interface, you add and manage Intel AMT systems on your LAN to the '''meshcommander''' web interface.		* Using the web interface, you add and manage Intel AMT systems on your LAN to the '''meshcommander''' web interface.

			'''Note''': On a Windows platform one can install MeshCommander using the MSI installer.

	Once a system has been successfully added and configured, you can bring up an out of band serial or remote desktop (VNC) to each managed system.		Once a system has been successfully added and configured, you can bring up an out of band serial or remote desktop (VNC) to each managed system.

Rwh: /* Linux Tools */

2019-09-15T12:01:51Z

Linux Tools

← Older revision		Revision as of 08:01, 15 September 2019
Line 168:		Line 168:
	Running '''gnome-disks''' to benchmark the disk read speed showed that the Samsung 970 EVO NVME SSD was operating at about half speed. While the access times looked good, the transfer rates looked slow (at least compared to what you would expect form the 970 EVO). After a bit of ''googling'' it looks like this is a known issue with this combination (see: https://communities.intel.com/thread/126725). Hopefully there will be a BIOS update that will address this in the near future.		Running '''gnome-disks''' to benchmark the disk read speed showed that the Samsung 970 EVO NVME SSD was operating at about half speed. While the access times looked good, the transfer rates looked slow (at least compared to what you would expect form the 970 EVO). After a bit of ''googling'' it looks like this is a known issue with this combination (see: https://communities.intel.com/thread/126725). Hopefully there will be a BIOS update that will address this in the near future.

	== Linux Tools ==		== Linux / maxOS / Windows Tools ==

	=== MeshCommander ===		=== MeshCommander ===

Rwh: /* MeshCommander */

2019-09-15T12:00:29Z

MeshCommander

← Older revision		Revision as of 08:00, 15 September 2019
Line 175:		Line 175:

	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.
	** On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.		** On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''
	* You ''npm install'' the '''meshcommander''' package.		* You ''npm install'' the '''meshcommander''' package.
	** On '''NST''' run: ''dnf install meshcommander''.		** On '''NST''' run: ''dnf install meshcommander''
	**On macOS running '''~~[https://en.wikipedia.org/wiki/Homebrew_(package_management_software)~~ Homebrew]''' run: ''npm install meshcommander''.		** On macOS running '''Homebrew''' run:
			*** First create a new directory: ''mkdir -p meshcommander''
			*** Go to the newly created directory: ''cd meshcommander''
			*** Next install: ''npm install meshcommander''
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.
			** On '''NST''' run: ''systemctl start meshcommander.service''
			** On macOS running '''Homebrew''':
			*** Go to directory: ''cd node_modules/meshcommander/''
			*** Start meshcommander using '''node''': node ./meshcommander.js
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).
	* Using the web interface, you add and manage Intel AMT systems on your LAN to the '''meshcommander''' web interface.		* Using the web interface, you add and manage Intel AMT systems on your LAN to the '''meshcommander''' web interface.

Rwh: /* MeshCommander */

2019-09-15T11:49:51Z

MeshCommander

← Older revision		Revision as of 07:49, 15 September 2019
Line 176:		Line 176:
	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.
	** On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.		** On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.
	* You ''npm install'' the '''meshcommander''' package. On '''NST''' run: ''dnf install meshcommander''. ~~One~~ macOS running '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' run: ''npm install meshcommander''.		* You ''npm install'' the '''meshcommander''' package.
			** On '''NST''' run: ''dnf install meshcommander''.
			**On macOS running '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' run: ''npm install meshcommander''.
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).

Rwh: /* MeshCommander */

2019-09-15T11:48:30Z

MeshCommander

← Older revision		Revision as of 07:48, 15 September 2019
Line 174:		Line 174:
	The ''MeshCommander'' project (see: http://www.meshcommander.com/meshcommander) provides an incredible tool for working with Intel vPro AMT systems on your network. It works as follows:		The ''MeshCommander'' project (see: http://www.meshcommander.com/meshcommander) provides an incredible tool for working with Intel vPro AMT systems on your network. It works as follows:

	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager. On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.
			** On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.
	* You ''npm install'' the '''meshcommander''' package. On '''NST''' run: ''dnf install meshcommander''. One macOS running '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' run: ''npm install meshcommander''.		* You ''npm install'' the '''meshcommander''' package. On '''NST''' run: ''dnf install meshcommander''. One macOS running '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' run: ''npm install meshcommander''.
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.

Rwh: /* MeshCommander */

2019-09-15T11:46:13Z

MeshCommander

← Older revision		Revision as of 07:46, 15 September 2019
Line 175:		Line 175:

	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager. On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager. On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.
	* You ''npm install'' the '''meshcommander''' package.		* You ''npm install'' the '''meshcommander''' package. On '''NST''' run: ''dnf install meshcommander''. One macOS running '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' run: ''npm install meshcommander''.
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).

Rwh: /* MeshCommander */

2019-09-15T11:31:22Z

MeshCommander

← Older revision		Revision as of 07:31, 15 September 2019
Line 174:		Line 174:
	The ''MeshCommander'' project (see: http://www.meshcommander.com/meshcommander) provides an incredible tool for working with Intel vPro AMT systems on your network. It works as follows:		The ''MeshCommander'' project (see: http://www.meshcommander.com/meshcommander) provides an incredible tool for working with Intel vPro AMT systems on your network. It works as follows:

	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager. On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.
	* You ''npm install'' the '''meshcommander''' package.		* You ''npm install'' the '''meshcommander''' package.
	* On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).

Rwh: /* MeshCommander */

2019-09-15T11:30:31Z

MeshCommander

← Older revision		Revision as of 07:30, 15 September 2019
Line 176:		Line 176:
	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.
	* You ''npm install'' the '''meshcommander''' package.		* You ''npm install'' the '''meshcommander''' package.
	* On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm'''.		* On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm''.
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).

Rwh: /* MeshCommander */

2019-09-15T11:28:14Z

MeshCommander

← Older revision		Revision as of 07:28, 15 September 2019
Line 176:		Line 176:
	* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.		* You install the '''npm''' and '''nodejs''' package for your platform on the system that will act as the central manager.
	* You ''npm install'' the '''meshcommander''' package.		* You ''npm install'' the '''meshcommander''' package.
	* On macOS one can use brew		* On macOS one can use '''[https://en.wikipedia.org/wiki/Homebrew_(package_management_software) Homebrew]''' and the on a command line run: ''brew install npm'''.
	* You start the '''meshcommander''' server.		* You start the '''meshcommander''' server.
	* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).		* You point your browser at http://127.0.0.1:3000/ (or alternate IPv4 address if you enabled the ''--any'' option).