I know this is a very common question, and I’m glad that I was the only person I know who asked it.
The “one way” relationship between the workstation and the primary domain is an important one because it can have serious consequences. If you have a trust relationship with the host operating system, then anything that happens on the workstation, even if it is a virus or a simple reboot or two, can cause the host operating system to malfunction. These host operating systems are Windows, Mac, Linux, and now (unlikely) Windows Server.
If you have a trust relationship with the host operating system, you can end up with a broken workstation. If you have a trust relationship with the operating system, you can end up with a broken workstation. If you have a trust relationship with the user account file on the workstation, you can end up with a broken workstation. If you have a trust relationship with the user account, you can end up with a broken workstation.
The first time I heard this concept, I thought it was some kind of new technology. But that’s not what it is. It’s a feature of Windows 8.1 that allows you to get a second copy of the user account file and then install that copy onto your system to allow you to use Remote Desktop Services on your Windows 8.1 machine.
Windows 8 has a feature called “remote desktop services.” Remote desktop services let you get into your computer remotely. The best part about remote desktop services is that you don’t even have to be logged in – once you’ve logged in, your computer just goes back to you. It’s like using your phone or laptop to talk to your boss.
In short, once youre logged into your desktop, the computer just goes back to you. The problem is that your computer is no longer the same computer you had before you logged in. It’s now a completely different computer. The only people who know you are the people you have logged in with, and the only people who know you are the people you have logged into remotely.
Its not like the computer was infected with malware or something. The problem lies in a bug in the Microsoft Windows Remote Desktop protocol. This protocol is used by Microsoft to connect with other Windows PCs to the same domain as the one the user is logged into and have that user logged in as well. The problem is that someone logged in as the user and then remotely logged in as the user, now that user doesnt know that anyone else is remotely logged in as that user.
The way we communicate with Windows computers is the Remote Desktop protocol. Each time we log onto a computer, our name, password, and a session identifier are sent over the network, which is then sent back to Microsoft’s servers. These servers then determine if the user is logged in, if a session is active, and if the remote user should be logged onto the machine we intend to share.
That all sounds good, but a remote user can also be a local user too. That’s why Microsofts servers will always send us the same session identifier for us to log in as – even if we go to a different computer. We have to be careful that we don’t send the same session identifier again, because the remote user might be a local user who’s not logged into the machine.
We can also send our own session identifier back to the remote user, but it’s a little bit more problematic. One way to do that is to send the remote user the IP address of the primary domain, which is fine, but what if the remote user logs out of the session. We would have to send that back to the server that the session was in anyway.