Install and configure phpMyAdmin on IIS
Creating you phpMyAdmin config file
First thing to do is to create your config file. To do this the easiest way is to copy the config.sample.inc.php file in you phpMyAdmin root directory and rename it to config.inc.php. Using this sample config file as a base means there are literally only a handful of settings that need to be added or altered so that you have a working configuration. Of course there is a lot more you can customise once you get more comfortable using phpMyAdmin. Now to the settings;
$cfg['blowfish_secret'] = '';. In this guide we will be using cookie authentication which requires that you set a pass phrase which is used to decrypt your browser cookies. Keep this as secure as you can by using upper and lowercase, and even make it alpha numeric for good measure. You will not have to remember this pass phrase once set, but don't over do it as it has a limit of 46 characters.
$cfg['Servers'][$i]['controlpass'] = 'pmapass';. This is the password used by the phpMyAdmin account used for all kinds of MySQL administrative functions, so it is a very good idea to change this to something other than the default. Again, you won't have to remember this password, so try and make it a strong one using upper and lower case with a mixture of alpha numeric characters. While you are here, you'll need to remove the double forward slashes (//) from all the configuration directives that are used for the phpMyAdmin user and database. This includes lines 37 through to 48.
$cfg['UploadDir'] = '';. This option allows you to specify where SQL scripts uploaded by users are stored. What I'd suggest you do is create a directory in your phpMyAdmin root directory called "user_data" or similar, and then make sure it is writable by IIS. To do this right click on the directory you just created, select properties and select the security tab, then click the add button and enter IUSR_COMPUTERNAME, where COMPUTERNAME is the actual name of the computer you are working on. Click OK to add the user and then select the read and write permissions with the IUSR user selected. Click OK again to apply the permissions. If you are setting up phpMyAdmin for a multi user environment, then it would be very advantageous for you to be able to seperate user uploads into their own directories. To do this, manually create a directory inside the main upload directory for each user, and then you can use the %u variable so that phpMyAdmin automatically redirects users to their own directories. For instance, using this %u variable this upload directory directive would look something like $cfg['UploadDir'] = 'user_data/%u';.
$cfg['SaveDir'] = '';. This directive specifies where SQL export files are saved when using the "save on server" option in phpMyAdmin. You can set this to a separate directory, but more often than not I find it more convenient to set this directive to exactly the same as the upload directory above. The reason for this is when you go to import a SQL file you have an option to upload the file, or select a file from the upload directory. Working with large databases will almost always mean you are limited by you PHP environment when uploading SQL files as you maximum file size is limited to the PHP max post size setting, and also the PHP maximum script execution time. However if the save directory is the same as the upload directory and you are using the %u variable, then when you export a database to an SQL file and save it on the server it is already in your upload directory ready to be imported, and by using the %u variable means that you'll only ever see your own SQL export files. One last piece of advise here is that when compressing your SQL export file (which is a very good idea), be sure not to use zip. This is because zip is processed all in memory and you run the risk of hitting your PHP memory limit, not to mention loading your server. If you use the gzip option, then compression is done on the fly. I've found gzip usually gives better compression results anyway.
With these main phpMyAdmin configuration directives set, then you can simply copy and paste these directives under the save directory setting;
$cfg['docSQLDir'] = 'docsql';
$cfg['ShowPhpInfo'] = true;
$cfg['ShowChgPassword'] = true;
$cfg['AllowArbitraryServer'] = false;
$cfg['LoginCookieRecall'] = 'something';
$cfg['LoginCookieValidity'] = 1800;
$cfg['AllowAnywhereRecoding'] = true;
$cfg['DefaultCharset'] = 'iso-8859-1';
$cfg['RecodingEngine'] = 'iconv';
$cfg['IconvExtraParams'] = '//TRANSLIT';
$cfg['GD2Available'] = 'yes';
$cfg['CheckConfigurationPermissions'] = FALSE;
$cfg['Servers'][$i]['hide_db'] = '(information_schema|phpmyadmin|mysql)';
From here you should actually be able to log into your new phpMyAdmin installation by entering the root username and password into the login screen of your phpMyAdmin installation URL. Might be a good idea to do that now to make sure everything is going to plan. be aware that there will be a good many features not available until we complete the install.