How does Windows Server 2008 work?

[McRat]

I have about 15 computers that need to share a common fileserver.

I was peer-to-peer Windows until we got a lot of "too many connections" at the client ends. Then in March, I changed the fileserver to Linux. That problem went away.

But I really don't know what Windows Server does that just peer-to-peer doesn't. And I don't know what to buy if I switch. How many "client licenses" do I really need? One for each computer? Or one for each active connection? We have 8 employees but have multiple computers for each of them. Some of the computers are machine controllers that don't access the server often. Only a max of 8 active server connections can exist.

 

[Mike]

I have about 15 computers that need to share a common fileserver.

I was peer-to-peer Windows until we got a lot of "too many connections" at the client ends. Then in March, I changed the fileserver to Linux. That problem went away.

But I really don't know what Windows Server does that just peer-to-peer doesn't. And I don't know what to buy if I switch. How many "client licenses" do I really need? One for each computer? Or one for each active connection? We have 8 employees but have multiple computers for each of them. Some of the computers are machine controllers that don't access the server often. Only a max of 8 active server connections can exist.

I have a version of Windows Server 2003 which I bought for 10 clients. To access that server from other clients, those clients had to be added as a user and once I met that limit I too was limited. I have found I can map a drive or folder on a client and then share that folder/drive and network browse that drive or folder. There may be an easier way than this but, I built two networks by installing two NIC's in the one shared content client. I then networked the other 3 computers to the one computer and set it as a gateway to allow internet access to pass through that client and read/write to the server. I know it's a hassle but with the price per client at the time it was a solution.
We only used it about 9 months then went another route. Biggest draw back was that computer had to be on all the time for the others to work properly no doubt.

 

[Fingers]

For your situation Pat, I recommend Network Attached Storage to my customers. Buffalo makes the Terastation in several sizes and is more or less plug and play. Some configuration required to enter users and divide up the disk space and such.

Unlimited connections. (within system resources) I have at least one installation banging the NAS with 50 connections.

 

[McRat]

Thanks!

Well, Linux is currently working, so I'm not in a big rush to change. But when I go to Microsoft's site to see what WS8 actually "does", it has a bunch of:

"Enhanced User Gratitude"

"Rich Widget Cloud Experiences"

"Enlightened Multi-client Symbiosis"

And other such rot.

Trying to figure out what it really does that peer-to-peer doesn't is perplexing. There must be SOME advantage to running server software.

 

[Poltergeist]

Normally you will run server software so that you can run server applications; exchange, sql etc. I don't know anyone that uses server just for file serving.

 

[Mike]

I see what you are asking now, sorry about that. Short of security ' work station admin control ' , additional supported hardware, stability ' Kernel ' and as Rob mentioned, software support I'd have to say forget 2008. Windows 7 Business, Professional and Ultimate all seem to be viable options for weeks on end stable time up. 7 versions all have issues of course but...

 

[GeneralTJI]

Other advantages of running Win Server would also include user/computer control via Active Directory, group policies etc. Not something you need from the sounds of it.

And I have my gripes with those "features" as well. Not to mention, the need to reboot Windows Server based software for almost all the same reasons you need to reboot a workstation. Win8 seems a little better but I can't believe how often you need to reboot server even when installing simple programs or updates. Sometimes you can manually restart the right service and avoid it but ... blah.. can be a real issue when you don't want a 'mission critical' server down for 15+ min.

I am a hardcore Windows guy overall, but I now have a LOT of Apple goodies (iMac 27, mac book pro 17, mac book air 13 (tune w/ it! kicks ass!), iPad, iphone4, iTouch etc. and am slowly making the switch as I find the right software to meet my needs...which can be a challenge)....

At work we have 1 Xserve and it's cool looking.. though I don't think we will be going to a mac based network anytime soon :rofl:

 

[Fingers]

There are very few features in Windows server that apply to the small-medium office. IMO. Now when you branch out and are trying to manage 100+ individuals and their 5+ machine each distributed over a 10 acre campus, blah, blah, blah. Yea, the centralized admin tools help as well as the seamless integration across multiple servers. All of which demands the full time attention of an IT supervisor of some sort.

