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…
Tales from the travelling tech founder 
Dude!!!
How to disable User account control on a windows server 2003 which is in a domain ????
I am also facing installation problem with error “value 3”
Action ended 12:01:34: _SetRootHealthService_Wizard. Return value 3.
Information 2896.Executing action _SetRootHealthService_Wizard failed.
Action ended 12:01:34: WelcomeDlg. Return value 3.
MSI (c) (D8:40) [12:01:34:846]: Doing action: FatalError
Action 12:01:34: FatalError.
Action start 12:01:34: FatalError.
Action 12:01:34: FatalError. Dialog created
Action ended 12:01:36: FatalError. Return value 2.
Action ended 12:01:36: INSTALL. Return value 3.
MSI (c) (D8:40) [12:01:36:299]: Destroying RemoteAPI object.
MSI (c) (D8:D4) [12:01:36:533]: Custom Action Manager thread ending.
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {26D71F0F-82B4-418B-96AC-BB9E54CED283}
Property(C): ProductLanguage = 1033
Property(C): ProductName = System Center Operations Manager 2007 R2
Property(C): ProductVersion = 6.1.7221.0