Our Global company is in the process of rolling out office 365 for the whole group. currently i am the only user in my location to start using office 365. I can create a new outlook 2013 profile for the office 365 account and it works well. Problem i'm having is after launching the new Office 365 profile outlook keeps prompting me for my local windows username and password. this only happens when i'm connecting to my local network. Our local exchange server is still in production and cant be removed at this stage as all my other 400+ users use it.
If i connect to my office 365 profile in outlook from another network this does not happen.
I created a new profile for outlook 2013 and this still occurs.
If i enter my credentials in outlook 2013 it downloads my local OAB instead of using the new Office 365 address book.
Current setup: Local Exchange 2007 server.
Office 2013 on windows 7 64bit
Microsoft employee here - sorry to hear about the difficulties you're having!
Can you answer these questions for me:
1. What specific Outlook 2013 version are you using? e.g. 15.0.4631.1000
2. Does the problem still occur if you set the ExcludeScpLookup Autodiscover reg value? Steps to do so can be found below:
a. Start regedit
b. Select reg key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover
c. Create a new DWORD value in this AutoDiscover reg key named "ExcludeScpLookup" (no quotes) with value 1
d. Restart Outlook and boot into your O365 profile
Note that #2 is not a permanent solution, just a troubleshooting step to determine where the issue might be occurring. Please delete that reg value after confirming whether or not the issue still occurs with it set.
Thanks!
Related
I have installed ADLDS in my Windows 10 (21H2) machine, we don't have any domain controller, the idea is to use AD LDS for user management in our Plant SCADA application. I am trying to create an OU via powershell cmdlets. But i get the following error:
New-ADOrganizationalUnit : Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
The same powershell cmdlets works fine with AD LDS instance installed in a server 2019. But i get issues when i run same powershell cmdlets in my windows 10 machine. When i checked the Server 2019 i can see there is a windows service "ADWS" running, but i don't find this in my windows 10 machine, so i am not sure if this is the issue as said in the error. i installed the RSAT:ADLS tools from optional feature, so couldn't figure out how to get this feature(ADWS) and get my cmdlets work in my windows 10 machine. ( i am able to create OU via ADSI edit, but the idea is we want to use powershell to automate) i would really appreciate if some one could shed somelight on this ( all my google search results are leading me nowhere :( )
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 have a MS Access 2003 Database which uses the command "CommonDialog".
In this Database has access many computers with windows 10 and Microsoft 365.
Some computers can work with no issue but some other appear the error:
"Object doen't support this property or method"
Do you know if there are any computer settings that can explain this behavior?
Microsoft has restricted the support of CommonDialog from Windows 10, build 1809 on.
You must switch to the FileDialog property. Unfortunately, you will need Access 2007 for it. Here is how to use the FileDialog:
https://support.microsoft.com/en-us/office/filedialog-property-8510b02d-e455-44a9-bf38-3787e6d5c8c1?ui=en-us&rs=en-us&ad=us
A customer of ours is using a kind of sharepoint (not sharepoint) -a document repository- that, for what I saw, uses webdav.
There are two terminal servers, one of them is Windows 2008 R2 Datacenter v6.1 build 7601, Office 2016, and Internet Explorer 10.0.9200.17609IS. They couldn't access anything at all, they went as far clicking "edit" on the site and then Word they that he's sorry because he couldn't open the document.
I've fixed that, I added the site to the Trusted Sites list, and disabled SSL 3.0 and TLS 1.0. Local admins can open and update documents. Non admin users can open the document but not update it, and by can't I mean that Word opens the document in read-only mode and any attempt to switch to read-write will save the document in the local computer.
Now, the other server, Windows Server 2012 R2 version 6.3 build 9600, Internet Explorer 11.0.9600.19867, the former fix did the trick for both admins and non-admins.
Does anyone know where to look?
Thanks,
Max
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.