RDP vs domain joining [closed]
Why would you join computers to a domain as opposed to just making everyone RDP to the server? As I understand it, if you make everyone in an office environment use RDP and use the server as a terminal server environment you only really have to worry about the server for the most part. But if you join the computers to the domain you have to deal with a lot more work because you have to make sure the pc's are taken care of too.
What am I missing here? Why do organizations add pc's to the domain vs just making them rdp from their pc to the server?
windows remote-desktop domain
asked Dec 11 at 1:48
captain
1
closed as primarily opinion-based by Scott, Appleoddity, Keltari, n8te, PeterH Dec 11 at 8:12
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Why would you join computers to a domain as opposed to just making everyone RDP to the server? As I understand it, if you make everyone in an office environment use RDP and use the server as a terminal server environment you only really have to worry about the server for the most part. But if you join the computers to the domain you have to deal with a lot more work because you have to make sure the pc's are taken care of too.
What am I missing here? Why do organizations add pc's to the domain vs just making them rdp from their pc to the server?
windows remote-desktop domain
asked Dec 11 at 1:48
captain
1
closed as primarily opinion-based by Scott, Appleoddity, Keltari, n8te, PeterH Dec 11 at 8:12
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
There are so many reasons. Too many to cover in a single answer. I suggest you do some research into Windows domains and active directory.
– Keltari
Dec 11 at 3:06
I mean I understand what a domain is and how active directory works. What I'm asking is what's the advantage, what's the security hole, why not just use RDP instead? You're response offers no information and isn't helpful at all. This says the question is put on hold because it's opinion based... Does this mean there's really no big difference between using RDP vs joining PC's to the domain? Just whichever way you want to do things for your network environment? I asked here because I knew I could get answers from people with far more experience than me. I've only used RDP recently.
– captain
Dec 11 at 13:56
Not trying to be rude, but you obviously dont know what a domain is or how active directory works. The reasons why you would use them and what there advantages are literally fill books. This is the reason the question is too broad. Not to mention there are limits to RDP.
– Keltari
Dec 11 at 18:08
add a comment |
Why would you join computers to a domain as opposed to just making everyone RDP to the server? As I understand it, if you make everyone in an office environment use RDP and use the server as a terminal server environment you only really have to worry about the server for the most part. But if you join the computers to the domain you have to deal with a lot more work because you have to make sure the pc's are taken care of too.
What am I missing here? Why do organizations add pc's to the domain vs just making them rdp from their pc to the server?
windows remote-desktop domain
asked Dec 11 at 1:48
captain
1
Why would you join computers to a domain as opposed to just making everyone RDP to the server? As I understand it, if you make everyone in an office environment use RDP and use the server as a terminal server environment you only really have to worry about the server for the most part. But if you join the computers to the domain you have to deal with a lot more work because you have to make sure the pc's are taken care of too.
What am I missing here? Why do organizations add pc's to the domain vs just making them rdp from their pc to the server?
windows remote-desktop domain
windows remote-desktop domain
asked Dec 11 at 1:48
captain
1
asked Dec 11 at 1:48
captain
1
asked Dec 11 at 1:48
captain
1
asked Dec 11 at 1:48
captain
1
asked Dec 11 at 1:48
captain
1
1
closed as primarily opinion-based by Scott, Appleoddity, Keltari, n8te, PeterH Dec 11 at 8:12
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as primarily opinion-based by Scott, Appleoddity, Keltari, n8te, PeterH Dec 11 at 8:12
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
There are so many reasons. Too many to cover in a single answer. I suggest you do some research into Windows domains and active directory.
– Keltari
Dec 11 at 3:06
I mean I understand what a domain is and how active directory works. What I'm asking is what's the advantage, what's the security hole, why not just use RDP instead? You're response offers no information and isn't helpful at all. This says the question is put on hold because it's opinion based... Does this mean there's really no big difference between using RDP vs joining PC's to the domain? Just whichever way you want to do things for your network environment? I asked here because I knew I could get answers from people with far more experience than me. I've only used RDP recently.
– captain
Dec 11 at 13:56
Not trying to be rude, but you obviously dont know what a domain is or how active directory works. The reasons why you would use them and what there advantages are literally fill books. This is the reason the question is too broad. Not to mention there are limits to RDP.
– Keltari
Dec 11 at 18:08
add a comment |
There are so many reasons. Too many to cover in a single answer. I suggest you do some research into Windows domains and active directory.
– Keltari
Dec 11 at 3:06
I mean I understand what a domain is and how active directory works. What I'm asking is what's the advantage, what's the security hole, why not just use RDP instead? You're response offers no information and isn't helpful at all. This says the question is put on hold because it's opinion based... Does this mean there's really no big difference between using RDP vs joining PC's to the domain? Just whichever way you want to do things for your network environment? I asked here because I knew I could get answers from people with far more experience than me. I've only used RDP recently.
– captain
Dec 11 at 13:56
Not trying to be rude, but you obviously dont know what a domain is or how active directory works. The reasons why you would use them and what there advantages are literally fill books. This is the reason the question is too broad. Not to mention there are limits to RDP.
– Keltari
Dec 11 at 18:08
There are so many reasons. Too many to cover in a single answer. I suggest you do some research into Windows domains and active directory.
– Keltari
Dec 11 at 3:06
There are so many reasons. Too many to cover in a single answer. I suggest you do some research into Windows domains and active directory.
– Keltari
Dec 11 at 3:06
I mean I understand what a domain is and how active directory works. What I'm asking is what's the advantage, what's the security hole, why not just use RDP instead? You're response offers no information and isn't helpful at all. This says the question is put on hold because it's opinion based... Does this mean there's really no big difference between using RDP vs joining PC's to the domain? Just whichever way you want to do things for your network environment? I asked here because I knew I could get answers from people with far more experience than me. I've only used RDP recently.
– captain
Dec 11 at 13:56
I mean I understand what a domain is and how active directory works. What I'm asking is what's the advantage, what's the security hole, why not just use RDP instead? You're response offers no information and isn't helpful at all. This says the question is put on hold because it's opinion based... Does this mean there's really no big difference between using RDP vs joining PC's to the domain? Just whichever way you want to do things for your network environment? I asked here because I knew I could get answers from people with far more experience than me. I've only used RDP recently.
– captain
Dec 11 at 13:56
Not trying to be rude, but you obviously dont know what a domain is or how active directory works. The reasons why you would use them and what there advantages are literally fill books. This is the reason the question is too broad. Not to mention there are limits to RDP.
– Keltari
Dec 11 at 18:08
Not trying to be rude, but you obviously dont know what a domain is or how active directory works. The reasons why you would use them and what there advantages are literally fill books. This is the reason the question is too broad. Not to mention there are limits to RDP.
– Keltari
Dec 11 at 18:08
add a comment |
1 Answer
1
active
oldest
votes
If it's a company machine I will join it to the domain. I want the user to know they are using company property for one reason. And being joined to the domain makes logging in and accessing shared folders or other company resources less complicated, often the end user can't handle computer network complications.
If it is the users personal machine, and they can pass security, then I generally don't force them to join the domain, but like I said, this can make logging in and accessing shares or other company resources more complicated so the user ends up being schooled about domains and permissions, etc...
answered Dec 11 at 2:08
Larryc
57228
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If it's a company machine I will join it to the domain. I want the user to know they are using company property for one reason. And being joined to the domain makes logging in and accessing shared folders or other company resources less complicated, often the end user can't handle computer network complications.
If it is the users personal machine, and they can pass security, then I generally don't force them to join the domain, but like I said, this can make logging in and accessing shares or other company resources more complicated so the user ends up being schooled about domains and permissions, etc...
answered Dec 11 at 2:08
Larryc
57228
add a comment |
If it's a company machine I will join it to the domain. I want the user to know they are using company property for one reason. And being joined to the domain makes logging in and accessing shared folders or other company resources less complicated, often the end user can't handle computer network complications.
If it is the users personal machine, and they can pass security, then I generally don't force them to join the domain, but like I said, this can make logging in and accessing shares or other company resources more complicated so the user ends up being schooled about domains and permissions, etc...
answered Dec 11 at 2:08
Larryc
57228
add a comment |
If it's a company machine I will join it to the domain. I want the user to know they are using company property for one reason. And being joined to the domain makes logging in and accessing shared folders or other company resources less complicated, often the end user can't handle computer network complications.
If it is the users personal machine, and they can pass security, then I generally don't force them to join the domain, but like I said, this can make logging in and accessing shares or other company resources more complicated so the user ends up being schooled about domains and permissions, etc...
answered Dec 11 at 2:08
Larryc
57228
If it's a company machine I will join it to the domain. I want the user to know they are using company property for one reason. And being joined to the domain makes logging in and accessing shared folders or other company resources less complicated, often the end user can't handle computer network complications.
If it is the users personal machine, and they can pass security, then I generally don't force them to join the domain, but like I said, this can make logging in and accessing shares or other company resources more complicated so the user ends up being schooled about domains and permissions, etc...
answered Dec 11 at 2:08
Larryc
57228
answered Dec 11 at 2:08
Larryc
57228
answered Dec 11 at 2:08
Larryc
57228
answered Dec 11 at 2:08
Larryc
57228
57228
add a comment |
add a comment |
There are so many reasons. Too many to cover in a single answer. I suggest you do some research into Windows domains and active directory.
– Keltari
Dec 11 at 3:06
I mean I understand what a domain is and how active directory works. What I'm asking is what's the advantage, what's the security hole, why not just use RDP instead? You're response offers no information and isn't helpful at all. This says the question is put on hold because it's opinion based... Does this mean there's really no big difference between using RDP vs joining PC's to the domain? Just whichever way you want to do things for your network environment? I asked here because I knew I could get answers from people with far more experience than me. I've only used RDP recently.
– captain
Dec 11 at 13:56
Not trying to be rude, but you obviously dont know what a domain is or how active directory works. The reasons why you would use them and what there advantages are literally fill books. This is the reason the question is too broad. Not to mention there are limits to RDP.
– Keltari
Dec 11 at 18:08