ch4mp10n's Posts

SaaS Ops is VMware support, just another name for it. it would be best to log a ticket with them.
it could be a smart group or too not working as expected, saasops might be your best bet here for troubleshooting further.
what compliance profiles/policies are being applied? can you check the device logs to see if it successfully applies then gets removed?
What version of Teams are you attempting to push out via the portal?
Does your backend Authentication support Cert based Auth for your app?
Is this specific to certain apps or all apps? What version of UEM are you using.
Wha browser are you using? Tried Chrome or Firefox? i had similar issues back in the day around UI issues.
Does the application have a maximum version of Android it supports? Can you try and install the apk or application on the device manually? Do you have any compliance policies in place that could be... See more...
Does the application have a maximum version of Android it supports? Can you try and install the apk or application on the device manually? Do you have any compliance policies in place that could be blocking installation? What is the device logs saying in UEM?
What issues have you come across? I am using the latest version of UAG for a customer mostly around patches for log4j and havent come across any issues. However we are not using Content Gateway - onl... See more...
What issues have you come across? I am using the latest version of UAG for a customer mostly around patches for log4j and havent come across any issues. However we are not using Content Gateway - only per-app tunnel.
Are you using Onprem WS1? or SaaS WS1? What timing differences are you seeing? Specific to a certain browser? (Edge/Chrome/Firefox)?   I can see a slight difference in accessing it via version 21... See more...
Are you using Onprem WS1? or SaaS WS1? What timing differences are you seeing? Specific to a certain browser? (Edge/Chrome/Firefox)?   I can see a slight difference in accessing it via version 21.5.0.39,  1-2 seconds to load each click.
PerApp VPN, im 90% sure uses paths the SYSTEM can see, this being device based rather then user based. did you try opening up a case with vmware support?
Can you login using Root, into the UAG can you also telnet onto to the IP over that port? is the firewall open between your subnet and that IP?
Hello, I goto Assign >> New >> I want to create an Application Assignment (Writable) however the OS dropdown box has no values.... Has anyone seen this or have a fix for it? regards, ... See more...
Hello, I goto Assign >> New >> I want to create an Application Assignment (Writable) however the OS dropdown box has no values.... Has anyone seen this or have a fix for it? regards, Mike.
@Ray_handels. This is exactly what I was getting at, I am running ESXi 6.0 u1, and do see a 3 second attachment time per Stack/Writable. Im running Writable Volumes UIA without Profile.... ... See more...
@Ray_handels. This is exactly what I was getting at, I am running ESXi 6.0 u1, and do see a 3 second attachment time per Stack/Writable. Im running Writable Volumes UIA without Profile.... I have literally 5 second login times for mandatory Profiles on Windows 8.1, Window 10 about 15. As soon as attaching a writable ontop it can increase the minimum login time to add an additional 25-30 seconds, for each OS then and additional 15 sec+ for each AppStack, these are extremely optimized profiles. To break that down Win8.1: 5 Seconds login with Mandatory profile 30-35 Seconds login with Mandatory profile and Writable. 45-120 Seconds login with Mandatory profile, writable and 1-3 AppStacks. Win10: 15 Seconds login with Mandatory profile 40-45 Seconds login with Mandatory profile and Writable. 55-130 Seconds login with Mandatory profile, writable and 1-3 AppStacks. I don't know if this is acceptable behaviour, but @ the end of the day its about the user experience... Running the above in a non-persistent pool + refresh, with UEM id expect closer login times to that of the mandatory profiles where users login every morning and have to wait that long to login seems very excessive and time consuming. I have gone with no AppStacks, just a Writable volume for user personalization that alone speeds up the login time for them by 40-50% then having them attached.
its very slow even with 1 AppStack, we shouldn't have to wait 45+ seconds to login... sub par 15-20 seconds should be the benchmark for user logins especially non-persistent.
I can confirm the same issue exists with Office 2013
As the title says, "Writable Volumes Breaking Office 365 (Office 2016) Skype for Business Address List Searching & Outlook Presence." I havent found a solution to this other then disabling the... See more...
As the title says, "Writable Volumes Breaking Office 365 (Office 2016) Skype for Business Address List Searching & Outlook Presence." I havent found a solution to this other then disabling the Writable volumes for users, this happens with the following configuraiton: ** OS's Windows 7 64 bit, Windows 8 64 bit, Windows 10 64 bit ** App Volumes 2.10 ** UEM 2.7 ** Latest Office 365 Office 2016 build. Very frustrating, as Writable volumes is really a must in our floating pool, non persistent environment. does anyone have a solution? regards,, Mike.
We had been waiting anxiously for AppVolumes 2.10 sup portability so we cant implement our architecture into our own internal VDI (upgrading from view 5.3). We would like to see the login time... See more...
We had been waiting anxiously for AppVolumes 2.10 sup portability so we cant implement our architecture into our own internal VDI (upgrading from view 5.3). We would like to see the login times under 30 seconds. Without any appstacks attached 18 seconds to login (not using any roaming profile or uia+profile), with 1-2 stacks attached we saw anywhere up to 5 minutes to login with a baseline out of the box appvolumes agent configuration on the VDI's. After tweaking registry agent keys (additional Notes), I can get it to around 55-60 seconds with the same configuration but no writable volume. I am experiencing very long login times up to 5 minutes for Windows 10 VDI's using the following configurations: * Windows 10 (64bit, 6gb, nVidia vGPU) * App-volumes 2.10 * Horizon View 6.2 Pooled Linked Clones * ESXi 6u1 * UEM 8.7 I have also confirmed by installing the same applications into the direct image that login times around 18-25 seconds, so i firmly believe this is an issue with the App-Volumes agent. I can confirm via vCenter the AppStacks get attached to the VM's in under 3 seconds each. I have attempted to tune the AppVolumes svservice (via registry keys attached here) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svservice\Parameters] "Hypervisor"="vcenter" "Manager1"="LEONVANWYK" "RebootAfterDetach"=dword:00000000 "VolAttachMessageOn"=dword:00000000 "LogFileSizeInKB"=dword:00002048 "DomainNameWaitTimeOut"=dword:00000003 "WaitForFirstVolumeOnly"=dword:00000001 "HidePopups"=dword:00000001 "DisableRunKeys"=dword:00000001 "VolDelayLoadTime"=dword:00000000 "MaxDelayTimeoutS"=dword:00000002 "VolWaitTimeout"=dword:00000001 "ConnectTimeOutMs"=dword:00000100 "DisableAutoStartServices"=dword:00000001 "ResolveTimeOutMs"=dword:00000100 "WaitForFirstVolumeOnlyValue"=dword:00000001 Also looking through the svservice.log it appears there is 22-32 seconds of the agent doing nothing....