OK, that's because I messed up (recall my smarta$$ "user error" comment). Looks like the config.xml file that needs to be edited is located in the WebDesigner.WW directory. I made a copy of the original and then dropped mine in, overwriting the original. I am no longer pestered for the product key but still have a dialogue or two to get past. Right now I'm getting prompted to install or customize the install. I'm still poking around.
I thought my previous method worked, but in retrospect I was probably just installing/uninstalling on a single machine and leaving behind data in the registry. I need to get this working on a clean install soon myself, will post back with any results.
The ONLY information I could find re this topic was
HERE. Looks like the config.xml file might need a reference to an .msi /q combination to install silent?
Edit: Looks like that's the config.xml file to be working with: I can enter the product key, user and company name, bypass the EULA, etc., but I keep getting stopped by the "Install Now/Customize" dialogue. Guess I could AutoIt . . . but it would be nice to .xml the whole show.
Edit/Edit: I punted and went with AutoIt (too easy). I edited the config.xml script found in the WebDesigner.WW directory as per above and then ran the following script from the root directory:
CODE
Run( @ScriptDir & "\setup.exe")
WinWaitActive("Microsoft Expression Web", "" )
Sleep(2000)
Send('!i')
Sleep(5000)
ProcessWaitClose('setup.exe')
Here's my script, place it next to setup and run it:
COMPILED SCRIPTIf you encounter issues, use Task Manager to kill the "install.exe" process and PM me with any gripes or suggestions.
The script runs setup without any switches (it's looking to the config.xml file in WebDesigner.WW by default, so please ensure it has been edited as per above) then waits for the Install/Customize dialogue. When the dialogue appears the Install button is clicked after a two second delay. The script next pauses for five seconds to ensure that setup has begun, then waits for setup to finish before exiting. There are four (4) Office 2007 critical updates related to the Expression Web install as of this writing that get installed along the way by extracting the .msp file from the update and placing each in the "updates" directory (KB934391, KB934062, KB932080, AND KB934393). You need to implement that. Works just fine now, if you don't mind the default installation.