JonAmadori's Posts

Thanks to the suggestion about the overzealous image optimization I took a look at our master image and found that our cleanup script we run before sealing the image had a typo which ended up deletin... See more...
Thanks to the suggestion about the overzealous image optimization I took a look at our master image and found that our cleanup script we run before sealing the image had a typo which ended up deleting the Downloads folder for all accounts instead of just clearing their contents.  This caused the default profile to not have a Downloads folder and when a user profile was spun up from the Default profile it also had no Downloads folder at the time DEM processed. Recreating the folder in the base image, modifying our script to not delete this folder, and recomposing the pool resolved the issue for our test users and will be pushed to production. Thank you for the help in finding what I overlooked.
@DEMdev we are using a local profiles for our users which are created from the default profile on the master image.  We then roam the profile with FSLogix, but did so in our previous Horizon environm... See more...
@DEMdev we are using a local profiles for our users which are created from the default profile on the master image.  We then roam the profile with FSLogix, but did so in our previous Horizon environment as well. I did run the VMware OSOT on the master image and it could very well could have been something in there which is causing the mapping problem, but I have only found this KB: Folder redirection configured by UEM does not show the redirected location (2150264) (vmware.com) talking about a setting in the OSOT which can cause redirection issues but that settings was not optimized in the base image and I have verified the registry key exists.
Hello, I have ran into a strange issue and thus far VMware support has been unable to resolve this issue. We recent migrated all of our users to a new Horizon cluster using Win 10 20H2 Enterprise f... See more...
Hello, I have ran into a strange issue and thus far VMware support has been unable to resolve this issue. We recent migrated all of our users to a new Horizon cluster using Win 10 20H2 Enterprise for our base image and running DEM 2009.  We use the DEM Folder Redirection setting to redirect the following folders/locations to a file share: Documents, Downloads, Music, Pictures, Videos, Desktop, and Favorites.  On first login to this environment, or first login after the user had their profile reset all of the folders will map properly except for the Downloads folder which logs the following error: [ERROR] Folder redirection: error 0x80070002 getting current path for 'Downloads' folder.  On subsequent logins the Downloads folder maps properly via DEM.  All other folders map properly all the time. I found one forum post referencing this error (https://communities.vmware.com/t5/Dynamic-Environment-Manager/VMware-View-Persona-6-2-to-UEM-9-1-Migration-UEM-Folder/m-p/2731229) but it looks like that was caused due to an issue with migrating from Persona to DEM.  We have only used DEM to redirect our folders and these specific settings worked in our previous Horizon cluster that used Windows 10 1909 and ran DEM 9.11. VMware support has only suggested reinstalling the Horizon agents which has already been done a few times for various issues and has not resolved the issue. Does anyone have any idea what I can look at or something I can try to resolve this issue? 
This I what I exclude for Office 2013: #Microsoft Office exclude_path=\Program Files\microsoft office\office15 exclude_path=\Program Files\Common Files\microsoft shared\officesoftwareprotect... See more...
This I what I exclude for Office 2013: #Microsoft Office exclude_path=\Program Files\microsoft office\office15 exclude_path=\Program Files\Common Files\microsoft shared\officesoftwareprotectionplatform
VDINinja311​ SR#: 17439278504
VDINinja311​ I had to apply both of the registry keys to fix.  I tried just using each key on its own and the Smart Policies would still not apply on login. Thankfully we were already planning... See more...
VDINinja311​ I had to apply both of the registry keys to fix.  I tried just using each key on its own and the Smart Policies would still not apply on login. Thankfully we were already planning to deploy SCCM to better manage our physical fleet which can push out the registry setting via a script.  Not sure if you have access to something similar or could push the registry key via GPO? Thanks for the info on 9.2, I had a feeling that was the answer.
Hi, I realize I am a bit late here but I have this same issue with UEM 9.1 and my Horizon Smart Policies not applying correctly on initial login, but applying correctly on reconnects.  I opene... See more...
Hi, I realize I am a bit late here but I have this same issue with UEM 9.1 and my Horizon Smart Policies not applying correctly on initial login, but applying correctly on reconnects.  I opened a ticket with VMware and this was the workaround we came up with: On virtual desktop agent: HKLM\Software\VMware, Inc.\VMware VDM\Agent\USB\UemTimeouts                                DWORD set to 120 decimal On Windows client: HKLM\SOFTWARE\WOW6432Node\VMware, Inc.\VMware VDM\Client\UemTimeout                   DWORD set to 120 decimal The tech I spoke with confirmed that this was a known issue and the fix would be pushed in a future update.  I am wondering if anyone has upgraded to UEM 9.2 and that resolved their issues with the Smart Policies not applying even though it was not listed in the release notes as a resolved issue.
We use Skype for business as well and the auto start on login was a problem, but as the company requires all employees to be logged into Lync/Skype for Business so I just placed a shortcut in the... See more...
We use Skype for business as well and the auto start on login was a problem, but as the company requires all employees to be logged into Lync/Skype for Business so I just placed a shortcut in the startup folder in my base image.  Not sure if you will be able to use this option or not. Also, I have slightly different profile that what you posted.  Not sure if this will help capturing other settings or not: [IncludeRegistryTrees] HKCU\Software\Microsoft\Office\15.0\Lync HKCU\Software\Microsoft\Office\Lync [IncludeFolderTrees] <AppData>\Microsoft\Office\15.0\Lync
So I am not sure if this qualifies as a fix but, I was given an update to several files to put into my base image.  I was given the following files: svdrivercatalogfile.cat svdriver.inf svdri... See more...
So I am not sure if this qualifies as a fix but, I was given an update to several files to put into my base image.  I was given the following files: svdrivercatalogfile.cat svdriver.inf svdriver.sys I was told to copy the svdriver.sys file into C:\Windows\System32\drivers and the svdriver.sys, svdriver.inf and svdrivercatalogfile.cat files into the AV Agent directory (C:\programfiles x86\cloud volumes\agent) When doing this and then recomposing my pool, IF a user's writable volume was deleted after I updated the snapvol.cfg file with the exclusions listed earlier in the thread then their local printers were restored.  I did not need to update or replace my Appstacks with new ones after the snapvol.cfg update.  However for users that I have not deleted their writable volume then they still do not have access to their local printers. I have informed VMWare of this information and will let you know if they have any additional updates.
In our environment we use App Stacks and App Writable Volumes, both of which have had their snapvol.cfg files updated but if both an App Stack and an App Writable Volume are attached at the same ... See more...
In our environment we use App Stacks and App Writable Volumes, both of which have had their snapvol.cfg files updated but if both an App Stack and an App Writable Volume are attached at the same time the local printers disappear again.  If we attach either an App Stack or an App Writable Volume then the exclusions restore access to the local printers.  Not sure if anyone else has ran into this issue, but I am hoping to hear back from VMware soon on how to restore access to local printers with both App Stacks and App Writable attached to a desktop.
To come back to this issue, I made a mistake when uploading a new snapvol.cfg file and had it nested in a folder when I zipped it up and uploaded it to the App Vol Manager.  Since the cfg file wa... See more...
To come back to this issue, I made a mistake when uploading a new snapvol.cfg file and had it nested in a folder when I zipped it up and uploaded it to the App Vol Manager.  Since the cfg file was nested it was not being processed and the App Writable Volume was backing up Office licensing information I though was excluded. After correcting that mistake, I have not had another user complain about Office being unable to verify its license.
Pim, Yes we just upgraded App Volumes Manager to 2.12 over the weekend but I am still having users report the issue.  I am still using the same writable template and snapvol.cfg from before th... See more...
Pim, Yes we just upgraded App Volumes Manager to 2.12 over the weekend but I am still having users report the issue.  I am still using the same writable template and snapvol.cfg from before the update (version 2.11).  We are currently using the UIA template which has been modified to allow for 30GB volumes instead of the default size.
I am using floating desktops that refresh at logoff with UEM 9.1, AppVolumes 2.12 using both app stacks as well as appwritable volumes.  Office 2013 x64 professional is installed in my base image... See more...
I am using floating desktops that refresh at logoff with UEM 9.1, AppVolumes 2.12 using both app stacks as well as appwritable volumes.  Office 2013 x64 professional is installed in my base image and licensed via KMS.  We are utilizing the UEM profiles for office 2013 which I believe I downloaded from this site and I have added several exclusions to my snapvol.cfg file to try and prevent anything in C:\Program files\Microsoft office from being captured. Generally my users are able to use office without a problem, however I have had about 10-15% of my users log into their desktops to find when they launch any Microsoft Office product they receive the following error message: Microsoft Office cannot verify the license for this product. You should repair the Office program by using Control Panel. The only fix that I have been able to find for the users is to delete their AppWritable volume.  I am hoping that someone here might be able to help me find a more permanent solution as a few of my users are on their 4th or 5th time deleting the AppWritable volume.
Eric, Thanks for the response, I tried capturing that Folder Tree and did not have luck getting the auto login setting to stay.  As luck would have it I reached out to a friend who came back w... See more...
Eric, Thanks for the response, I tried capturing that Folder Tree and did not have luck getting the auto login setting to stay.  As luck would have it I reached out to a friend who came back with a two step process that has been working: 1.) Create a new custom FlexConfig titled “IE WebCache” under Windows settings. With the settings in the below:           2.) Created logoff task in the User Environment settings, this is needed to kill a task that locks one of the WebCache files we need to back up.  Note, it’s important to set it to run task before profile export.          
Hello, I am using floating desktops that refresh at logoff with UEM 9.1, and I am currently capturing IE settings, IE passwords and Personal Certificates using the builtin Windows settings and... See more...
Hello, I am using floating desktops that refresh at logoff with UEM 9.1, and I am currently capturing IE settings, IE passwords and Personal Certificates using the builtin Windows settings and not redirecting the AppData. For almost all websites, UEM is able to capture my user's passwords and settings, however the login page for Sharepoint online (login.microsoftonline.com) will not remember that the user has checked the Keep Me Signed In box. When you enter in your email address and check that box, the user should be redirected to our ADFS website for SSO with Office 365 and then redirected back to our main Sharepoint online page. Upon logging out and back in I can see UEM captured cookies and user certificates, however when the user logs back in and heads to our Sharepoint online page, they are presented the login page and must authenticate again. Has anyone had any luck in capturing this setting or have any ideas as to what I can try next? Thanks.