Windows 10: Public booking system on local domain publicly available via RDP

Hellur company has received a link to access a booking system which uses an RDP connection. The booking system is publicly available to customers of the service.When opening the RDP connection the window immediately flags an untrusted certificate. I am not an expert in this but the certificate has been issued by serveruser.server.local and not by a recognised certificate authority.This booking system is used to collect personal information - payment details, home addresses, email addresses etc. in the UK. The company that provides the service has a valid domain name and their website has a

:)

 

Suggestions on Public domain name and local domain

Thank you in advance for any feedback or suggestions. Here is my situation....

Client has a local domain setup that is domain.local

Wanting to implement Hyper-V virtual desktops through RD Web Access

Purchased a secure certificate and added it to ISS, added the certificates to RDS

While the RD access works and allows me to sign on to the virtual desktops in the pooled collection. I am having a couple issues.

After signing in to RD Web Access it shows me the available desktop. When opened it downloads the .rdp file and opens and again ask to connect and sign on.

The rdp opens with the following details:

Publisher: app.example.com

Type: Remote Desktop Connection

Remote Computer: Gateway.example.local

Gateway server: app.example.com

Questions:

How do I get the remote computer to not show the domain.local address?

We have multiple clients that all have same domain, problem is when signing into the rdp connection, it tries to authenticate with our local domain controller, any way to prevent this?

Moved from: Windows / Windows 10 / Windows settings

 

Local account installation question

I'm fairly certain that Skip this step was available in 10.0.130 - the workaround in Step 20 (back button) is no longer required.

The currently known, as of 10.0.130, ways to create a Local account sign-in are

• Skip this step at the MS account creation phase
• No Internet connection during the install
• static IP (post# 2 by Fragment) - New (to me anyway)

 

Migrate Locale Profile to Domain

I removed my reply because watching those instructions on TechNet I started wondering if they really work with Windows 10.

Anyway, whatever you try create first a dummy profile, customize it a bit and move it to domain. If everything works, you can then move real profiles.