Automate IIS and Web Service installation (repost)

We need routines developed that can automate the installation and configuration of IIS so that a non-technical user can easily get an ASP.NET Web Service implemented. We’re not sure if this requires a Windows script or program code or a combination of both. The routines need to work on a variety of Windows platforms and with IIS 5, IIS 6 and IIS 7. They need to accomplish the following tasks with the minimum of user interaction. 1. Add IIS to the Windows features (if not already configured) 2. Check to make sure that ASP.NET latest version is already installed, if not, install it. (ASP.NET installation package should be included in the package in this project. The user should not need to download a copy from Microsoft site.) 3. Configure IIS for ASP.NET support (2.0) 4. Create specific virtual directory and web site folders (folder names will be supplied) 5. Copy our published Web Service folder into the IIS virtual directory 6. Configure default documents 7. Configure read/write permissions for IIS on specific application folders (again we will provide folder names) This is not an exhaustive list. This job needs someone skilled in configuring IIS for ASP.NET applications and who is able to advise on best practice and likely pitfalls that need to be catered for. Also, kindly notice that this whole installation and configuration process should fit as one part of a bigger installation process. In other words, there is an installation package, during or after which, the processes carried out by this project should be called to launch. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Saturday Feb 6, 2010 12:04:56 AM: Further explaination For Points 2 and 3 2 - Windows server 2003 and Windows XP mostly come with ASP.NET version 1.x. Currently, it is version 3.5 in the market. So, the installer should check to determine what version of ASP.NET framework is installed. If it is 3.5, then the installer should not do anything and simply proceed to the nest step. However, if the latest version is found to be less than 3.5, then the installer should install ASP.NET version 3.5. When doing that, ASP.NET 3.5 installation files should be included in the same installation package for this project. The user does not have to connect to Microsoft site to download ASP.NET 3.5 installation files. 3 - Even after installing the latest version of ASP.NET, IIS (whatever version is there) does not automatically detect it. Virtual directories created in IIS will still use the old version of ASP.NET. We need to automatically configure IIS to assign the latest version of ASP.NET to all of the new virtual directories created in IIS. ## Platform windows