robinsonjl3
Enthusiast
Enthusiast

Horizon and Outlook 2016 Problem

Jump to solution

I am currently testing Horizon 2103 with a Window 10 1909 image.  Office 2016 is installed on the image.  I am also using DEM.

The issue I am having is that I cannot launch Outlook.  Depending on whether or not Cached Mode is enabled gives me a different error.

With Cached Mode off, I get this error:

Cannot start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened.  The attempt to logon to Microsoft Exchange has failed.

With Cached Mode on and not redirecting the OST:

Cannot start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened. Your profile is not configured.

With Cached Mode on and redirecting the OST to DEM User Profile share or App Volume Writable:

Cannot start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened. The file is not an Outlook data file.

I have Googled and Googled which is why I have tried both redirecting the OST to the DEM User Profile share and also trying App Volumes Writeable Volume as those seem to be the most common solutions I found.

The funny thing is, in my lab, this works fine by just redirecting to the DEM profile.  In production, this is the problem.  My only assumption is there is a GPO in production that I don't have in the lab that is causing the problem.

Does anyone else have any other ideas of what I can do to fix this?  Would creating an App Package be a better solution or will I hit the same wall with the OST?

0 Kudos
1 Solution

Accepted Solutions
robinsonjl3
Enthusiast
Enthusiast

I had meant to post a follow up to this a while ago but forgot about it.

 

I ended up opening a support ticket with VMware and this is what they told me to do which fixed the issue:

 

On the master image, go to the following key in the registry:  HKLM\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator

 

Delete everything but the (default) key

 

Reboot the master image and test Outlook.

 

Once I did this, I refreshed the desktop pool and all was good again.

View solution in original post

3 Replies
sjesse
Leadership
Leadership

What happens if you disable the writeable, there is a localdata microsoft folder that causes I think the writeable is saving

0 Kudos
robinsonjl3
Enthusiast
Enthusiast

With the writable out of the equation I still get the same errors. 

I literally just finished setting up the writable and tested it 30 minutes ago.  I'm at my wits end as I'm on a time crunch to get VDI up for a few users.

 

Prior to using the writable I was just using DEM, same issues.

0 Kudos
robinsonjl3
Enthusiast
Enthusiast

I had meant to post a follow up to this a while ago but forgot about it.

 

I ended up opening a support ticket with VMware and this is what they told me to do which fixed the issue:

 

On the master image, go to the following key in the registry:  HKLM\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator

 

Delete everything but the (default) key

 

Reboot the master image and test Outlook.

 

Once I did this, I refreshed the desktop pool and all was good again.