WTware Technical Support

Sorry, seems we lost logs. Please, send us logs again

Wifi disconnects every one-two minutes. It is a problem.

In "tsclient-main.cpp ( 162)" terminal can not send keyboard event (key pressed or key released) because there are too many events already in queue and network connection doesn't work. Keyboard event dropped.

Try to save log immediatelly after boot. I want to see first messages, when error appears.

Does the same user on the same server disconnect in mstsc and doesn't disconnect in wtware?
Show me the log, please: https://wtware.ru/logs.html
3+ hours, boot without mouse.
Perhaps, it's easily to reproduce on separate server with timeout for several minutes instead of 3 hours.

Full log please.

Try to disconnect mouse and repeat test.

kevin.murilo wrote: ↑Thu Aug 06, 2020 5:21 pm I'm only running a single 2GB DDR3 stick on each machine, since WTware requires very little space. My question is, if I put a second stick os RAM on each system, would it be more responsive?

It will be more responsive if you run local Chromium. For RDP sessions 1GB is more than enough.

Since Network Boot is not too reliable, Just mark: on Raspberry is not too reliable. On x86, in safe network, it's reliable. ...if you could choose this saved setting on the first page of the dialog and than just click write on SD-Card. "settings" is in configs/initrd.wtc on SD. There is ...

Host and comment fields can be edited on DHCP tab for the terminal. It's not obvious solution, but it happend historically.

No, we see no future with Pi Zero.

Install wtware distributive on a new server. All significant data - terminals configurations, connections, templates, etc. - is stored in (by default) C:\ProgramData\WTware\
You can copy needed files to a new server into the same directory.

There is nothing to view on cl.wtware.com. Licensing site addresses were in email with password.

Configurator is installed by default.

1. Open in configurator DHCP service log and clear it.
2. Turn off this terminal.
3. Change terminal IP in configurator.
4. Turn on terminal.
If terminal IP won't change, send me to support@wtware.com DHCP log.