VMware Horizon Community
rgb99
Enthusiast
Enthusiast
Jump to solution

Outlook Signatures and FSLogix

Does anyone know how to ensure Outlook signatures are saved in a non-persistent VDI environment? I don't know where to look or what to change. Office containers are configured with FSLogix via GPO.

Horizon 8.1.0
DEM 10.1
FSLogix 2.9.7654.46150
App Volumes 4.3.0.57

Thanks!

0 Kudos
1 Solution

Accepted Solutions
rgb99
Enthusiast
Enthusiast
Jump to solution

With the help of VMware Support, within DEM > Personalization > General > Applications

  1. Right-click Applications > Create Config File...
  2. Use an Application Template
  3. Microsoft Office 2016/2019/365 (select options)
  4. Name the file
  5. Finish

The config included many things, but the key was:

[IncludeFolderTrees]
<AppData>\Microsoft\Signatures

Earlier, I used LocalAppData, and that messed up Outlook at launch. Outlook and other O365 apps launched fine after this, and signatures persisted.

View solution in original post

0 Kudos
7 Replies
sscnc
Contributor
Contributor
Jump to solution

%APPDATA%\Microsoft\Signatures

0 Kudos
rgb99
Enthusiast
Enthusiast
Jump to solution

After I added that to DEM, Outlook popped with an error at launch. I don't think I can use a DEM Profile and FSlogix with Office.

"Outlook is using an old copy of your Offline Folder file (.ost). Exit Outlook, delete the .ost file, and restart Outlook. A new file will be automatically created the next time you initiate a send/receive."

[IncludeFolderTrees]
<LocalAppData>\Microsoft\Signatures

 

0 Kudos
praviview
Enthusiast
Enthusiast
Jump to solution

Here what you are achieving with FSLogix and DEM together, either you need to do a Profile Container or an office Container. If you opt for any of them then your signature will be saved on the FSLogix Container. 

 

Try disabling the Office From the DEM and clear the profile container and try to login.

Praveen C
L3admins.com
0 Kudos
rgb99
Enthusiast
Enthusiast
Jump to solution

I do not have Office configured in DEM because FSLogix is used. I only set up the application rule for the previous suggestion. It is now disabled since it triggered the error.

Here's the current policy.

Computer Configuration (Enabled) > Policies > Administrative Templates >
FSLogix
Enable search roaming: Enabled, Single-user search

FSLogix/Office 365 Containers
Enabled: Enabled
Enabled Enabled
Include Office activation data in container: Enabled
Include Office cache data in container: Enabled
Include OneDrive data in container: Enabled
Include OneNote data in container: Enabled
Include OneNote UWP notebook data in container: Enabled
Include Outlook data in container: Enabled
Include Outlook personalization data in container: Enabled
Include Sharepoint data in container: Enabled
Include Teams data in container: Enabled
Store search database in Office 365 container: Enabled, Single-user search
VHD location: Enabled, \\<dem_server>\DEM_Profiles\%username%\containers

0 Kudos
praviview
Enthusiast
Enthusiast
Jump to solution

just do some testing by making some customization to your outlook client by changing the theme or default size of letter something like that a do a sign-out from the VDI and  look at your FSLogix container and see is it updated with the latest time stamp, and login after 15 minutes and check is your changes made to Outlook is persistent or not on your new VDI session.

Above test only to make sure that FSLogix capturing your changes as expected.

make sure that you enabled Modern authentication ( ADAL) on your Golden Image.

 

 

 

 

Praveen C
L3admins.com
0 Kudos
rgb99
Enthusiast
Enthusiast
Jump to solution

The Office theme withheld after launching a new VDI instance, however the signature I created went away. I may end up creating a ticket with VMware.

0 Kudos
rgb99
Enthusiast
Enthusiast
Jump to solution

With the help of VMware Support, within DEM > Personalization > General > Applications

  1. Right-click Applications > Create Config File...
  2. Use an Application Template
  3. Microsoft Office 2016/2019/365 (select options)
  4. Name the file
  5. Finish

The config included many things, but the key was:

[IncludeFolderTrees]
<AppData>\Microsoft\Signatures

Earlier, I used LocalAppData, and that messed up Outlook at launch. Outlook and other O365 apps launched fine after this, and signatures persisted.

0 Kudos