.\Matthew Long

{An unsorted collection of thoughts}

SCOM 2007 – Errors modifying automated agent installations manually with UAC.

Posted by Matthew on November 15, 2010

If you ever find yourself needing to modify or remove a SCOM R2 agent from a machine manually (The server is in the DMZ, or the SCOM console is unable to perform the uninstallation / repair) and the agent was originally installed via the SCOM Console, you may have issues if you have UAC enabled.

Scenario : You log onto the system in question, go to “Add / Remove Programs” or “Programs and Features” and you attempt to modify or uninstall the SCOM R2 Agent.  The MSI will launch and begin the operation but will quickly display an error message stating that there are missing ESENT Keys and that the operation cannot continue.

This occurs because the agent was installed in an Administrative context and the MSI is unable to detect that UAC is enabled.  When the installation runs in the user context those keys are missing and the MSI is unable to finish processing the changes to the installed product.

In order to correct this, you can run the below command from an elevated command prompt or powershell session :

msiexec /I{25097770-2B1F-49F6-AB9D-1C708B96262A

This will launch the SCOM R2 MSI in an administrative context and allow you to modify the product.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s