Having cleared all my IIS settings while installing DotNetNuke, I needed to re-install WordPress, or rather to make IIS work with it again. I used WPI. The install went fine, but I have a couple of notes or issues to report:
1. WPI said it would have to "install" MySQL, though MySQL was running the whole time. Maybe there needs to be a clearer way of phrasing that -- reconnect to MySQL? Update MySQL and reconfigure? Something like that.
2. In the WordPress part of the WPI install, I was asked for "Unique Key for Passwords, Unique Key for Secure Passwords, Unique Key for Authentication, Second Unique Key for Authentication". I've done a lot of WP installs by hand, so I was prepared to put in one unique key, generated at WP's secret-key API. I was surprised to need *4* of them, and even more surprised when the WP-generated keys weren't accepted due to too many unconventional characters. In the event, I took my WP-generated keys and just deleted the special characters that aren't on the top line of my keyboard.
I think the WPI needs to warn the user how many keys they're going to need, and there needs to be a link to an API that will generate one the system will accept -- preferably the WP secret-key API, since that's what we're used to using.
Once that was done, everything worked just fine. The WPI is definitely a *huge* improvement over the calisthenics needed to get WP working on IIS the first time.