Exchangemaster GmbH company logo

Exchangemaster GmbH - A Swiss IT Consultancy
Services
References
Partners
Contact
Getting Started
FAQs
Presentations
Articles
Community
Search
Popular
Tell-a-Friend
Follow Me

Follow exchangemaster on Twitter

Who's Online
We have 48 guests online
Syndicate
FAQ 000113 - PowerShell command failes to execute on a remote computer PDF Print E-mail
User Rating: / 20
PoorBest 
Written by Dejan Foro   
May 28, 2013 at 02:06 AM

This article applies to:

Windows Server 2008 R2

Exchange 2010 SP3

 

PROBLEM

When you try to execute a command the needs to execute on a remote server the following error is reported:

 

[PS] C:\Windows\system32>Get-OwaVirtualDirectory

Name                                    Server                                  OwaVersion
----                                    ------                                  ----------
owa (Default Web Site)                  EXCHANGE01                              Exchange2010
WARNING: An unexpected error has occurred and a Watson dump is being generated: Creating an instance of the COM
component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from the IClassFactory failed due to the following error:
80070721.
Creating an instance of the COM component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from the IClassFactory fail
ed due to the following error: 80070721.
    + CategoryInfo          : NotSpecified: (:) [Get-OwaVirtualDirectory], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.Exchange.Management.SystemConfigur
   ationTasks.GetOwaVirtualDirectory

 

CAUSE

 

An option is set in the Domain Controller Group Policy to deny NTLM Authentication requests.  

The option is found in the  Domain Controller Group Policy under

  Policies

    Windows Settings

       Security Settings

         Local Policies

             Security Options

                 Network Security:Restrict NTLM:NTLM Authentication in this domain - Deny all

 

 

SOLUTION

 

Setting this Option to Disable will remove the restriction and things will begin to work normally.

Do not forget to run gpupdate on the servers if you want the change to be applied immediately.

 

 

 

Last Updated ( May 27, 2013 at 03:44 PM )
<Previous   Next>