Thank you for your answer.
I fear I might have improperly explained what I wish to do.
Basically, I would like to reproduce the behavior of some service installer where the user can chose to use either one of several default accounts (well-known security principals like "Network services" or "system") or decide to use a custom one.
One example for this behavior is the installer for MSSQL server:
My problem isn't with the custom dialog design b ut rather with the behavior of the service installer. It shouldn't specify any password when using a well-known security pribncipal for the user.
Additionally, I can't find a way for IIS to use a domain\user for identity: I can only specify the user name coming from a property, not what domain should be used.
Thanks again
FOLLOW US
Get the latest news in Application Packaging