Previous Next

• 04-26-2007, 10:47 AM

  In reply to

  TheDean Joined on 04-05-2007, 1:52 PM Posts 43	Re: Information on Web Farms in IIS 7.0 Reply Contact I went through the msdn download center in the blog posts.... ...an ad the time of my posting i could see the download pages, but the download files where all 1gb big. That lslowly changed afterwards. Looks like the files needed to replicate or something.

• 04-27-2007, 3:05 AM

  In reply to

  steve schofield Joined on 06-10-2002, 8:54 PM MI Posts 2,581	Re: Information on Web Farms in IIS 7.0 Reply Contact Ahh I got them through connect.  I didn't check MSDN. Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget

• 04-29-2007, 5:14 AM

  In reply to

  TheDean Joined on 04-05-2007, 1:52 PM Posts 43

  Re: Information on Web Farms in IIS 7.0 Reply Contact I tried through the public download - seriously sucks. Terribly. I mean, getting a 1.8 / 2.5 gb file through a http browser request is like a lucky gamble. Especially when your speed gets down to like 25kb :-) Basically you can give up. This just is not sensible then :-) After a day (of unsuccessfull downloads) they also appeared on msdn - with more bandwidth and the nice download manager. Got the standard images (not the web edition, but I am not really interested in that one for now) within some hours. I am working on setting things up now - the server which did not work was ripped out of the hosting center on friday and goes back in tomorrow with beta 3. Then we will see how it works. On the topic of web farm config, btw. - I am disappointed. It looks like you can only redirect the configuration files. For me this turns the feature totally useless. * I can not keep all configurations in one place and ahve every web server filter out based on some criteria. What I would really love is one central configuration store. Every web server setup has the bindings, and the iis could then determine whether to load a website based on whether it canserve the ip address. After all, it can check local ip addresses. * I have a severe issue with the fact that ssl certificates are not part of the binding configuration. Basically it means I need to configure ssl certificates outside of iis config, which means - sorry - iis config is not useful. Please correct me on that. But at least for the central store I simply do not see it working with ssl. It looks likea nice feature if you need X identical web servers configured, but the moment they are not identical anymore it breaks apart. As most iis settings are now stored in the web.config anyway, and this is shared between all servers, there simply is not too much use for this central config store. Anyone feel free to enlight me on that and where I am wrong, please - I jsut see that with a decent control panel (that can then set up iis instances all around from it's databsase) the central store is just useless. And it does not handle all needs anyway (as I described above).

• 08-20-2007, 3:57 PM

  In reply to

  OWScott Joined on 08-12-2002, 1:25 PM Posts 57

  Re: Information on Web Farms in IIS 7.0 Reply Contact Hi TheDean, Your post is a few months out, but I just read it now and I thought I would reply, in case you still read this, or for future people reading this thread.There are many advantages to a shared configuration, and most of your objections have already been considered and addressed. The first goal is to make sure that you have a server neutral configuration.  You can do this by considering the following: System environment variables are supported in IIS7, so if you have different paths on each server, set the paths in system environment variables and use that in your configuration files.  (the same applies to other unique settings) Unused IP bindings are ignored.  So, your single configuration can have the IP bindings for all servers, all living beside each other.  Then, only the ones that are applicable will be used. If redundancy is a concern (and it should be on a webfarm), use DFS with replication for the configuration path.  Then if the primary server fails, you're not affected. With those in mind, shared configuration now gives you an opportunity to manage the entire configuration from any of your servers, knowing that it will immediately take effect on all of the other servers. As for SSL, you do need to manually install the certificate on all of your servers, but IIS will bind to the certificate properly as long as it exists.  So, after your once-only cert install, everything else will work perfectly.  That can all be scripted too. Thanks, Scott Forsyth