Wayk now installed and with Ent lic and on wayk den but it connects with black screen?

Hi John

Can you share some more information about the remote machine? It's a VM - does it have "displays" attached, or is it headless? Because you mentioned that Wayk sees 2 screens - presumably by pulling down the "Display" menu on the connecting client you see 2 displays listed - does that not match the actual configuration of the machine?

One thing that immediately springs to mind: is there a disconnected (but not logged off) RDP session on the machine? A disconnected RDP session interrupts remote graphics rendering, hence, when Wayk Now is connected, you see a black screen (see "Known Issues" in the online help for more information). I wonder if TeamViewer could be causing a similar interaction; but let's rule out RDP first...

Thanks and kind regards,

Hi yeah I read that in the kb article myself after posting this about the rdp sessions so I've asked the company owner to check for me. To make sure they all users are logged off so I can try again, as to your other question it's a headless vms so my assumption is that it's still got a session connected either rdp or TV as the company owner desktop would be 3 displays so its got to have a session connected so I'm waiting to here back then I'll post back my findings here. I have it's a pain as there a long way from my home office and I've not got there Sophos Xg firewl in place for vpn yet so wayk now was my only access lol.

T3for your reply and illl post back my findings once I've got the owner to check all users are logged off the vm in question

Just an addition to my reply i know wayk now used to have issues when installed on terminal server setup vms but i was under the understanding the latest offering that was fixed is that right?

So I assume even so there is still some glitch causing there to be these issues with black screens if an RDP session is still active? Is this something thats being actively looked into still as i know TeamViewer never had this issue but its free use on Server OS's is limited to 5min sessions unlike wayk now but im an ent licence holder for wayk now and ive run into this Black screen problem before but this is first time since a very early version so id love if this could be fixed so its not going to conflict with RDP sessions if it so happens sessions are left active its very anoying!

Ok i managed to send a logoff remote command via wayk now which def logged off the active session but now the passwords been reset and its not taking my Windows domain login either very anoying!

yey seems using remote logoff command cleared the active session so its working!

Hello John

First, I am glad that the issue seems to be resolved. I'll run through and try to answer all the points but please don't hesitate to let me know if I miss something or you have a further question.

Earlier versions of Wayk Now shipped a workaround for this issue; however we no longer include it in the installer. Unfortunately it proved to be dangerous as an error or misconfiguration of that component could disable remote desktop services on the machine.

The issue inherently is that Wayk will try to connect to the active session on the remote machine, similar to VNC we try to follow the "physical" session and show what you would see if you were sitting in front of the box. This becomes a problem - as you have seen - if the active login session is a remote one.

The good news is that we currently have a dedicated team working on improving how Wayk Now integrates with Remote Desktop Services. You should expect to see improvements here in the first part of this year.

In general Wayk is not currently well tested with headless systems. On Windows, we use Win32 to enumerate the available display devices and evaluate what we can can capture. A truly headless box will not return any display devices. In this case it sounds like things are working - so it's likely there's a display driver configuring one or more "virtual" displays. I believe both RDP and TeamViewer do this. There are also various hardware dongles that provide this functionality.

When you were trying to connect originally, Wayk would've been trying to attach to the active RDP session (which, as discussed above, lead to a black screen). If the Wayk Now client was running in that session, we consider the session to be "attended" (i.e. you are connecting to an existing user session) and offer SRP authentication as the default (if it is enabled in the options). This allows you to connect using the one-time password shown in the Wayk Now client UI. Once that RDP session was terminated, and with no active login session on the box, the connection now becomes "unattended" and we would only offer SRD authentication. This will accept Windows domain credentials, but the user must be a member of Administrators, Remote Desktop Users, or wayk-users.

So it sounds like things are working now?

We apologise for the confusion and inconvenience. I understand the frustration of trying to connect to the remote machine and hitting a roadblock like that. Hopefully that clarifies things but as I said above, please let me know if you have further questions or feedback.

Thanks and kind regards,