Quick Tip: System Center Operation Manager R2 Beta “failed to lower Monad ExecutionPolicy security level…”

Those of you trying out the BETA of SCOM R2 may run into an error during installation telling you to search for “value 3″ in the setup log files.

Doing that may uncover an error along the lines of:

GetRegistyStringValue: RegQueryValueEx failed.. Error Code: 0x80070002.
SetRegistyStringValue: RegOpenKeyEx failed to open registry key. Error Code: 0x80070005.
SetMonadExecutionPolicy: Unable to lower Monad ExecutionPolicy security level..
Action ended 12:38:48: _SetMonadExecutionPolicy.E1C3A829_C8F3_443F_B5FE_0CE01DB47829. Return value 3.

The simple solution is to disable User Account Control.

Actually if you launch PowerShell and try the “Set-ExecutionPolicy RemoteSigned” you will also get an access denied on the registry when UAC is activated. Same cause, same solution.

PS: No, I haven’t turned into a System Engineer, still a dev. Might talk a bit about what I’m doing here soon…

Advertisement

1 Response to “Quick Tip: System Center Operation Manager R2 Beta “failed to lower Monad ExecutionPolicy security level…””


  1. 1 ven February 11, 2009 at 0:13

    Dude!!!
    How to disable User account control on a windows server 2003 which is in a domain ????


Leave a Reply

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

Gravatar
WordPress.com Logo

Please log in to WordPress.com to post a comment to your blog.

Twitter picture

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

Facebook photo

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

Connecting to %s




Subscribe / Search


XING

 

January 2009
M T W T F S S
« Aug   Mar »
 1234
567891011
12131415161718
19202122232425
262728293031  

Twitter

Blog Stats

  • 356,723 hits

Follow

Get every new post delivered to your Inbox.

Join 57 other followers