First off, this is a great start for helping centralize installs of the various 'web' products, both developer and IIS related. Few observations.
1) this worked good at my house although .NET 3.5 sp1 wasn't installed and rebooted during the install of everything, I'm not sure if stuff actually finished. It was like the 3rd or 4th item that installed.
2) What about offering this type of thing, 'behind the firewall'. When we stage IIS servers, we want to automate deployment of certain modules, components etc. If we could use this and have the source local to the network vs. having the need to go out to the web to grab files. I guess having them on the web is 'in the cloud' computing, but I can see making the source either on the web or local. Other products like WSUS, service packs allow for offline install support.
3) When deploying certain updates, allow us to 'resume' after necessary reboots like .NET 3.5 sp1. I'm not sure this will ever be 100%, but for stand-alone installs, this tool fits perfectly. If you want me to post the install log from my local machine, let me know.
Keep up the great work, hope this helps.
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield
http://www.IISLogs.comLog archival solution
Install, Configure, Forget