That is unfortunate....Just so I'm clear, it is the screen at ' All Settings | System | Enterprise Integration | VMWare Tunnel | Configuration' and VPN profiles are not deploying to newly enrolled devices even though it was already configured prior to the upgrade?
I ask because I have it configured at my top level OG and it is inheritited at the lower level OGs.
We do also have this issue, but not in lab environment (where DNS not contains ' vpn' . We're running 184.108.40.206 I found this in the changelog for 1907 https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1907/rn/VMware-Workspace-ONE-UEM-Release-Notes-1... PPAT-5454: Proxy whitelist check fails if the console hostname string contains ' VPN' . Is this really fixed. Our server DNS name contains ' VPN' .
I have a support ticket, but it's slower response than usually.
It looks like this we released on 10/7 and looks an awful lot like the issue you guys are seeing. Has support reached out to anyone here saying this would fix the tunnel issue?
URGENT-1706 - Custom Agnostic patch resolving crashing UEM Console Tunnel page -SINST-175378
I'm planning on upgrading to 1907 including patch installer 18. Wonder if the fix is included in the patch installer since it was released on 10/8...one day after the fix.
UPDATE: Looking at the text file in the patch installer, it doesn't look like it includes the 1706
Same problem here, tunnel page is working but vpn profiles do not apply on devices after update from 1903 to 1907.0.18.
Agnostic Patch is not possible, in the appsettings.json you should delete ' Usage:...' from the TunnelDB Connection String. In my appsettings.json there is only an encrypted text at this position. The SQL script in the patch only seems to change the version information to 220.127.116.11.
API Urls directing to Consoleserver (on Global and all OGs).
Update: it seems that the api urls have to be the device service server. After that it works with the profiles