Michael Zielinski

procmon was what finally cracked this nut. Thanks for the link and tip, Sascha.

The tunnel as such works with the other apps. It's just Citrix that won't work. When the tunnel is in device mode Citrix works and I can start published apps. When in per-app mode selfservice.exe will not let me log in and I cannot start apps from browsers as well. I can connect to web based citrix as I have added the url to our browser rules. But I cannot start apps as this is initiated by selfservice.exe. As this works in device mode I believe that selfservice.exe calls another app to actually connect and since this is not added the connection will fail. So basically what I need is a list of the citrix apps to allow in the tunnel or a pfn

Hi, I was wondering if any of you could give me some pointers on how to allow citrix and the published apps through the tunnel? So far I have allowed the store in Chrome and Edge and allowed the Citrix Workspace through the tunnel. I can successfully conect to Citrix through a browser but I cannot connect directly through the workspace app. Also I cannot launch apps from inside citrix. I get an error that the selected resource failed to respond in time. If I set the tunnel into per-device mode everything works

Hi, I was wondering if anybody had gotten the wirelss display and encryption (both with and without USB encryption) beta profiles to work? We have tried for weeks and finally created csps in policy builder for custom profiles.

Unfortunately we are not in a position where we can use beta profiles that may or may not work as expected in our production environment. For example, we have spent days if not weeks trying to get the encryption template to work without any success. 2 minutes in policybuilder and a custom profile and everything worked.

I found the beta profiles to be useable for the most basic tasks at best. The policybuilder was such a great tool that saved tons of time. I really hope you bring it back. The ADMX editor is blocked by Windows from running on our pcs. Got it to work however not all options are available in the ADMX which again makes the policybuilder a far superior tool. For example in the wirelessdisply admx only 2 of the options are available while the policybuilder had all of them AllowMdnsAdvertisement AllowMdnsDiscovery AllowMovementDetectionOnInfrastructure AllowPCReceiverToBeTCPServer AllowPCSenderToBeTCPClient AllowProjectionFromPC AllowProjectionFromPCOverInfrastructure AllowProjectionToPC AllowProjectionToPCOverInfrastructure AllowUserInputFromWirelessDisplayReceiver RequirePinForPairing

Hi Siddesh, we use baselines and profiles already. The code we created in the policy builder would be copied to the custom section of a profile. The new beta profiles are far from perfect, some unusable if you don't have syncml you can paste. We control everything through profiles, Bitlocker, wireless casting, windows updates,... Regards Michael

Hi, https://vmwarepolicybuilder.com/ seems to have stopped working. It is an incredibly useful site to build syncml policies and even linked to from the Omnissa documentation. Will Omnissa revive the policy builder? Kind regards Michael