asked on
Why Get-OwaVirtualDirectory -Server servername | FL *auth* gives nothing on my Ex2010 ?
All user mailboxes are in Exchange 2007 together CAS, HT, etc.
I also have two Exch2010 servers -- one with only CAS while the other with CAS, HT, MB.
When I issue the following cmdlet on Exchange 2010 servers:
Get-OwaVirtualDirectory -Server servername | FL
It gives all details but anything about authentication as the following:
ClientAuthCleanupLevel : High
InternalAuthenticationMeth
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
ExternalAuthenticationMeth
No wonder the following two cmdlets give nothing:
Get-OwaVirtualDirectory -Server servername | FL *auth
Get-OwaVirtualDirectory -Server servername | FL *auth*
It makes me worry if there is something wrong in my Exchange 2010. Can you help?
I also have two Exch2010 servers -- one with only CAS while the other with CAS, HT, MB.
When I issue the following cmdlet on Exchange 2010 servers:
Get-OwaVirtualDirectory -Server servername | FL
It gives all details but anything about authentication as the following:
ClientAuthCleanupLevel : High
InternalAuthenticationMeth
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
ExternalAuthenticationMeth
No wonder the following two cmdlets give nothing:
Get-OwaVirtualDirectory -Server servername | FL *auth
Get-OwaVirtualDirectory -Server servername | FL *auth*
It makes me worry if there is something wrong in my Exchange 2010. Can you help?
Exchange
Last Comment
Castlewood
either you hit a bug or you don't have access to these value because a RBAC?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks. Found need to run as admin on EMS.