Headless Access: Difference between revisions
Jump to navigation
Jump to search
openhomelab>Chris (Doing some Categorisation) |
(→vPro) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 31: | Line 31: | ||
=== vPro === | === vPro === | ||
This is similar to IPMI, but for desktops. https://www.meshcommander.com/meshcommander | |||
Latest revision as of 01:40, 9 February 2021
This article is a stub. You can help The Open Homelab project by expanding it. For information on external remote access see the Remote Access article.
Introduction[edit | edit source]
Use Cases[edit | edit source]
The use cases for headless access to your homelab include:
- A
- B
- C
- Servers are in a remote part of the house, e.g. Loft, Garage, Shed, etc
- Servers are actually in a colocation facility at a datacentre (yes it sounds expensive, but some people do actually do this!)
- You are a millionaire and have a whole DC full of your homelab kit! (Ok, maybe going a bit far now...)
Solutions[edit | edit source]
Some example solutions to provide remote access to your screen are as follows:
iLO[edit | edit source]
X
iDRAC[edit | edit source]
Y
KVM[edit | edit source]
If you start off with a small homelab with a handful of servers you may have the ability to connect them all up to a single management keyboard, mouse and screen.
KVM over IP / Remote KVM[edit | edit source]
When you want to take the KVM concept a step further it is actually possible to connect up to a KVM switch with remote IP connectivity, though they aren't cheap!
vPro[edit | edit source]
This is similar to IPMI, but for desktops. https://www.meshcommander.com/meshcommander