@scottalanmiller said in Making an RDP Terminal Server with Ubuntu Linux: I recommend the Remmina RDP client tool, it's the bomb. I love Remmina as a client.

@syko24 said in Can remote desktop Win10 be remotely activated somehow?: @Pete-S said in Can remote desktop Win10 be remotely activated somehow?: Thanks guys. I tried accessing remote registry, remote powershell and ssh but without success. I have to find out how they do their remote administration and get them to enable rdp for me. It was worth a shot though. Try MMC and see if you can add Services for their computer. If you can add that successfully then you can enable Remote Registry and then from there enable rdp. Make sure you restart the rdp service after making the registry change. Another method would be if you have PDQ deploy installed on another system at the location, you can try to push a ScreenConnect or similar install to the system. There are steps one needs to take to ensure remoteability in any kind of way you are hoping for. Either through specific group policies, in the base image, during deployment, via device management software, etc. It's something they would know they did. Any MMC snap in such as remote registry will have required specific steps be taken first to ensure access that way. The best thing to do is ask, because it takes 2 minutes to write the question, then do other things while you wait for the answer, rather than wasting time and money throwing darts in the dark.

@pmoncho said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?: @Dashrender said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?: Cool, then you should have it easy. FYI - Published apps still create a full profile on the RDS box, Just the desktop isn't presented to the user. If the application allows them to browse around, they could typically see the drive letters, the mapped printers, etc... that's why you still need to lock all that stuff down. Thanks for the info. I will keep that in mind. I was debating about using UPD's like @wrx7m and that was my interest in this post. Also, still planning out where to put Connection Broker, WebAccess and Licensing but that is another post. For local profile management, UPDs are a lot cleaner. If we are not putting them on a file server across the network then a second partition/VHDX is set up for that task to keep them separate. With the inclusion of FSLogix with RDS CALs/SALs now it's a no-brainer, IMNSHO, to set the project up on the FSLogix version. Storage management is another reason why UPDs on a network or separate partition make sense. Keeping a local profile on the C:\ of the session host is messy and can cause issues down the road with users coming and going. As far as the Broker/Gateway/Web put those roles on one VM but separate from the Session Host.

@scottalanmiller said in Microsoft Office - Licensing Questions For 3 Scenarios: @flaxking said in Microsoft Office - Licensing Questions For 3 Scenarios: I think you must be missing what's going on here. This removes the requirement to integrate more directly with MS Office, instead relying on a separate library that is provided standalone from Office and thus allows saving to Excel. We've had zero issues with using this library, which is actually pretty uncommon for us. The issue is flexibility. Using third party libraries, you can integrate with Excel or with anything else. Using the Office libraries, every user, in ever system, is bound by the limitations of the most problematic. It makes deployments more costly, and more complex. That's true, it's the kind of self perpetuating lock-in that has served Microsoft so well. People use Excel, and they ask for saving to Excel spreadsheet, so we create the integration specially to allow Excel and not include ODF, then we help keep the industry locked into using Excel because that's all we support unless you want to just save to CSV. As for the cost and complexity of deployments... that could be true, except that the installation of our main software is already so complex and costly that dealing with potentially installing this library is the easiest part. I think we probably only have one other developer who would be able to figure out how to install it. I've never heard of any client's IT that have been able to figure out how to install it (just calls from those who have tried), client services has to do literally every install.

@serseri26 said in Reset 120 Day Grace Period for Windows RDS Server with PowerShell: I tried server 2019 and it was successful you saved me from great trouble thank you so much. Glad that it worked still!

@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

@JasGot said in Updated - Connecting to 1 Site With Separate Logins/Several IPs: @wrx7m said in [Updated - Connecting to 1 Site With Separate Logins/Several IPs]> This works on Windows 10 (1703, 1809, 1903), Server 2016 (1607), Server 2012 R2 and Server 2008 R2. Tor is another option. Proxies are already out there. Lots of guides on setting it up to run multiple browsers from different IPs. We did it years ago for a project and it was perfect. Took a few minutes to setup, but was perfect for the task. There's even a bash script to do all the setup for you. (Not on Windows, of course) Thanks. This has been up and running via squid on Fedora for several months and works really well.

@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.