Thanks for the write-up. It is a good review of the process.
I prefer to save the .ini file and call it from a small batch file so that I do not have to type all that stuff at the command line. If I save the config file with the rest of my installation files in the installation folder, I can map a drive to that installation folder, and call the setup executable with a switch that points to the configuration file. For this example, I map a drive V to the installation folder
echo Installing SQL SERVER 20xx...
I name the batchfile InstallSQL.bat, and open a command prompt with RUN AS ADMINISTRATOR option, and traverse to the correct directory/folder, and simply call the batchfile. Takes a little bit of setup, but it will save you keystrokes over time.