mikeshaver
asked on
Reasons NOT to connect a Vista home machine to a domain
Got a stubborn person on my hands...he's got a new server 2008 installation, and has a few old Vista Home machines (in addition to all his new Windows 7 Pro machines) that he wants to connect and share files from the new 2008 server.
I want to talk him OUT of it, and have all machines as functional domain members.
I'd appreciate some reasons why that I could use as "why" we shouldn't connect to the file shares from Vista home.
Or would the file shares even work on the home machines...?
I want to talk him OUT of it, and have all machines as functional domain members.
I'd appreciate some reasons why that I could use as "why" we shouldn't connect to the file shares from Vista home.
Or would the file shares even work on the home machines...?
You can't join home machines to a domain. You need an Enterprise/Business or Ultimate.
File share can still be accessed, but will require separate sign on credentials.
File share can still be accessed, but will require separate sign on credentials.
Nuttycomputer is right, but I think that this you already know.
As you know that you can access to shares on domain servers from home version of Windows.
For your sake I hope that this don't know your costumer - but I'm afraid that he does.
1. Home editions were designed for home use and not for business use.
2. It is Vista OS... ...CENSORED...CENSORED...C
3. Domain is useful because of its central authentication and administration. If you don't use computers that can join the domain you will have a lot of work doing administration on separate PCs, changing/setting passwords and permissions hundreds of times,...
As you know that you can access to shares on domain servers from home version of Windows.
For your sake I hope that this don't know your costumer - but I'm afraid that he does.
1. Home editions were designed for home use and not for business use.
2. It is Vista OS... ...CENSORED...CENSORED...C
3. Domain is useful because of its central authentication and administration. If you don't use computers that can join the domain you will have a lot of work doing administration on separate PCs, changing/setting passwords and permissions hundreds of times,...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks everyone. I know you can't join it to the domain.
I'm looking for reasons to talk him OUT of simply connecting to a shared location on the server.
Would anything have to be changed on the server (Server 2008 R2) to allow the shares to be seen from non domain machines?
I'm looking for reasons to talk him OUT of simply connecting to a shared location on the server.
Would anything have to be changed on the server (Server 2008 R2) to allow the shares to be seen from non domain machines?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.microsoft.com/kb/929543