You can obtain a free hostname from a dynamic DNS service provider like Dynu and then use that hostname to access your PC in your home network using RDP. I have both RDP and VNC access to my machine at home so that in case RDP fails, I am able to access using VNC.
I have always on device tunnels working. However one important aspect is not functioning, I cannot communicate with VPN connected devices from internal resources. However I can communicate with all internal resources from the device tunnel. Is there a route I need to publish to my core switch? Right now both of my NICs on the vpn server are on the same subnet, should the external one be on a separate subnet in the dmz? I've tried adding routes to the VPN server, but to no avail. I see aside from the two NICs I have on the VM, RRAS creates a virtual NIC I assume as the gateway for VPN connected devices.
I followed this and then found out there's a missing step. After you have moved the SUSDB and LogFile, you need to make sure this account has read and write permissions to both or your WSUS will not sync because it will be in READONLY mode: NT ServiceMSSQL$MICROSOFT##WID
Hello. We use a tool ADAxes to configure the security on OUs. This tool uses powershell to modify rights and can use PowerShell cmdlets as needed. This tool exists in a different forest from the forest where the computers/OUs are located.
The AdmPwd,PS cmdlets to set security does not seem to function with the target in a different forest (there is a forest-level trust between the two).
Is there a work-around? For simplicity, we prefer to use the cmdlets to modify our 200 OUs rather than translate the security into pure PowerShell commands to modify ACLs.
I have a problem with TightVNC. When I login to user using this method over VNC, and I want to install something, o run an application from the user then I can't paste the password to the UAC-promt. With the other programs installed as service, like Teamviewer or Anydesk I can use the copy-paste.
The AD join method worked perfectly, thank you very much for providing this information. Saved us a ton of work rebuilding an ESX host!
Note to others - it may take a little while for AD to replicate the group, membership and computer account information around all DCs if you have several DCs, so just be patient - it took about 20 minutes for the replication to complete for me (4 DCs).