I'm having the exact opposite issue reported here in another topic.
After performing a pretty standard installation, the installer triggers a custom action of type "EXE with path given by a Property". This EXE is the commando prompt with the following parameters:
/C ""[#post_instal.bat_1]" "[APPDIR]" [SERVICE_USER] [SERVICE_PASSWORD]"
that is, a bat script that performs some administrative actions, such as creating a new user, setting its password and managing a couple of services.
When I perform this installation on a Windows XP or Windows 7 in which the UAC is disabled, everything runs smoothly. However, if the UAC is enabled, it looks like the process triggered by this custom action doesn't inherit the elevated privilege given by the initial "OK". Everything fails with an "Access Denied" erro message.
I've tried to avoid using and external script, but have run into many other issues that I'll try not to bring to this specific topic. So, how can I check what's going on and fix this issue?
This little thing is driving me insane because we're way delayed of our schedule and there's simply nothing else we can think of doing.
FOLLOW US
Get the latest news in Application Packaging