As I export a server config using the Web Deploy GUI, what parameters ought I skip, those that hold the bindings? I'd like skip those and then export the rest with a password.
I got a recommendation that when creating additional servers in a web farm that one can avoid machine key issues if one uses the web deploy GUI to export a server configuration with a password. Since I'm not building hundreds of web servers, maybe only a few, this seems to work, so I'd like to continue with the GUI for now--it works. Mostly.
On importing a config built from the master, the master server bindings are carried into the new server, and it's a bit of a pain to reset on 10+ bindings that used to be okay.
Does anyone know which parameter holds the bindings, without messing with the machine keys?