Little Server Guy -
Info from a Guy Trying to Run a Little WS2003 Server on the Cheap
I think I've read 1000 times in help forums that "you get what you pay for." Translation:
"I only know one way to do this and it involves spending a lot of money." Ok, that's
one answer.
My objective is to overcome that mindset, and run a Windows Server 2003 server without
spending a lot of money. I'm just a little guy (in both the technology and business
sense), but I'm persistent. I've already faced some problems, overcome some of them,
and want to overcome the rest. My objective here is to make my experience available
for any other little guys out there who might benefit. And I mean "guy" in the midwest
sense, so if you're female you're still included in that.
Disclaimer: I reserve the right make my own stupid mistakes and be responsible for
the outcome, so you do that too. It's ok if you want to follow my lead and make
the same mistakes, just don't ask me to be responsible. Like I said, I'm just a
little guy. And, this is free, and as we all know, well, you get what you pay for.
Also, I'm a firm aherent of the 80/20 rule, and spell checking falls
in the 20% I don't sweat too much. My brain works faster than my fingers, so if
you find words missing, you can just fill them in. I actually AM a writer, but I'm
not trying get an A in composition; just convey some information.
I've cleverly put a nav bar up top with a few things on it. Multi-homing is my pet
beef right now so that will be first. Licensing, gateway filtering, virus checking,
backup, and even hardware might come along if I'm motivated.
Enjoy.
Richard
Comments? Combine the word "richard" with the words "server guy" with no spaces
or punctuation and stick it in front of the domain this page is hosted on. That
should get an electonic message to me.
(c) 2006 Richard Skerritt