jqvm's Posts

Hi peoples, We've just upgraded from 2.9.1 to 2.13.2 (Horizon 7.0 to 7.3.2) and are seeing a different behavior when processing complex appstacks. If svservice is still processing appstacks... See more...
Hi peoples, We've just upgraded from 2.9.1 to 2.13.2 (Horizon 7.0 to 7.3.2) and are seeing a different behavior when processing complex appstacks. If svservice is still processing appstacks after group policies and the verbose "preparing desktop" screen, we see a black screen with an active white mouse pointer for 10 to 60 seconds.  At the end of the black screen period we see the vRops/helpdesk vmware login manager pop up quickly, then the desktop loads. Appstacks with fonts/printer drivers are slow to process (Adobe Acrobat Pro adds 50 seconds to processing time) Has anyone else seen this, or know of adjustments that could help? Thanks Josh
Hi Ray,   For that first excel performance bugfix, do you have any info about which version this issue was first seen/introduced? Raymond_W​ Thanks Josh
So after my OP and original workaround, our issue reoccurred following a reinstall of View 7.0 agent and UEM 9.1.0.  All Zero client USB was blocked on connect and reconnect. We applied the t... See more...
So after my OP and original workaround, our issue reoccurred following a reinstall of View 7.0 agent and UEM 9.1.0.  All Zero client USB was blocked on connect and reconnect. We applied the two regkey changes via GPO and USB started working again.  Thanks for the progress and support UEMdev​ and everyone on the community! Instant0Darth0Vader​ did you install UEM 9.2.1+ with your Horizon 7.4?
FYI, support have provided a workaround for the Disabled users issue that we see when multiple AD domains are specified in AppVol 2.12+.  (This is still an issue in 2.13.1 I believe) Setting t... See more...
FYI, support have provided a workaround for the Disabled users issue that we see when multiple AD domains are specified in AppVol 2.12+.  (This is still an issue in 2.13.1 I believe) Setting the LDAP Base on all domains allows the AD sync to find the users in the correct domain.  Working well for us, all users appear enabled after changing the settings. Navigate to Appvolumes Manager console go to Configuration-> Select AD domains> set Base for all domain controllers: For example if the Parent domain name is : corp.com and child domain name is child1.corp.com and child2.corp.com then below is the format that has to be set in LDAP Base For Parent domain : DC=corp,DC=com For child domain1 : DC=child1,DC=corp,DC=com For child domain2 : DC=child2,DC=corp,DC=com
GSS have reproduced our issue where an AD Sync causes all users to be 'disabled' until next login. This only seems to occur when more than one domain is added to the manager. No timeframe on a... See more...
GSS have reproduced our issue where an AD Sync causes all users to be 'disabled' until next login. This only seems to occur when more than one domain is added to the manager. No timeframe on a fix from engineering as yet.
Ray we also had issues during the schema upgrade, ours was related to transferring the 'trusted domain' settings in 2.9 to the new domains settings in 2.12.x.   We had to remove the trusted domai... See more...
Ray we also had issues during the schema upgrade, ours was related to transferring the 'trusted domain' settings in 2.9 to the new domains settings in 2.12.x.   We had to remove the trusted domain settings prior to running the upgrade. Has anyone progressed their SR's with this disabled users after AD sync?  We have an SR running for this also.  DDunaway​ WTopping​ Josh
We also see this issue, it occurred after upgrading from 2.9 to 2.12.1 as a resync of objects is initiated after the upgrade.   The user object gets re-enabled after their first login, but you ca... See more...
We also see this issue, it occurred after upgrading from 2.9 to 2.12.1 as a resync of objects is initiated after the upgrade.   The user object gets re-enabled after their first login, but you can't modify direct assignments to the user until this first login. Additional resync operations mark all users as disabled again.
Hi Lakshman,  any word on the fix for stopping invalid Adobe Reader configuration with AppVolumes?  We have seen similar issues with Protected Mode since AppVol 2.6, which still seem exist in... See more...
Hi Lakshman,  any word on the fix for stopping invalid Adobe Reader configuration with AppVolumes?  We have seen similar issues with Protected Mode since AppVol 2.6, which still seem exist in 2.12.1 startup.bat.  AppVol forces bProtectedMode=0 in the provisioning/attachment scripts, which creates an invalid configuration if the customer sets ProtectedView=1 in their environment. (ie, when customer requires a secure configuration) (See the note at the top of this page) Protected Mode — Acrobat Application Security Guide A workaround we have used is to change these regkeys in the later stages of login using allvolsattached.bat in an appstack applied to all users. Thanks Josh
We have a bug ticket open for a similar issue that produces a Server 500 Error after a 2.12.1 upgrade.  Ours was caused by having a "Trusted Domains" configuration in Appvol 2.9/2.10/2.11, that c... See more...
We have a bug ticket open for a similar issue that produces a Server 500 Error after a 2.12.1 upgrade.  Ours was caused by having a "Trusted Domains" configuration in Appvol 2.9/2.10/2.11, that causes a failure in the migration scripts used during the 2.12.1 installer.  Workaround was to remove the Trusted domain config prior to upgrade. The migration script fails to move both the primary and trusted domain configs to the new schema format, and then triggers another migration script that attempts to run SQL scripts incorrectly as the local machine account  <domain>\<machine$>.  We have SQL user authentication configured, so the appvol computer account should not be used. (Local machine dbo rights are only needed when Windows integrated auth is being used for ODBC, as per the install doco & KB2108131) As a side note, our testing would see similar server 500 errors when: - The manager .msi file is launched instead of the setup.exe.  Setup.exe runs additional migration/odbc scripts needed during the upgrade (such as svmanager_setup.bat) - Windows integrated Authentication is being used, and the local computer account does not have access to grant roles/dbo.  Josh
Word of warning for anyone starting a UEM migration, it appears that UEM can mess with PCoIP USB if it is left in a running but unconfigured state. We installed UEM in a Gold master image and ... See more...
Word of warning for anyone starting a UEM migration, it appears that UEM can mess with PCoIP USB if it is left in a running but unconfigured state. We installed UEM in a Gold master image and left the service to automatic startup, with no UEM GPO's were applied to the linked clone pools.  (We were preparing for UEM migration/testing) USB devices fail to attach in the initial login session, a reconnect on PCoIP allows the devices to pass through from the Zero client.   The issue also seems to delay the attachment of Appvolumes appstacks.  PCoIP server log reports: LVL:1 RC:   0        SOFT_USB :VHUBLIB(error): GetUemStatus : Failed to open key path is Software\VMware, Inc.\VMware UEM\SessionData\1 LVL:1 RC:   0        SOFT_USB :VHUBLIB(error): The UEM component is still not ready yet Workaround is to set the service to manual/disabled until UEM is required for a desktop pool.   If UEM is enabled at login (say via the GP extension method), the issue does not occur.   We didn't raise a case for this, but an interesting one anyway. (UEM 9, Appvol 2.9, Horizon 7) Josh
2.7 - 2.9 needed VolDelayLoadTime = 0 to be set explicitly, if not entered in registry it did not apply and drive letters still appeared. I have only very rarely seen drive letters being consu... See more...
2.7 - 2.9 needed VolDelayLoadTime = 0 to be set explicitly, if not entered in registry it did not apply and drive letters still appeared. I have only very rarely seen drive letters being consumed (1 or 2 slow appstacks) with this config, the issue has been resolved for us. 2.10 should also have this fix carried through (I haven't tested it)
Sounds like persona didn't start for these sessions, which can be caused by GPO failing to apply or potentially a timing issue with folder redirection/Offline files conflicting with Persona etc. ... See more...
Sounds like persona didn't start for these sessions, which can be caused by GPO failing to apply or potentially a timing issue with folder redirection/Offline files conflicting with Persona etc. We've seen ~5% of machines failing to apply GP at boot up (and hence persona services stays disabled). This starts occurring 30 days after the last recompose, due to the default 30 day AD Computer password reset which View Composer service races to update from the internal disk at boot time.  See KB 208443  (being updated to refer to Persona Management soon we're told) When Persona service is still disabled at user login, Windows App log might show some WinLogon events with vmwvvpsvc login notification errors.  Josh