Network issues

My wife just bought a business that has about 15 pc's running on a small network. Some are XP Pro, some XP Home. The Pro's all appear to be set up on a domain, Home's on a workgroup. I think they initially ran a client/server network as there are 2 servers in the back.

Their business software is co-located, run completely over the internet. The pc's are all connected to a router. I'm thinking of simplifying the system by getting rid of the servers and setting everything on a workgroup. This would give me 15 free-standing pc's, all connected to the internet through the router.

Any thoughts/suggestions?

 

you wont have a domain obviously, so that will rule out any kind of active directory or group policies you have. what is running on those servers?

 

also just fyi xp pro and xp home don't play well together. so be very carefull

 

One server has their old business software running. There is one guy that references it every now and then. I could move the database to his computer and eliminate that server. The other server isn't running anything except the server software - SBS 2003, I think. I actually turned it off last week and nothing happened that I could tell.

My experience with XP Home is pretty limited. What kind of issues should I be looking for?

 

Nothing wrong with using a workgroup for 15 pcs. It would run fine. Several companies I look after run like this.

There would be differences - advantages and disadvantages.

If users normally always log on to the same pc then the you don't need one of the big advantages of a domain - the ability to log on at any pc.

Runnning a workgroup has other advantages - you can only have one domain but can have several workgroups and so arbitrate , for instance, printer use or access to accounts data. This is a way of replacing the centralised permissions you get with a domain.

However there are also disadvantages.

Firstly it is more work intensive for the IT tech. OK for me on contract, but harder on an inhouse guy or gal.

Secondly since it is the PC not user that logs on with a workgroup consider what happens if a pc fails. With a domain you just swap it out with another ready set up and working one, because all the stuff, including the user personae, reside on the whole network. With a workgroup getting a given user back working can be a problem.
I actually address this by storing cloned hard drives for some mission critical pcs in workgroups.

 

I don't think this will be much of a problem. There are only 2 or 3 users who do more than connect to the co-located software or the internet. Actually, I wish that thin clients were cheaper than what they are because that's what she needs.

I'm not sure thin client would be the correct term. What she really needs is something that will connect to the internet and nothing more.

 

it is how the assign and recognize rights to folders. sharing anything from pro to home is copper plated Btch