
In a verbose log you’ll see the following line MSI (s) (B0:04) : Executing op: ActionStart(Name=res.exe,) A Custom Action named ‘res.exe’ is used to configure the RES service with the specified datastore connection.
#RES WORKSPACE MANAGER UNATTENDED INSTALLATION INSTALL#
Install will run elevatedĬustom Actions are used in Windows Installer to launch executables that are on the local machine or installed by the installation. MSI (s) (B0:04) : MSI_LUA: Elevated credential consent provided. MSI (s) (B0:04) : MSI_LUA: Credential Request return = 0x0 In a verbose log you’ll see the following line MSI (s) (B0:04) : MSI_LUA: Elevation required to install product, will prompt for credentialsįollowed by the following lines after the user confirmed. Since the installation makes changes to the computer, elevation is required and the user is prompted by UAC. The user interface that’s shown to the user (of hidden when running unattended) runs in the users context with a filtered token (without administrative privileges). Windows Installer is used to install RES Workspace Manager Agent (.msi extension). In the environment where I’m setting up RES Workspace Manager UAC is enabled with the default policy (notify only when programs try to make changes to the computer).

The user needs to confirm to run the process in elevated mode (and specify credentials) in a UAC prompt. The administrative privileges are only available when a process is ran with elevated permissions. When UAC is enabled (introduced since Windows Vista) a user has a token with only basic privileges, administrative privileges are filtered (removed).

PS: This applies for both SR2 and SR3 ( release notes ).

As a result the agent is unmanaged.Īfter extensive testing I found the solution to solve this issue. When RES Workspace Manger 2012 is installed unattended and configured to connect to a Relay Server, and User Account Control (UAC) is enabled, the configuration is not stored.
