I think you can do either or, I would setup NLB. I think that supports 4 servers. Bear in mind that NLB can bounce between sites so if your holding cookie/session type data you will need to hold that in case they bounce around servers.
If you have www.domain.com and then www.domain.com/site then as already mentioned ssl may/may not be an issue. Also, in iis the /site could be a virtual directory, or just a directory. Whereas a subsite.domain.com would have to be its own site within iis I believe. This offers flexibility such as which .dll's or scripts can run on the different sites, but if they are generally the same then it would seem like more management to keep making new sites and then having to go in and allow the same scripts/dlls/exe's to run the site have to be manually added. You could always make www.domain.com/site <http://www.domain.com/site%20point%20to%20subsite.domain.com> point to subsite.domain.com so maybe that would be better to start off and you could always change it. From: Reimer, Mark [mailto:[EMAIL PROTECTED] Sent: Friday, February 29, 2008 4:42 PM To: NT System Admin Issues Subject: Best practices in setting up a web site with IIS Hi folks, Question in setting up a website. We will be using IIS (this has been decided by others, and I can't change it). Should subsites be: www.subsite.ourdomain.com or www.ourdomain.com/subsite Which is better practice? We will be spreading across multiple servers, with each server hosting one or two subsites. If the latter, what the preferred way of setting things up so the subsite gets pointed to the right server? I know it's Friday. If you want to wait until Monday, that's fine with me. Have a great weekend. Mark Mark Reimer; MCSE, MCSA, A+ Windows Servers & Networking Prairie Bible Institute Box 4000 Three Hills, AB T0M-2N0 Canada 403-443-5511 www.prairie.edu <http://www.prairie.edu/> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
