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...?

Who is Participating?
Darius GhassemConnect With a Mentor Commented:
You would have to type your username and password everytime to access any domain resource. You wouldn't be able to just connect to the share without having to enter a password this is the biggest issue.
Vista Home Premium and Vista Home Basic can't be joined to a domain anyways:
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.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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...CENSORED ;) I really don't like vista, because it is (on my opinion) poorly written, slow, full of problems,...
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,...
NuttycomputerConnect With a Mentor Commented:
I would add Security to that list as well. For security purposes you're going to want to make sure that no one can access those shares but Authorized Users and only from Authorized Computers.
mikeshaverAuthor Commented:
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?
davorinConnect With a Mentor Commented:
You don't have to change anything on w2008.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.