We're running into two issues with Windows users created by advanced installer are looking at how to address them.
Our installer creates a Windows user that is an administrator. That administrator is set to run a scheduled task that calls the updater program. We have that user set to be deleted if the software is uninstalled. On the custom action page that deletes the user we have Regular uninstall checked, and Replaced by a new version unchecked.
We've found that running the updater program as that administrator has the upgrader program downloaded and run by that administrator, and then the upgrade program is crashing. Running the updater program as any administrative user other than the created one works fine. My interpretation of this is that the upgrader program is deleting and recreating the user, and crashes as the user that is running the program has been deleted.
Another issue we've run into is at sites that have password complexity enabled. During the upgrade we receive an error message that the user does not meet the security requirements. Our interpretation is that the user is being deleted and recreated, and then windows complains that the password being assigned has already been used.
How can we prevent this uninstallation step from happening during an upgrade?
FOLLOW US
Get the latest news in Application Packaging