Virtual_Leo

If you haven't already tried that should solve it. I had to expand the disk to be able to upgrade, installed parted according to photon documenation (Expanding Disk Partition · VMware Photon OS 3.0 Documentation) and ran the update, it failed after a while because of this package. Luckily i was able to run it again with not too much service interuption. I cannot find the Photon OS upgrade being mentioned anywhere, atleast that would have been nice to know. Clearly focus is on the cloud product of Access. This ofcourse sucks for on-premise users that has extremely strict security policies and can't move to the cloud.

Hello We have an on-prem enviroment with Horizon, users authenticate using a third party IDP through WS1 Access. TrueSSO is in place to login to the VDI-sessions Is there any way to get information in a VDI-session of how the user authenticated in Access? The only thing i can find is the enviroment variable that says TrueSSO is used. I would like to know which method the user authenticated with in Access like "LOGIN (Third Party IDP Auth Method1)" or "LOGIN (Third Party IDP Auth Method2), this i can currently see in the WS1 Access log Is this currently possible in any way?

Ok then I understand what it's meant for, ofcourse it's a good thingy to be able to block network access in that way. I was hoping it was able to query something like smartgroups or tags. For our Windows endpoints (not UEM managed, we use SCCM for them) we use Active Directory groups to manage this which is working very neat. Group 1 = Net1 Group2 = Net2 etc.

Hello We currently are looking into splitting our devices to different netoworks/firewall rules, this ofcourse we wanna make as dynamic and automatic as possible. It may be possible in the future that this could be 5-6 different networks with different firewall rules. Today we only have one network for our MDM-devices and ISE is looking at the OID when the device tries to connect to send it to the correct network I would preferbly not want to use different certificates for different networks/firewall rules, we looked at the ISE integration you can do, i'm not completly sure of how you can query UEM, is smartgroups possible to query? If not i quite don't understand what the benefits of the integration would be I've read both documentation from CISCO and Omnissa Cisco Identity Services Engine Administrator Guide, Release 3.4 - Secure Access [Cisco Identity Services Engine] - Cisco https://techzone.omnissa.com/resource/integrating-workspace-one-uem-and-cisco-ise-v31-and-beyond We run UEM on-premise Anyone else runs this and have any input to help us further?

Ok thank you for the answers Is Access with a SaaS subscription expected to have 0 downtime during upgrades?

Hello We run Access on-premise in a cluster of 3 nodes, version 23.09. We now want to upgrade it to 24.07, when looking at the upgrade documentation it says to remove all nodes except one, and now upgrade the node that still is connected to the loadbalancer. Upgrade a Workspace ONE Access Cluster (omnissa.com) This sounds kinda odd to me, is there really no way to upgrade with 0 downtime for the end user? We have a completly HA Horizon environment with all components loadbalanced, two pods, multiple UAGs, AppVolume Managers, Connectionservers etc. The part that currently makes the environment not 100% serviceable without any disruption is Access, which is being more and more important in our environment

We are having users that is running Classic Teams currently that we need to migrate to new teams. We are using FSLogix HF4 This is what i'm going to try deploy to a couple of test users. In my testing this seems to work to allow new teams to start, the outlook integration is also working and i'm able to join meetings from outlook meetings powershell -ExecutionPolicy bypass -Command "Add-AppxPackage -DisableDevelopmentMode -Register 'C:\Program Files\WindowsApps\MSTeams_24165.1414.2987.41_x64__8wekyb3d8bbwe\AppxManifest.xml';Remove-Item 'HKCU:\Software\Classes\TeamsURL' -Recurse;Remove-Item 'HKCU:\Software\Classes\ms-teams' -Recurse;Remove-Item 'HKCU:\Software\Classes\msteams' -Recurse" Using VMware DEM to deploy it as a logon task with a condition to check if new teams exists on the non-persistent VDI, by reg key HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\MSTeams_24165.1414.2987.41_x64__8wekyb3d8bbwe It isn't beautiful with static versionnumbers but will work for us with a short transition period