Cli php.ini is for your commandline based php (scripts, cronjobs, ...)
There should be another php.ini which is used by the webserver. Php (and those websites as ezpublish) runs as a sort of plugin in the webserver. Thus the webserver needs to have a php.ini too. In linux/debian you should have the following files:
/etc/php5/apache/php.ini is the one you need to edit for ezpublish. /etc/php5/cli/php.ini is the one for cronjobs, and common commandline-php scripts.
I don't know the locations on windows7 and IIS.
My guess is you hit the wroong php.ini. Utilize a simple php-test-script using "phpinfo();" (google it if you need help) to determine the exact location of the php.ini used by windows-webserver.
did you manage to put "phpinfo()" into a php file and called this php-file in your browser?
My guess would be that the vhost configured in IIS did not load the correct/corresponding php-ini. This in turn loads the default php-settings which is not sufficient for eZPublish.
My solution would be:
view php-info output via a browser, not cli
get the location of the loaded ini-file
edit this ini-file
reload webserver
check settings again
do loop until correct
As I dont have any experience with combination iis/php/ezpublish/windows i cannot help any further at this point. sorry mike.