Users

All Posts (39)

avatar

ppp3

CTL-ALT-DEL on server core freezes at logonui.exe, requires disconnect / reconnect to use

avatar
avatar
avatar

The news letter indicated that WaykNow 3.0 was RTM, is this the case and should we switch over to the release version & validate it?

CTL-ALT-DEL on server core freezes at logonui.exe, requires disconnect / reconnect to use

avatar
avatar
avatar

The new Beta (8) does fixxthe screen crash on MacOS when connecting however on Server Core after the CTL-ALT-DEL is issues & password provided the session freezes up rather than crashing. Discponnect & Reconnect are required to see that you have logged in and the session is accessible.

Client crashes on MacOS Mojave after sending C TL-ALT-DEL

avatar
avatar
avatar
avatar

The sequence does go through and core prompts for the password, as soon as the PW is provided WaykNow client crashes.

Crash report is attached.

CTL-ALT-DEL does not work on Server Core

avatar
avatar
avatar

It works and install/ upgrade was painless! Well Done

Remote access to Server Core does not work

avatar
avatar
avatar
avatar
avatar

Here's the exported session

Remote access to Server Core does not work

avatar
avatar
avatar
avatar
avatar

CTL-ALT-DEL does not work on Server Core

avatar
avatar
avatar

Tried copying it over and yes it worked, also crashed Wayknow client on my Mac as soon as it logged in.

I figure it this way. If TeamViewer & Royal TSX can do it without the sas.dll then you can too and I'll just need to be content & wait rather than dump .dll's on my hyper-v hosts that may/may not have aotherside effects.

Remote access to Server Core does not work

avatar
avatar
avatar
avatar
avatar

I'm on a Mac and I'm sorry but I don't see any option to change any of the types or add/remove any plugins or engines as there is on the Windows version.

Add options to MSI command line to facilitate remote installation or installation on server core

avatar
avatar
avatar

Is it possible to edit a global .cfg file and push it into the installation folder immediately after the install to have it take effect on the reboot?

Also, as we've discovered, unless the reboot is immediate there may be problems with the TLS services, so could this file be pushed into place first and would the install keep it, or overwrite it?

Remote access to Server Core does not work

avatar
avatar
avatar
avatar
avatar

It flashes up quickly & goes away "Graphics mode not supported".

Happens regardless of mode, does not happen with competitor's products that utilize free RDP

The WaykNow team has a server core test bed yo may want to try it against.

CTL-ALT-DEL does not work on Server Core

avatar
avatar
avatar

Yah Server Core is an animal unto it's own genus but one that's going to be extremely prevalent in the IT forest quickly.

Bottom line is it requires considerably less maintenance & patching than the GUI version, it runs faster & uses considerably less resources so it handles it's assigned roles better, & it's the only flavor that M$ will be supplying that does not have an end-of-life built into it.

FWIW VNC doesn't work with it either, probably for the same reasons. It's also causing issues with Remote Desktop Manager's RDP implementation with a "graphics mode not supported" error.

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

Please do me a favor and keep a server 2016 Core test server up and also you may consider a server 2019 test bed of both Core & GUI

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

The registry for lsmproxy can't be written to while the server is runniing :(

Looks like I need to use the same steps I did on the other server to recover

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

Well some good news at least.

Install Beta 5 complete, reboot, remove RDS but choose the option that will require reboot by not stopping the services, reboot manually with restart-computer in PoSh and RDP is once again working.

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

I may have lucked out. Installing Beta 5, with RDS, has restored RDP capability to one of he Hyper-V hosts (Server 2016 Core).

I'm testing now to see if I can safely remove RDS while keeping RDP know that in a worst case scenario I can return to the full Beta 5 installation until you come up with a fix that works.

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

I did ask if I should remove the service using Beta 5 first and then upgrade to 6. In hidsight this would have been the way to go.

Fortunately teamviewer works on Server 2016 Core so I've regained some ability to manage my infrastructure for now but I still need to get RDP working on both of those hosts.

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

Removal via the Beta 5 change is safe, RDP is not affected.

Is there a possibility that repeating the process with the beta 5 installer and then removing RDS may restore RDP on those hosts?

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

I'm testing that on one of my GUI base servers now to make sure that RDP is not affected when Beta 5 removes the RDS from WaykNow.

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

I need to get RDP active on my hosts ASAP. I can't manage my entire infrastructure w/oi it.

If I remove the Remote Desktop component from the existing beta 5 installs is the same thing going to happen?

Beta 6 breaks windows native RDP!!!!

avatar
avatar
avatar

The removal of the remote desktop services completely breaks windows native RDP. I now have two Hyper-V servers (Core) that I'm unable to manage

I'm not touching any more servers or workstations until this is fixed and I need a fi to get RDP working on my Hyper-V hosts that does not involve a complete re-install of the OS.

Second reboot may be required to enable TLS connections

avatar
avatar
avatar

Yes I did install it, do I need to remove it before switching to beta 6? Or, if there are no other differences, can I just remove that component and save having to reboot everything again?

Remote access to Server Core does not work

avatar
avatar
avatar
avatar
avatar

Any attempt to connect to Server 2016 Core with RDP reports that the graphics mode is not supported. This is not the case with other, similar, products.

VNC is useless on Server Core since you can't send the CTL-ALT-DEL sequence to it so RDP is the only method that consistantly works, except in RDM.

Unattended access & services install & work on Windows 10 Enterprise

avatar
avatar
avatar

The downside to that is that many management functions on servers must be carried out on the console session. You'll need to have a method, like RDP itself, to designate if you want the console or not. For workstation OS, it's a moot point since you can only have the console session (unless you have a workaround for that).

Second reboot may be required to enable TLS connections

avatar
avatar
avatar

Some further information on this. If you reboot immediately after the install, that is from the prompt put out by the installation itself, then the second reboot is not required. If you delay the reboot, to allow applications to close, etc.. then the additional reboots are required.

Unattended access & services install & work on Windows 10 Enterprise

avatar
avatar
avatar

well it's a bug in the sense that you indicate it should not work. It's positive in the sense that I'm glad it does work.

Still required three reboots however to get it working :)

1 - 25 of 39 items