Sheridan

Pm sent, cheers!

Yeah - I thought Server 2019 and Windows 10 1809 were pretty much identical! Obviously not 100%!

That's the file I've got and it errors out every time - it does work on Windows 10 though. 2019 must be different in some way

Has anyone managed to get Live Movie Maker to work on Server 2019? I know its a crusty old thing, but we have a couple of people who want to use it on out 2019 RDS system to edit some old videos? The installer just brings up an error 0x8004075 - it does work on Windows 10 though.

Looks like gmail and various other google services have been down for a few hours, mainly affects smtp email access as the web interface seems to work ok Maybe it’s their turn this year, it seemed to be office 362 last year!

I did get one to activate, by fluke more than anything I think, but testing it seems to have brought up even more issues! Creating a new project takes about 10 minutes of 'Downloading scripts' etc - every time you create a project. Where is it downloading from and to, as I can't see much being created in the project folder or AppData folders?

I've now had the request to install this software, its seems like a painful process and so far I can't even get it to activate. I followed their instructions and created the offline installer, which seems to work and install Unity without the Hub. I then run the batch file with the serial number and generic Unity account details in it - something seems to happen but no notification or response. However every time I try and run Unity it tells me I need to activate and to do that I have to install the Hub! I dread installing new software these days as 10% of the time is installing, and 90% of the time is trying to get these flipping awful licensing methods to work. As for Unity, its in the bin for now as I've wasted several days on their licensing mess.

Me too! I'd rather have found I was doing something wrong, or had missed a stage out as this doesn't make a lot of sense. Still, server 2019 is based on Windows 10 so anythings possible....

Bizarrely I now seem to have a working system - all I did in the end was rebuild the 2019 server (even though it was a fresh install!) and install the RDS using the simple method which is exactly what I did the first time, and port forwarded though our TMG it works fine! It does not like reverse proxy on either Smoothwall or TMG though.

I'm only running RemoteApps so I don't get the RD interface normally. I've tried a manually setup RDP session and I get the same error now as well, and nothing appears in the connection monitoring Having now tested server 2016 RDS and got exactly the same error I'm starting to think it might be an external factor!

I don't see any connections in the monitoring tab but I guess that's expected as they only appear when an App is running? And I don't get to that point. I've checked the policies and its the default 'all users, all computers' still, I haven't configured it in any detail yet.

Well, even when I removed the Gateway role on the RDS server I get the same error. I'm guessing RDS doesn't work in 2019 as it seems to have been a buggy release since day one.

It works fine internally and clients don't get the option to bypass the gateway, and externally we get as far as the Apps page. Its now being port forwarded through our old reliable TMG gateway on port 443 only. I've double checked and the whole Domain Users group is a member of the local Remote Desktop User Group on the RDS server. I'll try the reg hack, but it also fails on W7 and Macos so I'm guessing the problem is either the RDS or the routing. However the routing is now very straightforward as the external IP is bound to the TMG, which port forwards all HTTPS on that to the RDS internal IP. Its frustrating as I want to move to this for a year or two instead of keeping our old Citrix system alive. Edit: I notice when I remove the Gateway role and test again, I immediately get a message saying the remote computer could not be found when opening an app, whereas when using the Gateway it takes a few seconds for the original error to appear, suggesting a timeout or routing problem perhaps.

OK, before I run off into the bushes crying, I can't see for the life of me what is wrong on my very simple, basic RDS test box. Internally - a single RDS server 2019 with the Gateway/Web Access/Licensing role on it, with a fixed IP address and domain wildcard certificates installed on it for all the services Externally - a public IP dns registered with the server.domain - with that IP being our Smoothwall UTM's public facing IP Smoothwall - configured to port forward incoming 443 to the internal IP of the RDS server It works fine internally, but externally I can login and see the apps but always see an error 'Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. ' When I look at the connection from the external client, it shows Remote computer as the internal name of the RDS server, and the Gateway as the external fqdn mapped to our smoothwall's external IP It seems like the Smoothwall is working, in the sense I get the login page and can see the apps, but at that stage it fails?

I get this error on Windows clients. Seems to be a fairly generic error though. I've only got port forwarding on 443 so I'm wondering if its trying to access on port 3389?

Yes, that just pops up saying the remote desktop server is currently unavailable! I think I'll go back and try server 2016 next

Hmm, looks like RDS just doesn't work at all from a Mac client. Doesn't matter what I do I get the same error (0x000008 or 0x000016) I can't get the Windows clients to work either. Weirdly it works on a Mac tethered to a phone, but not when at home. The Windows version at home simply continually requests login details even though they're input correctly. I wasn't expecting much from RDS but it looks like I'll be sticking with Citrix on our new build server - it may be expensive but it works across platforms properly!

Bindings on IIS are all IPs on the server, managed to get port forwarding working though! Still can't get reverse proxy to open an app - same 0x3000008 error after the second login appears

I think the Smoothwall is going to be tricky to get working. I've tried both ways and they fail in different ways 1) Reverse proxy the https://server.domain/rdweb to the internal RDS server ip fails with 'connection refused' 2) Port forward HTTPS on our external IP to the ip of the internal RDS shows connection timeout I'm not sure if its the UTM or my RDS server that's not configured correctly, as the Smoothwall config seems pretty simple.

I guess that's my plan B - I assume you're directing all inbound traffic on your public IP/443 to your RDS server? We also want to publish another HTTP service this way but it does use a different port to 443

Its using RD Web Access. I was expecting to use the reverse proxy, probably as I'm used to the TMG method of old. We have the smoothwall public IP as the DNS destination for our rds server so I thought we would reverse proxy the https://server.domain to the internal RDS server ip?

I'm testing a new 2019 server with RDS for Mac and Windows users, it works fine internally but when tested through our 'test' firewall (an old TMG 2010 server) it fails with the error code 0x3000008 which seems to be a generic connection error. I'm about to try and publish the server through our smoothwall UTM instead, has anyone ever tried this, as I would be interested in any pitfalls or problems that they might have had? We have a domain wildcard ssl so we're ready to put a live server out.

That makes sense, you can read 10 articles on MS licensing and come away with 20 different answers! I'll ask our reseller about the cost of these - anyone know what the typical cost is for an RDS CAL?

Hmm, I seem to be stuck in the usual MS licensing loop again! We have OVS-ES based on our FTE count, which I thought covered RDS for this - based on searches and previous threads on here. However a recent enquiry to VLSC support regarding this and they say we didn't purchase it So am I wrong in thinking I can use our OVS-ES agreement number to activate RDS on a server? We have the standard Client/CAL/Office pack

I've trying to run an Office 365 PST import job to pull in some emails - the pst file is showing in the Azure explorer, and the files and map files have passed validation. Problem is the job is showing as 'In Progress' 0% - and has been for hours. The PST file is only 25mb! I've never really used this before, does it actually work or am I needing to find an alternative PST import method?