Thin client from Raspberry Pi 2

[aka]

Hello!
I'd like to introduce my project, that refers to this theme - networking and servers.
WTware for Raspberry Pi 2 is free thin clients operating system, that creates connections to Windows Remote Desktop Services. Raspberry Pi 2 with installed WTware displays Windows Desktop and Windows applications, that are running on Windows Terminal Server, like usual office x86 computer with mstsc.exe

For more details read http://winterminal.com/

[fruitoftheloom]

Hello!
I'd like to introduce my project, that refers to this theme - networking and servers.
WTware for Raspberry Pi 2 is free thin clients operating system, that creates connections to Windows Remote Desktop Services. Raspberry Pi 2 with installed WTware displays Windows Desktop and Windows applications, that are running on Windows Terminal Server, like usual office x86 computer with mstsc.exe

For more details read http://winterminal.com/

Personally I do not like the use of "Network Boot" as it does not do so however you frame it, the RPi must be booted up to a Kernel stored on a SD Card, that is not made clear afaiac...

Apart from that it appears a nicely packaged RDP Product

[aka]

In WTware we do make true network boot. Kernel boots from TFTP.
Here are more details: viewtopic.php?f=29&t=109292

[hansotten]

Hello!
I'd like to introduce my project, that refers to this theme - networking and servers.
WTware for Raspberry Pi 2 is free thin clients operating system, that creates connections to Windows Remote Desktop Services. Raspberry Pi 2 with installed WTware displays Windows Desktop and Windows applications, that are running on Windows Terminal Server, like usual office x86 computer with mstsc.exe

For more details read http://winterminal.com/

Personally I do not like the use of "Network Boot" as it does not do so however you frame it, the RPi must be booted up to a Kernel stored on a SD Card, that is not made clear afaiac...

Apart from that it appears a nicely packaged RDP Product

On their website frontpage it is written:

WTware for Raspberry Pi 2 can boot from local SD-card or by network. In both cases you need microSD card. Even for network boot microSD is still needed: there's no flash with BIOS on board, and code, that will load boot images by network, is stored on microSD.

And further on they describe how to flash the SD card.

That is quite clear for me!

Network booted thin client has many advantages in a larger environment, no local images to update, all centrally maintained, fast deployment etc.

[fruitoftheloom]

In WTware we do make true network boot. Kernel boots from TFTP.
Here are more details: viewtopic.php?f=29&t=109292

So you are stating that if the RPi is shutdown and the power lead is still plugged in you can then fire it up with no user intervention ???

[aka]

So you are stating that if the RPi is shutdown and the power lead is still plugged in you can then fire it up with no user intervention ???

No, RPi doesn't support Wake-on-LAN.

[fruitoftheloom]

So you are stating that if the RPi is shutdown and the power lead is still plugged in you can then fire it up with no user intervention ???

No, RPi doesn't support Wake-on-LAN.

Yes no PXE support therefore it is not Network Booting.

You are still booting the RPi to an initial U-Boot which is booting the ""kernel"" wherever that is stored

Das U-Boot (Universal Bootloader) is an open source, primary boot loader used in embedded devices to package the instructions to boot the device's operating system kernel.

https://en.wikipedia.org/wiki/Das_U-Boot

https://en.wikipedia.org/wiki/Network_booting

The word of the day is SEMANTICS


So if I am in an office I have to go to the RPi and actually apply power. Really great exercise for a Sys Admin

Looks like will need to setup a PoE to each RPi 2B

[aka]

From your wikipedia link about Network boot:

Process
The initial software to be run is loaded from a server on the network; for IP networks this is usually done using the Trivial File Transfer Protocol. The server from which to load the initial software is usually found by broadcasting a Bootstrap Protocol or Dynamic Host Configuration Protocol request.

That is exactly as WTware on RPi does.

[fruitoftheloom]

From your wikipedia link about Network boot:

Process
The initial software to be run is loaded from a server on the network; for IP networks this is usually done using the Trivial File Transfer Protocol. The server from which to load the initial software is usually found by broadcasting a Bootstrap Protocol or Dynamic Host Configuration Protocol request.

That is exactly as WTware on RPi does.

I am au-fait, but other perusers of this forum may not be, my point is to a general user Network Boot will convey the same as PXE.

It should be made clear that the RPi 2B should physically have power supplied in CAPITALS, not everyone who will try your RDP Solution will be "technically aware"

[hansotten]

So you are stating that if the RPi is shutdown and the power lead is still plugged in you can then fire it up with no user intervention ???

No, RPi doesn't support Wake-on-LAN.

Yes no PXE support therefore it is not Network Booting.

https://en.wikipedia.org/wiki/Network_booting

Nonsense. It is a Workstation solution running RDP, so there will be a user behind to turn it on and off. And turning on and off is not a very technical challenging exercise ... its the number one advise from helpdesks

Whether the network boot code is stored in ROM with an PXE capable adapter, or stored on an SD card, it is network booting.

[fruitoftheloom]

Nonsense. It is a Workstation solution running RDP, so there will be a user behind to turn it on and off. And turning on and off is not a very technical challenging exercise ... its the number one advise from helpdesks

Whether the network boot code is stored in ROM with an PXE capable adapter, or stored on an SD card, it is network booting.

Many offices hide the PC so end users can not switch on/off, they rely on PXE

[jpxdude]

Just tried winterminal, and I'm thoroughly impressed! Looking very forward to see how this develops going forward.

-J

[lctronico]

Hello everyone,

I am a new guy in this world of WTWare with Pi 2. Can you guys guide me how to set up my device in order to use the USB WIfi.

Thanks.

[aka]

At first, download new WTware version and rewrite SD card. At the very beginning of boot press Del to Enter Setup. In text menu change network to Wifi and specify your Wifi settings. It should work. If any problems, please, contact me support@wtware.com

[aka]

As our users say WTware works on Pi 3 now. Only WiFi is not working yet. We'll make it work as soon as we receive our Pi 3. So our project becomes https://winterminal.com WTware for Pi 2-3

[hansotten]

As our users say WTware works on Pi 3 now. Only WiFi is not working yet. We'll make it work as soon as we receive our Pi 3. So our project becomes https://winterminal.com WTware for Pi 2-3

Good work!

Since PXE is is coming for the Pi 3 (wait is for software, the hardware can do it), this will be a complete thin client even satisfying the biggest nickpicker