@dbeato said in Reset 120 Day Grace Period for Windows RDS Server with PowerShell: @scottalanmiller I assume you needed to do this while dealing with the RDS CALs on your post about that right? Yeah. They still have not come through, but there is a chance that they might today. We will see.

@gjacobse said in Add a User to Remote Desktop Users in Windows Remotely: I seem to remember doing this via ScreenConnect CMD Only works if SC is installed, which if it was, we'd not need to do it

Update- So far, I have 2 vultr instances running squid. I used a snapshot of the first, to deploy the second. I have setup postfix for notifications by fail2ban and dnf-automatic. I also setup the firewall and squid settings to only allow connections from our WAN IP range and set the proxy to only allow access to certain domains that were specific to this project. I mostly have the servers ready to go. I tried a Chrome extension called sessionbox. They have a paid version that allows you to run multiple proxy servers in different sessions with color coded tabs. Unfortunately, it is pretty complex (too complex for most of my users) and I can't find a way to push out settings or do bulk changes. That means I am circling back to what JB suggested, by launching chrome with incognito and proxy options. %pathtochrome%\chrome.exe --incognito --proxy-server="http://proxy01.domain.local:3128" --user-data-dir="%LOCALAPPDATA%\Google\ChromeProxy01\User Data I have tested this by running it in a cmd prompt. These will need to be launched separately, so users can keep track of which window they opened for which login they should be using. Otherwise, it defeats the purpose. Is the only way to run this by using a bat file? I can't seem to get it going by just using a simple shortcut to Chrome.

