pfarber22
asked on
Syntax for Set-OutlookProvider command in Exchange 2007
Some of my external Outlook 2007users is prompted for their password multiple times. It happens to both domain and non-domain computers that are using Outlook Everywhere option. The Exchange 2007 server is in the Essential Business Server environment where Microsoft TMG with a wild card certificate is the front-end Exchange server. As part of the troubleshooting process, I want to follow up on "Wildcard Certificate Causes Client Connectivity Issues for Outlook Anywhere Microsoft" article (http://technet.microsoft.com/en-us/library/cc535023.aspx)
My question is: "What is the correct syntax to setup a Set-OutlookProvider command, Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.contoso.com as indicated in the main article
or
Set-OutlookProvider -Identity EXPR -CertPrincipalName *.contoso.com like indicated in the comments"
One more. Should I be doing the same change to EXCH (Set-OutlookProvider -Identity EXCH -CertPrincipalName *.contoso.com)?
My question is: "What is the correct syntax to setup a Set-OutlookProvider command, Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.contoso.com as indicated in the main article
or
Set-OutlookProvider -Identity EXPR -CertPrincipalName *.contoso.com like indicated in the comments"
One more. Should I be doing the same change to EXCH (Set-OutlookProvider -Identity EXCH -CertPrincipalName *.contoso.com)?
In my notes I have this:
Set-OutlookProvider expr -CertPrincipalName:"msstd:
Therefore you would change it to the * variant.
Although your best option would be to switch to a SAN/UC certificate as a wildcard isn't really suitable.
If you want to use the UM role then you must switch to a SAN/UC certificate.
Simon.
Set-OutlookProvider expr -CertPrincipalName:"msstd:
Therefore you would change it to the * variant.
Although your best option would be to switch to a SAN/UC certificate as a wildcard isn't really suitable.
If you want to use the UM role then you must switch to a SAN/UC certificate.
Simon.
ASKER
So, whoever added a comment to a Microsoft article was wrong?
Comments on the Microsoft articles are often wrong. I ignore them.
It isn't clear what comment on what article you are referring to, so I cannot say for sure whether it is incorrect or not.
Simon.
It isn't clear what comment on what article you are referring to, so I cannot say for sure whether it is incorrect or not.
Simon.
ASKER
This is from my question:
My question is: "What is the correct syntax to setup a Set-OutlookProvider command, Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.contoso.com as indicated in the main article
or
Set-OutlookProvider -Identity EXPR -CertPrincipalName *.contoso.com like indicated in the comments"
My question is: "What is the correct syntax to setup a Set-OutlookProvider command, Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.contoso.com as indicated in the main article
or
Set-OutlookProvider -Identity EXPR -CertPrincipalName *.contoso.com like indicated in the comments"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It took a long time to get to the correct explanation
Reason 1: Wrong Autodiscover Service settings
Reason 2: Wrong certificate
Reason 3: Wrong permission settings on the EWS virtual directory.
Reason 4: Logged on with another user account (user logged into pc with a different domain than email account ie logged into to PC as MICHAEL\Rich and logged into email server as Richard\Mike)
See the link below for detailed screen prints and documentation that will resolve your issue.
Usually is the reason 3 or reason 4, even though everyone points to the autodiscovery issues.
http://www.proexchange.be/modules.php?name=News&file=article&sid=686