hope somebody can help me as I'm banging my head against the wall with this one! I've read and researched as best I can but cannot find a solution.
I have an Exchange 2010 server. The active directory domain is example.com and all my users are like this: first.last#example.com.
However, I've set the URL in IIS for Outlook Web Access to https://exchange.example.net. (Notice it's a .NET tld), because I have site-wide SSL certificate for *.example.net.
This is my desired set up. It works great.
However, Autodiscover is causing me a problem in Outlook 2010 clients. About 30 seconds after opening outlook and after the connection to Exchange is established (successfully), I get a certificate warning telling me the certificate name does not match.
It pops up twice, first for autodiscover.example.com and then exchange.example.com.
I need to change the URLs to autodiscover.example.NET and exchange.example.NET.
PLEASE can somebody help me - it's driving me to despair!
Thanks,
Simon.
Open a ExchangeManagmentShell (Powershell with Exchange Extension) and issue this command:
Get-ExchangeCertificate |select -ExpandProperty CertificateDomains
Can you see your domainname in the output?
Related
I have an Outlook Web Addin, running in O365. This is currently hosted at my first server. (oldserver.domain.com)
I wanted to change the address the addin calls, so I changed all Urls in the Manifest file to (newserver.domain.com)and uploded it via the Microsoft 356 Admin Center. The new manifest was accepted, but the Addin is always calling the oldserver.domain.com. Since these updates sometime take a while to finish, I waited for the next morning.
I found this:
How often does the Outlook exchange server pull the web-addin manifest if they are "sideload" installed via URL
With this description it should already work. How can I get my addin to call the new url?
The changes may take an effect in up to 24 hours, not just next morning. You can find the following statement in the Deploy add-ins in the admin center article:
Outlook add-ins can take up to 24 hours to appear on app ribbons.
Sometimes it is necessary to enable and disable the add-in (multiple times) from the Office 365 admin center.
I've been chasing this problem around for a while now and I can't get to the bottom of it. I've read the other solutions on here (https://identityserver4.readthedocs.io and https://github.com/IdentityServer/IdentityServer4.Quickstart.UI) and it's still not working, so I've tried to reduce this down to the absolute basics. This is not the actual problem I am facing, but produces the very same outcome. i.e. I can't get Windows Authentication to work.
I clone https://github.com/IdentityServer/IdentityServer4.Samples
I amend Quickstarts/7_JavaScriptClient/src/QuickstartIdentityServer/Quickstart/Account/AccountController.cs so that WindowsAuthenticationEnabled is true
I then goto http://localhost:5000/account/login and attempt to use the Windows external provider and I get 401.
The only difference with this simple sample here, and what I see on my actual system is that I'm getting challenged for credentials on my real site.
Debugging the code I never see if(HttpContext.User is WindowsPrincipal) succeeding, because it's always a ClaimsPrincipal.
Can someone explain to me what I'm doing wrong?
Do you have windows authentication enabled on your IIS site? This needs to be enabled for your WindowsPrincipal to be assigned. Note that windows authentication only works when running behind IIS or IIS Express.
I followed the documentation on https://support.office.com/en-ie/article/Deploy-Office-Add-ins-in-the-Office-365-Admin-Center-737e8c86-be63-44d7-bf02-492fa7cd9c3f to publish a created addin to our users. Unfortunately it is not showing up when users check out their Add Inns ( I see a caption Office 365 / Managed by admin but no selectable addin.
I tried:
Restarted MS Word
Logging in and out from MS Word does not help.
Removing the add in and adding again (through file or URL both not work)
Any ideas?
We seem to have the same issue; If you intercept the HTTPS traffic (by Fiddler for instance), do you see a 500 response to the 'POST /ews/exchange.asmx' with the body containing 'GetPrivateCatalogAddIns'?
So far, this seems to be an issue with Exchange internals. We've been trying to get into contact with Microsoft about the issue. Here you can find the StackOverflow issue we have filed, and Here you can find the question on the MS fora.
EDIT: It was confirmed that this was indeed an internal problem. We have removed our deployed plug-ins and added them again. The call now responds with a 200 and everything seems to be working again.
Unfortunately, we also found out that there is an issue with the Add-in registration interface in the Office 365 Admin Centre, as people who are not full administrator but User management administrator instead can no longer upload Add-ins due to an Exchange credential error. A Office 365 Administrator however can and this seems to be working with us.
Today I had a support engineer of Microsoft on the phone about my case and they resolved the issue. I can deploy add-ins again.
To whom it may respond to,
We have deployed a web service to Windows 2003 Server SP2 , .net framework 3.5 .
"The service is not running , we are getting the error :
The website declined to show this webpage
HTTP 403
Most likely causes:
•This website requires you to log in.
What you can try:
Go back to the previous page.
More information
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help."
We have played around with the permissions but the situation didn't change a bit.
We would be very glad ideas on it,
Thank you for your concern,
Best Regards,
Kayhan YUKSEL
Make sure you have aspnet_isapi.dll as your wildcard handler in the Virtual Directory setup. Properties --> Virtual Directory --> Configuration --> Insert... --> aspnet_isapi.dll, make sure you uncheck Verify that file exists.
I have installed Powershell V2 on 2 machines and run Enable-PsRemoting on both of them. Both machines are Win 2003 R2 and are joined to the same active directory domain and I can successfully run commands remotely. So PS remoting is working between the local server and remote server.
But when I try to access a share on a 3rd server (dir \someOtherServer\builds), which is also Win 2003 R2 and joined to the same active directory, I get the error:
Get-ChildItem : Cannot find path '\someOtherServer\builds' because it does not exist.
So what does it take to get this "hop" to work? Is it the delegation settings (in the active directory) to the remote machine? Are there any settings that can be done when creating a PSSession that will make the hop to work?
I addressed this issue for Workgroups in a blog post. I think the info should apply to domains but I haven't tested in a domain. Anyway, see if it helps. FYI, the solution involves Enable-WSManCredSSP and the Authentication parameter to Enter-PSSession.
It's can be many causes of that. If kerberos auth, check the time on all servers. It must be sync. It may be DNS resolution problem. Need more detailed problem description/
Sorry fo bad english :). If something wrong, please correct me :)