After applying Cumulative Update 2 for System Center Operations Manager 2007 R2, the OpsMgr shell may fail to open
After applying Cumulative Update 2 (CU2) for System Center Operations Manager 2007 R2, the OpsMgr shell may fail to open in environments with a code execution policy of “All Signed." The following errors are generated:
The following error occurred while loading the extended type data file:
Microsoft.EnterpriseManagement.OperationsManager.Client,
C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Types.ps1xml : File skipped because of the following validation exception:
File C:\Program Files\System Center Operations Manager 2007\Microsoft.En terpriseManagement.OperationsManager.ClientShell.Types.ps1xml cannot be loaded.
The file C:\Program Files\System Center Operations Manager 2007\Microsoft.Enterp riseManagement.OperationsManager.ClientShell.Types.ps1xml is not digitally signed.
The script will not execute on the system. Please see "get-help about_signing " for more details...
There were errors in loading the format data file:
Microsoft.EnterpriseManagement.OperationsManager.Client, , C:\Program Files\Syst em Center Operations Manager 2007\Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Format.ps1xml : File skipped because of the following validationexception:
File C:\Program Files\System Center Operations Manager 2007\Microsoft .EnterpriseManagement.OperationsManager.ClientShell.Format.ps1xml cannot be load ed.
The file C:\Program Files\System Center Operations Manager 2007\Microsoft.En terpriseManagement.OperationsManager.ClientShell.Format.ps1xml is not digitally signed.
The script will not execute on the system. Please see "get-help about_signing" for more details...”
Cause: The following files are not signed in CU2, thus causing this issue:
- Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Format.ps1xml
- Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Types.ps1xml
- Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Startup.ps1
We have confirmed this issue and a fix is scheduled to be released in a future update.
Workarounds: To workaround this issue you can do one of the following:
- Change the PowerShell execution policy to allow these files to be executed.
or
- If your security requirements don’t allow the execution policy change, you can copy the above files 3 from the R2 RTM installation and then apply the workaround to fix the previous known issue as per the following link:
José Miguel Constantino | System Center Support Escalation Engineer
Comments
- Anonymous
June 11, 2011
I like your website, also Knowing the calories in foods, will help you know how many calories you have consumed during the day. This will in turn, help you to maintain your calorie balance to reduce weight. http://www.caloriesforfood.com