I R teh IT noob. I mean, IT manager.
 

So, it's become increasingly apparent that my company is relying on me to build and manage our network, at least beyond what we already have, which is a handful of windows workstations plugged into the switches in the utility room. I've been asked to determine requirements for workstations, order them, install them when they arrive... and the same thing with a server. :eek: Also been asked to develop and implement data backup systems and procedures, as well as network file standards so all this hardware we're buying serves us worth a crap.

Point of the thread- tell me a couple books I can read to help me learn the basics of making Windows XP Pro computers talk to each other. Assume I know nothing about this stuff, because it's not far from the truth! The more I learn from outside sources, the fewer threads I'll have to post in the future about it. :p

Go to Barns & Noble...
Go to the computer self-help books section...
Pick any one of the 44,000 books on the subject...
Read for 5 minutes...
Realize that your life is going to totally suck...
Get a job that doesn't involve IT work...
Profit.

Yeah... did that. Except on Amazon.com. :(

While I was there I ordered the obligatory 'for dummies' book on networking. Hopefulyl that will teach me enough to at least narrow down teh next 3 books I have to buy to solve my immediate issues.

Learn to say the phrase, "It depends".
Them: "What kind of workstation should I get?"
You: "It depends."

Them: "Should I get Windows Vista?"
You: "It depends."

etc.
x10 on Scott's reply too.

IT is like a box of chocolates. You never know what you are going to get because nobody reads th F'ing descrip/instruc-tions.

I'd almost say web searches are a better bet than most books. Though networking for noobs will get you some terminology and other basics.

I like Mark Minasi's books on Windows.

You need to decide if you want to have a Workgroup or a Domain. M$ recommends a Domain for 10 or more computers, but you could have a Domain with 3 computers or a Workgroup with 20 or more computers before administration becomes a bitch.

I use Trend Micro Office Scan for AV and a combo of Ghost, a nifty batch file, WinZip, FTP, and hot swappable SATA drives that go off site with me every night to back up our entire network (25 computers) every night.

Workgroups are easy. Just make sure every computer has the same Workgroup name and after 30 minutes or so, they'll all show up in My Network Neighborhood. File sharing can then commence.

A domain is a bad idea with anything less than 2 physical servers acting as domain controllers. It also requires you to buy professional versions of windows. And I don't believe Kevin has any servers, so stick to a workgroup.

I've got a physical server coming next month. Well, 'server' I guess. It's just a desktop tht will be used as a file and print server basically. Almost never used as a workstation. I don't plan on doing anything complicated anytime soon. Everything in our office (including the incoming server) is on XP Pro. I'm not going to buy any dedicated networking software, and probably won't even go to Windows Server 2003 until the next server upgrade which is well over the horizon.

We've nearly reached the limit of physical space in this office for people, so I don't have to worry about expansion beyond maybe 10 total workstations until we move. I think our basic Windows networ isn't the absolute most efficient solution, but it's the cheapest and easiest and does meet our needs, which are print and file sharing and a better data backup solution than we currently have, which is nothing..

XP/2000 Pro only allows 10 concurrent connections...just as an FYI. This means you could have more than 10 computers that use the same shared printer and or/network accessed file on one XP/2000 machine as long as they don't all print/access files at the same time.

For backup solutions, check out Acronis.com. It's like Ghost but better since Symantec hasn't had their ham fist in it.

In essence, that's all a server really is. Just a computer dedicated to do server stuff. Well, technically a server is software and the hardware is computer (sometimes in a specialized form factor) that runs servers.

But, that's just an argument of semantics that I'm hoping to trap Dean in.

In an effort to conform with the SEECS goal to turn every thread OT...

All servers should be topless and drinks should be free.
http://www.maximonline.com/hotties/i...06/6206_L1.jpg

Because, if you trap Dean in a case of internet semantics, he might get distracted from driving fast this weekend.:lol:

Hey, does anyone who works in IT or systems at their company, have a tutorial or some type of training program that could be loaned to Kevin? I'm thinking books or tapes, or some type of "Learning Microsoft Networking" tapes or self-study kits, that I know alot of companies buy, use for one administrator,then shelve it.

Your link is b0rked Dean, but that's probably good since I am reading this from work...

Fixed but it is WS IMHO.

The problem is, most of these books that we have are geared toward Active Directory, something you can't use with a Workgroup.

Who let the horse in here? Quick someone feed her a carrot!