When using the CheckIfUserExists Custom Action, if the given USER_NAME is found within the system's default domain, it appears that the DOMAIN_NAME property is ignored (AI_USER_EXISTS = "Yes").
I am attempting to allow the user to configure what User Account should be used to run a service by setting `Services To Install -> <My Service> -> Account -> Username` to [DOMAIN_NAME]\[USER_NAME] having used CheckIfUserExists to validate the credentials provided. Because CheckIfUserExists doesn't always validate the DOMAIN_NAME, it is possible for the user to input an incorrect DOMAIN_NAME which will pass my validation but then fail when the service is installed. Is there an alternative way to solve this problem?
FOLLOW US
Get the latest news in Application Packaging