If you need these features on a scaled down level, I would recommend something like SME which is Linux based. Painfully stable.

 

[Poltergeist]

Pat what exactly were you looking at using Server for?

 

[McRat]

Ideally, I want to isolate the CMM machine PC's from the internet (too risky) yet still allow them to access the fileserver and other non-CMM PC's.

It would also be cool to have just 1 seat of MS Office on the server, then have client licenses for each machine.

 

[Mike]

Ideally, I want to isolate the CMM machine PC's from the internet (too risky) yet still allow them to access the fileserver and other non-CMM PC's.

It would also be cool to have just 1 seat of MS Office on the server, then have client licenses for each machine.

You should be able to accomplish the security concerns with firewalls, hardware and software along with your Linux OS.

Are you wanting each work station to be a terminal? Basically dummy workstations with all processing being done on the server?

 

[DAVe3283]

Ideally, I want to isolate the CMM machine PC's from the internet (too risky) yet still allow them to access the fileserver and other non-CMM PC's.

It would also be cool to have just 1 seat of MS Office on the server, then have client licenses for each machine.

This should be pretty easy with linux. Just put 2 NICs in the linux machine, and run the CMM PC's from the 2nd NIC, and don't forward any internet traffic through the server. That way, most PCs can get on the internet, but the ones behind the linux server can't (or only sites/traffic you allow)... but they still can get all the files.

Since you've already got the linux box set up, I'd stick with that, it should do everything you need. I personally have WinServer 2008R2, and it works great; though I got a free license, I'd probably be using linux otherwise.

The main thing I love about it is the ability to run applications remotely (like you mentioned with Office). I run the GM Techline eSI program on the server, and I can pull that up from any PC on the network, and even from the internet if I need to. That is the perfect example of where Windows Server shines. The Techline system (at least my copy) is like 5GB, which is more than I want to install on every system. However, by installing it on the server, I can access it from any computer, without installing it or taking up space.

That being said, it is probably cheaper to get Office for the 15 computers (especially the Home & Office packs) than to set up a Windows Server with all the User CAL's and RDP CAL's you'd need. Microsoft is mighty proud of their server software. It is impressive if you need enterprise level management, but even then, it seems a bit expensive.

 

[jlawles2]

Using the 2 NIC interface is the easiest way, but what may be better than that is to look into layered switches. You can control internet access through the switch ports not user settings.

I might be able to get the IT guy at work to sketch a setup and explain if Windows server or a layered switch is the better option.

 

[Cougar281]

If going the NAS route, check out the Drobos (www.drobo.com). IMO, they blow away pretty much every other NAS device out there. I have a DroboPro attached to my server, which is more of a SAN than NAS, but they have other, lower models that are NAS devices.

Server software allows you to run server software such as exchange if you want, remote desktop, eliminates the 10 connection limit, and unless you get SBS
(which SUCKS!), never actually stops allowing connections based on number of CALs you have. It also allows centralized authentication, so you don't have to make sure all user accounts are the same (same username and password) on all machines in order to access any other machine. One thing to note though, you mentioned buying a copy of Office and installing it on the server to run in terminal services; you can't just buy one license unless one user will be using it at a time. Each simultaneus user needs a license of office on the TS.

 

[jlawles2]

Taked to the It guy at work.

If you just want to block the CMM's from the internet, you can do it through the router and DHCP. On most routers, you can set static IP's for the machines you want to have access to the internet, and block all other IP's traffic to the WAN.

If you use Server, the active directory can be used to limit access to specific folders on the network servers and also control access via a proxy server.

Not knowing the exact network equipment and setup you are using, it is harder to help you determine if you need Windows server or if you can get away with something else.

Depending on how much security you want on the CMM's and how much access you need from an office computer, it is possible to setup independent networks. Keep the CMM's and machining software on one network with shared storage, and the other for internet traffic. If a virus gets into the system, it is possible that it spreads to all machines from any one if they are in the same system. The IT group at work has spent a lot of time and money isolating individual offices but still keeping them connected. The last virus outbreak we had shut down the worldwide connection for over 1 week.