http://sqlblog.com/blogs/john_paul_cook/archive/tags/installation/default.aspxTags: installationenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/john_paul_cook/archive/2008/08/15/sql-2008-configurationfile-ini-file-not-just-for-unattended-installs.aspxFri, 15 Aug 2008 13:30:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:8397John Paul Cook9http://sqlblog.com/blogs/john_paul_cook/comments/8397.aspxhttp://sqlblog.com/blogs/john_paul_cook/commentrss.aspx?PostID=8397<P>Scripting installations of SQL Server 2008 is much easier than it is with SQL Server 2005 because of the <STRONG>ConfigurationFile.ini</STRONG>. Even if you don't script your installations, you should review the contents of this file to verify that the installation transpired as intended. Although it is possible to script a SQL Server 2005 installation, you can't capture an interactive installation and replay it. When&nbsp;SQL Server 2008 is installed, a <STRONG>ConfigurationFile.ini</STRONG> file is created in <STRONG>C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\<EM>yyyymmdd_hhmmss</EM></STRONG>. To use <STRONG>ConfigurationFile.ini</STRONG> with the installation wizard, select <STRONG>Advanced</STRONG> and <STRONG>Install based on configuration file</STRONG>. If you need to make changes to the file before performing another installation, it is a best practice to make a copy and work with the copy. From an auditing and compliance perspective, each installation's <STRONG>ConfigurationFile.ini</STRONG> file should be preserved in its original state as verification of the initial state of the SQL Server installation.</P><img src="http://sqlblog.com/aggbug.aspx?PostID=8397" width="1" height="1">SQL Server 2008installation