Customer Premises Out of Band Management Platform Ideas
-
@scottalanmiller said:
If you install Xen you get hit with VDI licensing requirements for Windows desktops, though. If you use Windows desktop as the "base" OS and install the HyperV role it bypasses that while still virtualizing everything. It's not ideal, but it saves a lot of money. Really odd that MS does that, but hey, it's pretty minor overall. That way we can have both Windows and Linux on the box at the same time.
I realize that XP is EOL - but would it remove the VDI licensing issue?
-
@scottalanmiller said:
@g.jacobse said:
I don't think a Pi will function in that regard.... Sadly one of the first devices I can think of is a Laptop. I have several here that would allow for a SIM,.. so bypasses the WAN.
Raspberry Pi can't run Windows, so that's a big limitation. Laptops are too fragile. That was suggested but it's hard to imagine customers not messing with a laptop that is sitting there.
Agreed. It was the first thing I thought of having a SIM - I have not looked for / at other cellular devices - or cellular embedded devices.
-
@g.jacobse said:
@scottalanmiller said:
If you install Xen you get hit with VDI licensing requirements for Windows desktops, though. If you use Windows desktop as the "base" OS and install the HyperV role it bypasses that while still virtualizing everything. It's not ideal, but it saves a lot of money. Really odd that MS does that, but hey, it's pretty minor overall. That way we can have both Windows and Linux on the box at the same time.
I realize that XP is EOL - but would it remove the VDI licensing issue?
No, XP isn't licensed for that use at all.
-
AirCard from AT&T / Verizon / T-Mobile?
-
That or something like it. Simple and reliable is what we need.
-
Branding the device is a great idea. It's a good opportunity to remind everyone who is managing things. And it would make identifying the device that much easier.
-
A commercial device would mean easier to find parts too. Fewer issues should something fail.
-
@scottalanmiller said:
If you install Xen you get hit with VDI licensing requirements for Windows desktops, though. If you use Windows desktop as the "base" OS and install the HyperV role it bypasses that while still virtualizing everything. It's not ideal, but it saves a lot of money. Really odd that MS does that, but hey, it's pretty minor overall. That way we can have both Windows and Linux on the box at the same time.
Does this apply to Windows Server too or just the desktop OS? Although I can see why you would want a desktop OS with cost alone being an issue.
-
VDI is a desktop only thing. VDI = virtual "desktop" infrastructure. While you can sort of make desktops out of server OSes and call it VDI, sort of, because it acts that way, the entire idea of VDI exists only for the Windows desktop licensing world. There is no VDI licensing for servers.
-
@scottalanmiller said:
VDI is a desktop only thing. VDI = virtual "desktop" infrastructure. While you can sort of make desktops out of server OSes and call it VDI, sort of, because it acts that way, the entire idea of VDI exists only for the Windows desktop licensing world. There is no VDI licensing for servers.
That is what I assumed but your previous remark made me second guess it. Thanks for the clarification.
-
I checked with a fellow IT'er and Engineer and he doesn't know if a Desktop that has a Cellular option. So anything you 'add' with be 3rd party.
(ETA) At least As Far As I know....
