Article ID: 2810617 - View products that this article applies to.
Consider the following scenario:
This issue occurs because the required Windows Management Instrumentation (WMI) service stops during the installation process. The WMI service is needed to query Active Directory Domain Services (AD DS) to verify the Windows PowerShell script execution policy that must run as a part of the setup.
To avoid this issue, follow these steps:
(http://support.microsoft.com/kb/2808208/ )Description of Exchange Server 2010 Service Pack 3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To verify the execution policies before you begin the installation process, run the following Windows PowerShell cmdlet:
The output should resemble the following:
If any of the execution policies are set to a status other than Undefined, refer to the steps in the "Resolution" section before you install an Exchange Server update rollup or service pack.
For information about an issue that can occur when you run a setup and encounter an error, click the following article number to view the article in the Microsoft Knowledge Base:
2668686For information about an issue that can occur when you try to install Update Rollup 1 for Microsoft Exchange Server 2010, go to the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2668686/ )Error message when you try to install Exchange Server 2010 SP2: "AuthorizationManager check failed"
981474For information about an issue that can occur when you try to install an update rollup for Microsoft Exchange Server 2010, go to the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/981474/ )You receive error 1603 when you try to install the Exchange Server 2010 RU1
(http://support.microsoft.com/kb/2467565/ )You cannot install an update rollup for Exchange Server 2010 with a deployed GPO that defines a PowerShell execution policy for the server to be updated
Article ID: 2810617 - Last Review: February 25, 2014 - Revision: 3.0
Contact us for more help