@dafyre said in Running Xrdp on Ubuntu: Not sure what to do about the EFI issue.... What I do when I want to use mine like that is set up x11vnc-server and then run it through XRDP (and choose the console option). It's faster than stock VNC... Don't ask me why, lol. I haven't gotten instructions for that yet, I don't think. If I remember right, after a reboot, you have to connect, close the connection, and then reconnect back using the XRDP+VNC option. I don't have any installation instructions for that setup on hand though. I can work it out and post them if you like. This is likely where I went 'rouge' in that I didn't use x11vnc-server.. I had notes on that,.. at least I believe and have misplaced them. so I had forget that. As I was starting to have other 'OS' Kernel issues (the mouse and keyboard wasn't working correctly) I nuked that partition from Windows, and will rebuild. Maybe it'll survive as I am of course getting grub 'errors' since that partition is gone.

I'm just reading the manual, but taking a stab I would think xfreerdp /multimon /monitors:0,1

RDP at home is fine.

@dbeato Has to be at least related because disabling it works

Is Remmina ceashing when RDP to older servers like Server 2008 R2? That’s the only server giving me issues with Remmina. Try freerdp or rdesktop through command line and see if you have a better experience.

@black3dynamite said in Remote Desktop to Fedora 28?: @dafyre said in Remote Desktop to Fedora 28?: @black3dynamite said in Remote Desktop to Fedora 28?: @dafyre said in Remote Desktop to Fedora 28?: @fuznutz04 said in Remote Desktop to Fedora 28?: @dafyre I didn't ever get back to needing this until now. How were you able to achieve this? I use Fedora 28 and the Cinnamon desktop. Sadly, no, I haven't. From what I can tell, Fedora 28 (probably 29 too) use Wayland by default. I haven't found a way to get it working yet. I tried switching the Login Screen to use X first, but even that didn't help. Have you tried disabling Wayland instead? I hadn't thought about that. I'll have to do a fresh install and see how that's done, unless there's a working VNC Server package in Fedora 29... Just edit /etc/gdm/custom.conf and uncomment WaylandEnable=false and then restart. You will have only two options GNOME and GNOME Classic. That gets me one step closer. I can get XRDP to connect to the local VNC server, but the user has to log in (locally) first...

Thanks.

@dbeato said in Disable Network Level Authentication or NLA Remotely via PowerShell: @scottalanmiller said in Disable Network Level Authentication or NLA Remotely via PowerShell: (Get-WmiObject -class "Win32_TSGeneralSetting" -Namespace root\cimv2\terminalservices -ComputerName "remoteServer" -Filter "TerminalName='RDP-tcp'").SetUserAuthenticationRequired(0) This worked, but also as soon as the server is updated to the latest then the issue goes away. Yes, if you have that option.

This might be useful for some people: https://mangolassi.it/topic/17197/disable-network-level-authentication-or-nla-remotely-via-powershell

Hello. I tried rdp connection to the server by entering the ip address with relative port (192.168.1.66:1512) and it worked. I do not understand why the problem occurred with the installation of the latest Windows 10 release (April 2018). thank you. regards.

I've been dreaming of creating my own RD gateway authentication plugin - but I doubt I will ever find the time.

Take a look at this as well https://docs.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc

@Dashrender said in Unable to connect to RDP: @JaredBusch said in Unable to connect to RDP: @Dashrender said in Unable to connect to RDP: @JaredBusch said in Unable to connect to RDP: @Dashrender said in Unable to connect to RDP: Does it work from a computer on the same network at the server? Looking to see if it's an ZT problem or a Server problem. Same error over normal IP also once I brought up my IPSEC tunnel OK but you still haven't tried from another PC on that network - i.e. no VPN. Does not matter. No one connect on network. Also two differnt IP protocols do not work. Issue is not whatever the hell you are driving at. two different IP protocols? /sigh... IP subnets.

@DustinB3403 said in RDP support for VMs or Console only Access: Opening up RDP access (not necessarily from the Internet) but in general just opens more ports, more firewall changes etc. Sure, but granting unnecessary access to the console does that, too. You need access to the VMs from far more places than you need it to the console.

Remmina is a great tool. I've had excellent luck with it.

@Dashrender said: @dafyre said: @Dashrender said: @scottalanmiller said: @FATeknollogee said: @Jason said: @FATeknollogee said: Type 3: Users (are contractors), they connect via VPN from overseas Seems like a bad idea. Usually employees are given VPN access from company owned devices. a VPN is too much exposure for non-company owned devices and for people who aren't full employees. I would look into some other form of access, RD Gateway with RDS or Ctirix etc for these people. Are you saying access via ZT is not a good idea? Correct. ZT is a VPN. VPNs from arbitrary devices is normally a bad idea. The only exception to this is when you would have happily exposed the LAN to the Internet and this is purely a handy control of IP addresses. If security is your goal, you are bypassing security using a VPN in this role. VPNs are very dangerous because they are about exposure. The whole trusted network issue. LAN vs LAN-less As more and more things move to networks that are not local to our computers, we're changing seeing how we trust things. Traditionally we trust machines that are on our local LAN, but, if flip that on its ear and trust nothing, and always setup authenticated/trusted communications no matter where device is in comparison to us, then we are much safer. I think that it is beyond time that we stop trusting machines on our local lan. Even my home network has the service discovery disabled, and each machine has its firewall turned on for that very reason. I go back and forth on using the home networking features that Windows has these days. I use them because they are there. I also have linux boxes at my house too, so there's that.

@stacksofplates Btw Centos got updated to: CentOS 7.4 (1708) CentOS Linux release 7.4.1708 (Core) https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7?action=show&redirect=Manuals%2FReleaseNotes%2FCentOS7.1708 Noteable mentions At least 1024 MB RAM is required to install and use CentOS-7 (1708). When using the Live ISOs for install, 1024 MB RAM produces very slow results and even some install failures. At least 1344 MB RAM is recommend for LiveGNOME or LiveKDE installs. The initramfs files are now significantly bigger than in CentOS-7 (1503). You may want to consider lowering installonly_limit in /etc/yum.conf to reduce the number of installed kernels if your /boot partition is smaller than 400MB. New installations should consider using 1GB, which is now the upstream recommended, as the size of the /boot partition. Sadly Centos 7.4 does not work with this guide Damn

@dafyre said: Cool. A few months back, I stumbled across MobaXterm and snagged it when I had a few extra bucks. I'll keep my eyes on RoyalTS for sure, though. Just checked MobaXterm and i really like it. My most favorite option as of now is the file explorer & shell on the same window. Helps me a lot if i need to edit some text files, copy files to and from the desktop etc at the same time while executing other commands.

With so many services starting up, there is a lot of chances for things to have not all fired up yet.

Is say so!