Phil_Helmling's Posts

Have a look at https://github.com/helmlingp/WS1UEM_CustomKiosk/blob/main/ExampleKioskProfile_with_CitrixWorkspaceApp.xml example. on Edge browser blocking ICA files, I guess you would deploy the Browser CSP - https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser but not sure as I've not done that  

Hi, I would recommend you look at VMware Dynamic Environment Manager to achieve this integrated with Workspace ONE https://techzone.vmware.com/resource/what-vmware-dynamic-environment-manager#top-5-things-you-should-know https://docs.vmware.com/en/VMware-Dynamic-Environment-Manager/2203/com.vmware.dynamic.environment.manager-adminguide/GUID-37CCC0E9-A8BC-4916-B9C2-7D30188F43F7.html Phil

MSIX packages don't natively use app.config files for configuration and Windows devices don't natively use them either. There is no MDM API to use them. As such, WS1 doesn't support them as a policy for Windows devices. If you wanted to provide a different configuration delivered by the app.config file, then push the app.config file as a separate package. You could use Freestyle workflows to do this.

Your best option is to follow the guidance in the doc linked here https://www.vmware.com/au/products/workspace-one/windows-10-windows-11-management.html > Resources > Windows OS Lifecycle Management Guidance

Hi Kyle, not sure about the stability question and apps not installing on Win11. Are these on-demand app installs? They are initiated by Hub but executed by SfD so need to see what is happening with logs. I would log an SR for that

Hi Mikhail, yes this should be fine - https://techzone.vmware.com/deploying-vmware-workspace-one-tunnel-workspace-one-operational-tutorial#configuring-workspace-one-web-for-per-app-tunnel. Workspace ONE Tunnel (UAG) does support websocket proxy as some Horizon traffic is proxied this way I believe. 

Hey Larry what is your enrolment grouping set to? Normally we would config at the top (Customer) OG and config the device to move based on user group. But this does depend on the OS of the device being enrolled and whether you are using staging enrolment.

The enrolment must be run with Admin privileges so yes using runas would help. Also bear in mind that our enrolment on Windows requires an active user session because it is an OMA-DM enrolment, which only runs in user context. So the install of the agent and services are in SYSTEM Context, and enrolment is USER but must be initiated from SYSTEM context or using local Admin account including runas.  HTH

Hi Andrey, Assist is a separately licensed product. Being On-premises you will need to check you are licensed follow these instructions - https://kb.vmware.com/s/article/2961361?lang=en_US Also checkout this docs page on high level architecture and requirements to ensure you have everything in place - https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/WS1_Assist/GUID-AWT-RMV4-INTRO.html and then follow this doc to actually implement - https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/WS1_Assist/GUID-AWT-INSTALL-ARM-SUPERTASK.html I know you said you have already deployed, just walk through the docs and ensure you have done everything it says please. Otherwise, I would log a support call via Customer Connect - https://customerconnect.vmware.com/ 

Hi again Nolan, I wrote this script to achieve your base requirements. It is designed to be deployed with WS1 Scripts and requires the two variables set as part of the WS1 Scripts function. You set the frequency of run in the assignment. https://github.com/helmlingp/WS1UEM_Scripts/blob/main/GenerateLocalAdministratorPassword.ps1