![]() ![]() I should have mentioned this is in a VMware Horizon Instant Clone environment. ![]() So how do we manage to get Outlook 365 to connect to our on-prem Exchange server when installing it with the shared license option? We do not have a hybrid model yet and are not using Exchange online yet. We also tried manually adding the on-prem server by manually setting up an account in Outlook. There was mentioning of a different path in the registry somewhere (can't find the link anymore), but those paths did not exist in our registry either. However, that registry key does not exist in our environment. > HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\office\16.0\outlook\autodiscover We've already tried the registry fix mentioned here. configuration-Office365Shared.xml | Everything but Outlook not connecting to on-prem works fine as well.configuration-Office.xml | This one was used initially, everything works fine and Outlook connects to the on-prem Exchange without issues.From the How would you like to repair your Office Programs screen, select Online Repair to ensure everything gets fixed, and then select Repair. Right-click the Office product you want to repair, and select Change. The attached "ODT 365.zip" file contains the two files: Go to Control Panel, From Category view, under Programs, select Uninstall a program. ![]() However, after re-deploying it, Outlook just will not connect to our on-prem Exchange server but instead connects to Exchange online. Every time you run a PC, countless things happen in the background, and a temporary problem in any of those processes can prevent Outlook from connecting to the Internet. In an effort to switch to a shared licensing model, we are re-deploying Office 365 via ODT. Start with a simple restart Ask any tech guy or gal, and a restart is the first thing they’d recommend. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |