Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It obviously uses more memory (with the fancy themes), but from what I have ready, IIS7.5 is fully functioning. I use it for a dev server, but what about a full-on prod server?

share|improve this question
up vote 6 down vote accepted

Windows 7 Ultimate allows a max of 20 concurrent connections to any piece of software running on the machine. Not sure, but this may be lower for lesser editions of Windows 7. Go to Start | Run and type in winver, then scroll down to where it says Device Connections to see how many are allowed (by license) for your edition.

Based on this thread IIS7.5 has a limit of 10 concurrently executing requests, but no max on concurrent connections.

On top of that, your next biggest issue is running a production system on workstation class hardware. This is typically not recommended, although you'll need to gauge that based on your environment and your requirements.

share|improve this answer
A couple of notes. First is that winver doesn't say anything about maximum concurrent suggestions here (7 Ultimate x64), and second is that there is no Start->Run in Windows 7. You probably meant the search box. Also, client operating systems will run on server hardware. – fahadsadah Apr 27 '10 at 18:39
@fahadsadah: There is a Start->Run if you turn it back on. It's just turned off by default. Also, most people asking about running Win7 as a production server are probably running it on older consumer grade hardware too (might not be the case here, but commonly). – Chris S Apr 27 '10 at 18:47
Of course it's going to be tough to use up all 10 requests by yourself since client OSes are single user at a time by license. That's the reason yuo can switch users on windows xp and up but you can't remote desktop with more than 1 user – Jim B Apr 27 '10 at 20:10
This answered everything! Thanks. Looks like I won't be using 7 outside of dev. – Jeremy Boyd Apr 27 '10 at 20:13

The biggest pitfall is not technical. Running a production, multi-user IIS installation on Windows 7 breaks the end user licensing agreement and you are on very shaky ground legally.

share|improve this answer
Where exactly? Please can you quote the relevant portion? – fahadsadah Apr 27 '10 at 18:40
@fahadsadah Windows 7 EULA - "Unless otherwise provided in these license terms, only one user may use the software at a time." Clause 2.c in Enterprise; 2.d in Home versions. – Chris S Apr 27 '10 at 18:55
Thanks @Chris, go away for 10 minutes and you miss important stuff... – MattB Apr 27 '10 at 18:56
FWIW, Microsoft would be on very shaky ground legally to sue you claiming that making a HTTP connection to a process running on the software is the same as using the software. – fahadsadah Apr 27 '10 at 20:11
but is running IIS really allowing "multiple users access"? If it's running as a system process, it would seem as though to me that it's still just one "user" – warren Apr 27 '10 at 20:14

This should help, its for Windows Vista (i.e. IIS 7), but should be similar:

Seems that the main issue is the limit on concurrent network connections. The max for the edition that comes with Vista is 10. Windows server is unlimited.

Seems like you might also want to check:

share|improve this answer
This doesn't answer my question. It just links out to vista related article and the bottom link is old and doesn't have any news about windows 7. – Jeremy Boyd Apr 27 '10 at 18:15
Maybe not exactly, but it points you in the right direction. If the technical limitation in IIS 5.1 (Windows XP) and IIS 7 (Vista) was connection limits, its likely that the IIS 7.5 has similar issues, and would be something specific for you to research. – Randy Syring Apr 27 '10 at 18:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.