Please register or login. There are 0 registered and 984 anonymous users currently online. Current bandwidth usage: 326.30 kbit/s December 09 - 09:16pm EST 
Hardware Analysis
Forums Product Prices

  Latest Topics 

More >>


  You Are Here: 
/ Forums / Windows 7 /

  Windows 7 and Bussiness Networking 
 Date Written 
R G Mar 08, 2012, 03:45am EST Report Abuse

Im buying about 10 computers for a small office and I was wondering if Windows 7 Home basic 64bit would be able to connect to a network Server.I saw that next to the description it said (JOIN one HOMEGROUP ONLY).
Not sure what thats suppose to mean but if it means it cant join a big network or somehow are handicapped in that manner I would rather want to stay away form it?

Thanks and regards

Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
R G Mar 10, 2012, 01:08pm EST Report Abuse
>> Re: Windows 7 and Bussiness Networking
No Replies?
Ghez thanks allot guys?

Dr. Peaceful Mar 10, 2012, 02:03pm EST Report Abuse
>> Re: Windows 7 and Bussiness Networking
Dude, you can't really expect a fast response in this forum here. Not a whole lot of tech heads remaining here, and no one's expert in everything, computer is a big field...

As to your question. Yes, it's true that Win7 Home can NOT join a domain server without modifications / workarounds. Here is a thread from another forum that gives some solutions and suggestions.

john albrich Mar 10, 2012, 02:40pm EST Report Abuse
>> Re: Windows 7 and Bussiness Networking
Another VERY important factor for any business IT planner to consider is Microsoft's termination schedule for any given Windows OS's support.

Win7 Home support is planned to terminate Jan 2015...less than 3 years from now. See my thread at:

In my opinion, Win7 Home is a crippled marketing-leveraged OS. Network limitations are only some of the reasons to steer clear of 'Home' version and go at least for Win7 Pro in a home or small business environment.

(BTW, I appreciate you didn't expect instant responses, but sometimes people don't see every single thread that crops up on the 'latest' page, especially when SPAMMERS come along and fill-up the 'latest' page threads list...thus perhaps burying your thread down the page or in the 'noise' of a dozen SPAM posts.)

R G Mar 10, 2012, 04:01pm EST Report Abuse
>> Re: Windows 7 and Bussiness Networking
Hey John thanks allot for the reply.
Well the PCs really only need to be able to Access the server and run an .Exe from the server to load into their ram then everything that gets punched into the (Now loaded) PC should read and write to the server HDD...although the server is Windows 2003 Server machine.
Would there be any complications accessing windows 2003 from a Windows 7 Home PC?

I totally do understand the hampering that unsupported windows versions might cause but this is really just the most basic form of Windows Usage soo if I could to that then im in the clear.

BTW the server literally has a SHARED folder with the program on in it.And the that folder then gets mapped on the PCs having to run it.

john albrich Mar 12, 2012, 08:06am EDT Report Abuse
>> Re: Windows 7 and Bussiness Networking
R G said:
...Would there be any complications accessing windows 2003 from a Windows 7 Home PC?...BTW the server literally has a SHARED folder with the program on in it.And the that folder then gets mapped on the PCs having to run it.

You may luck out and everything will run smoothly with a few simple mods on the clients ...but history tells us that is unlikely.

But, the short answer is yes, there will likely be complications. The degree to which that impacts the usability in a particular network topology can vary significantly. The impact can range from requiring low-level configuration manipulation (e.g. registry manual editing) to non-operability and dataset and program support elements (e.g. dll) compatibility issues.

For example, the Home versions of Windows generally cannot join a domain without using manual workarounds, and those still may be unable to provide full networking functionality in some situations.

Search the internet on something like
[ Windows 7 home clients and windows 2003 server ]
You may also find instructive information from more long-term historical experiences by searching on
[ Windows XP home clients and windows 2003 server ]

Whatever you decide to do, it would be a good idea to try all the program sharing, dataset sharing, dataset access control, emailing, printing, etc. that you plan to do with one licensed client before you pay for the additional licenses. This may uncover such things as the necessity of sharing (and providing lock control for) datasets with separate applications installed on the clients as opposed to a single application on the server...which can further complicate the compatibility issue.

Regardless of the OS installed on your clients, don't forget there is also the legal book-keeping issue of ensuring your licenses allow the clients you intend to use.

edit to add:
I also don't know to what degree, if any, applying mods to 'Home' clients (to fool them into networking as though they are 'Pro' or 'Enterprise' clients) will have on network and workstation security. I have personally never tried to gimmick-up a 'Home' OS installation to run in a business environment. I don't consider the minimal up-front license cost savings to be worth it...compared to increasing the complexity and therefore increased cost of maintenance, possible increased maintenance down-time, possible loss of functionality/compatibility (possibly at the most inconvenient times), and potential unquantified increased risk of compromising network security.



  Topic Tools 
RSS UpdatesRSS Updates

  Related Articles 

A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.