tpc1337's Posts

Greetings, We are using the folder redirection feature from VMware DEM for a while now, and it always works as expected. Until recently we were testing with the command line utility Git4Windows (Git... See more...
Greetings, We are using the folder redirection feature from VMware DEM for a while now, and it always works as expected. Until recently we were testing with the command line utility Git4Windows (Git Bash), and noticed that when browsing to the Desktop via the Git Bash client,(which is redirected in DEM), files saved there where not redirected to the users' archive. It seems that when redirecting folders such as Desktop, Documents and Downloads; DEM itself creates a seperate set of these folders in the users' profile directory ( e.g. C:\Users\%username%\Desktop, C:\Users\%username%\Documents and C:\Users\%username%\Downloads) . When putting a file in one of these folders, the file isnt redirected to the profile archive on the file server. I noticed that DEM creates shortcuts for Desktop, Documents and Downloads under C:\Users\%username%\Links\. When placing files in one of these directories ( e.g. C:\Users\%username%\Links\Desktop\ ), the files are immediately redirected to the users' profile archive. But since command line utilities like Git Bash cannot traverse through an actual shortcut (.lnk for C:\Users\%username%\Links\Desktop.lnk), it does not seem possible to edit and save files in these locations. My question is, is there a possibility to use command line utlities such as Git Bash together with folder redirection?   Kind Regards,   Tim
Sorry for the late reply, I tested this and it works, thanks a lot!
Hey thanks for the quick reply, thats completely understandable then. I am quite interested in using a COM interface to create those approved zipfiles. Also wondering how that would work, but yeah th... See more...
Hey thanks for the quick reply, thats completely understandable then. I am quite interested in using a COM interface to create those approved zipfiles. Also wondering how that would work, but yeah that would be cool if you could give me some detail about that!
Unfortunately I cannot put our client machines (VDIs) in the Ansible inventory because of licensing reasons. So the option I am stuck with is targeting the DEM fileserver with Ansible. I am using a t... See more...
Unfortunately I cannot put our client machines (VDIs) in the Ansible inventory because of licensing reasons. So the option I am stuck with is targeting the DEM fileserver with Ansible. I am using a template XML and ZIP file for the "Files and Folders" section in management console. I created this with the management console. When our automation pipeline is nearly at an end, the end users playbooks / roles are kicked off. Ansible copies the template XML file, injects user specific conditions (which works well, since it shows up in the management console after editing), after that the template .zip file is extracted, the .ini file that resides in the extracted archive is replaced with a template (also filling some user specific variables) and then the archive will be compressed to a .zip file. Although the setting does show up in the management console, when a user logs in falling under the condition (eg Active Directory group), the settings are not applied, and a FATAL error is logged in the user's archive log file, indicating the .zip file created by Ansible cannot be read.
Hi,   From an automation perspective, I am trying to place config files in de AppData directory for certain applications. Now I have everything working (automation wise), but I discovered settings ... See more...
Hi,   From an automation perspective, I am trying to place config files in de AppData directory for certain applications. Now I have everything working (automation wise), but I discovered settings are not applied since the .zip file cannot be read. It causes a fatal error when looking at the logs for the specific user. From https://communities.vmware.com/t5/Dynamic-Environment-Manager/Error-while-importing-UEM-settings-Fatal-Error-reading-archive/m-p/2837522/highlight/false#M6801 I saw UEMdev making a comment that the management console has trouble reading edited .zip files. I was and am still wondering if there is a workaround for this. I tried looking at differences between a config file generated by the management console and a config file generated by our automation (Ansible). There seems to be something underwater that is prohibiting the .zip files to be read by DEM / management console. I am wondering what this is and if there is a workaround, since this would make automating the end user experience a lot easier.   Kind Regards, Tim
Hi Jesse,   Will do. Thanks.   Kind regards,   Tim
Hi, I know this has been asked a long time ago, but I am wondering, if theres any possibility of editing these profile archives with automation in mind? We are trying to automate certain profile sett... See more...
Hi, I know this has been asked a long time ago, but I am wondering, if theres any possibility of editing these profile archives with automation in mind? We are trying to automate certain profile settings for our users, such placing a config file in AppData\Roaming. Although the automation step works, as UEMdev stated, DEM cannot read the generated .zip file, it causes a fatal error when looking at the logs for the specific users. Is there any way to still automate placing certain config files and DEM being able to read them? Ive been spinning my head for weeks/months on this. Would really appreciate if there was a way so that DEM would accept the modified files.   Kind regards,   Tim
Hi DEMdev, Spot on! It was indeed due to config files being read in the user profile itself. On the DEM part everything went well. I'm doubting if we will be using the cleanup tool, since we'v... See more...
Hi DEMdev, Spot on! It was indeed due to config files being read in the user profile itself. On the DEM part everything went well. I'm doubting if we will be using the cleanup tool, since we've to manually look up every regkey/file location of every application in order for the cleanup tool to work properly. Thanks for your quick response! Regards
We use persistent VDI's where users have their own profile. As long as they work in the same VDI, the profile settings are saved on that VDI. When users get assigned a new VDI their profiles are ... See more...
We use persistent VDI's where users have their own profile. As long as they work in the same VDI, the profile settings are saved on that VDI. When users get assigned a new VDI their profiles are gone and so are all their environment settings. Thats why we are currently working towards implementing VMware DEM so that users' settings will be persistent across newly assigned VDI's. We implemented the DEM environment exactly as stated in the VMware docs. Like previously mentioned, all other things are working fine. We profiled 2 applications and added 4 common Windows settings in the Management Console, this all works great and is tested with several users. It's only the self support tool that we can't seem to get working properly.
Hi, We are in the process of deploying VMware DEM in our environment. So far everything is working fine, except for the Self Support tool. I did some tests with it and noticed that in the Flex... See more...
Hi, We are in the process of deploying VMware DEM in our environment. So far everything is working fine, except for the Self Support tool. I did some tests with it and noticed that in the FlexEngine.log application settings were reset, but when our user account starts the application the settings are still there. I am using DirectFlex for the mentioned application. I also did tests  with the "Windows Common Setting" for the taskbar, and it had the same effect. FlexEngine.log shows that there is no profile archive to import for the specified config file, so I'm assuming that the cleanup actually worked. But when I logoff and logon again, the application settings are still there. Maybe I am missing something, so that's why I decided to post this on the forum. Regards