This is a great place to start. As the url signifies it is a library of W2K
server walkthroughs.
http://www.microsoft.com/windows2000/library/planning/walkthroughs/default.a
sp
You don't need to go to the office to reboot a machine when there is a
problem. You can just set up terminal services on the server and run the
terminal services client on your box at home. So that is the easy part.
Erik's right however, hosting stuff in house is a pain in the ass and if you
are the one in charge of it, you better be getting a raise. Going from CF
Architect to SysAdmin is what keeps tobacco companies in business.
http://www.microsoft.com/windows2000/downloads/recommended/tsac/default.asp
Running SQL and CF/IIS on the same box is a bad idea. Actually running SQL
on a box with anything but SQL is a bad idea. If you can afford it, put it
on its own box. Its a friggin RAM pig and will cause funky ass results in
your CF applications. SQL reserves RAM like crazy and isn't very nice about
giving it back So if you have to put it on its own box, make sure you go in
and confine it to a set amount of RAM and don't plan on using session
variables, because SQL has a bad habit of breaking out and spiking yer RAM
for no appearant reason.
----- Original Message -----
From: "Erik Voldengen" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 9:03 PM
Subject: RE: W2K Web Server
> There are some tutorials (viewlets) coming up at SecretAgents.com
> that cover things like setting up sites on IIS, stuff like that.
>
> I don't know of any white papers out there that describe the caveats
> of starting to host in house, but I'll sum it up the best I can for
> you.
>
> 1) Just use IIS. It works really well, and comes with W2K server
> 2) If you're going to use an enterprise level database, better put that
> on a separate box. Make sure that's running, too. Access is okay
> on the same box, but don't expect enterprise level performance with
> this configuration.
> 3) After IIS is running on the server (Test it) install CF server
> 4) Test your CF installation by setting up your datasources in CF
> Administrator
> (it will be in the start menu)
> 5) Bind as many IP addresses to the NIC as you think you'll need.
> Doing it up front saves you from having to reboot the server
> down the road. You can also set up multiple sites in IIS to
> use a single IP address (there's a viewlet on that coming up @ SA.com)
> 6) Set up your DNS. W2K has a DNS server built in. Hopefully
> someone knows a little about DNS in house. If not, O'Reily
> makes a great book on BIND/DNS. Microsoft also has a very
> in depth white paper on DNS using it's product. I myself just
> installed BIND on NT, but I don't think anyone else would or
> even should do that.
> 7) Set up your web sites in IIS (Also a viewlet for that on the way)
> 8) Don't forget to fudge the site properties for each site you create,
> making sure your usage logs are being put where you want them, and
> they are storing the data you need them to store.
>
> That's about all I can think of right now. Definately send me an
> email (to me, rather than the list) and let me know what you're having
> trouble with. I will write a primer, but I don't remember what
> was and was not obvious when I took the task on myself a few years
> ago.
>
> And one more note - hosting stuff in house is a pain in the ass.
> All of a sudden, someone needs to be able to come into the office
> to reboot the server, etc. And right when you have a deadline to
> hit, the server takes a big crap and you end up having to work on
> it for several agonizing hours. And if I had a nickle for every
> time a client called and said the statistics program was "frozen,"
> I would have about 4 dollars and 75 cents. Not that I'm bitter
> or anything... Just be aware it's not going to be a zero maintanance
> task you are taking on here.
>
> Again, feel free to email me off the list if you get stuck.
>
> Good Luck!
>
> -Erik Voldengen
> http://www.erikv.com
> scumbag independent contractor
>
>
>
>
>
>
> -----Original Message-----
> From: Brad Roberts [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 14, 2001 6:08 PM
> To: Fusebox
> Subject: OT: W2K Web Server
>
>
> I'm really in need of advice on setting up a web server. In the past I've
> always used an ISP so this is all new. We've got a Dell server with W2K,
> IIS 5, CF 4.5, and a dedicated internet connection to our ISP. I need to
> start hosting our sites in house. Does anyone know of a (beginners) step
by
> step guide to setting everything up? I don't want to go through our ISP
to
> set up domain names so I'm guessing we have to configure our server as a
> dns??? I need to transfer around 100 domain names to our server. Any
help
> would be greatly appreciated.
>
> FWIW, I've already read through the IIS docs with no good starting place.
>
> Brad
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
