My installer may allow the user to create a local user account, providing a username and password.
However, if the user enters a new password that would fail password complexity requirements of the computer or domain, the install fails.
I would like to validate that the username and password will be correct for password policy early in the installer and allow the user to fix the problem, rather than failing later on.
I've found LogonInformationDlg and the "Check if user exists" custom action. These are great for confirming the user found and provided the correct password for an existing user. They also help the wizard offer the option of creating a user if the one they specified does not exist.
It seems like the only way I can do this is with a custom action that actually *creates* the local user, sets an error message if that failed, then *removes* the user so that AdvancedInstaller can perform its own built-in user creation after wizard dialogs are complete. Are there other options?