jigocz Tracker

published application opening in full screen

jigocz — Thu, 26 Aug 2021 14:18:35 GMT

Hello,

we have some applications published to Horizon,

when user1 is logged in and is opening the published application e.g. SAPGUi, application is opening - in full screen window without any option to change the application screen resolution...

and for the other user - user2 is opening correctly - The SAPGUi appears and looks just like it would if it were a locally
installed app.

Any Idea which and where configuration we are missing for first user?

Thank you in advance.

Horizon Linked Clone - customization running forever for updated Golden Image Windows 10 LTSC

jigocz — Thu, 26 Nov 2020 16:12:06 GMT

Hello,

we have golden image with Windows 10 LTSC - 1809 - OS Build 17763.1158 with installed,

Vmware Tools 10.3.5 - build 10430147
Vmware Horizon agent 7.11.0
AppVolume Agent 2.18.6

it is used for Automated Desktop pool Floating Assignment, Linked Clone, the last build / update for image was done August 2020.

We use Sysprep Customization script.

The Golden image is configured per guidance

https://techzone.vmware.com/creating-optimized-windows-image-vmware-horizon-virtual-desktop,
https://www.carlstalhood.com/vmware-horizon-7-master-virtual-desktop/

and was operating without any issues till now.

We installed now the latest windows patches - October or November 2020 and closed the master image, created a new snapshot for provisioning.

Since we installed the Windows patches, all the new provisioning or recompose for the VM is "failling" and "stuck" on customization.

The machine is provisioned with the correct hostname, IP is assigned from DHCP, powered-on and
then the machines sit in a customization process and never go any further - initial sysprep is done and then nothing.

Has anyone observed this behavior and if so, were you able to resolve it?

Thank you.

Re: AppVolumes - Appstacks 2.15 vs 2.18.2

jigocz — Fri, 19 Jun 2020 06:43:04 GMT

Hello,

we have been told by Vmware support that in Appvolume version 2.18.0 there is special handling for environment variables in a certain callback function, but it is not present in 2.18.2 onwards.

The recommendation is to downgrade the agent to 2.18.0 :smileysilly: and deploy a test pool to see if the issue with environment variables occurs.

If it doesn't occur, then I would suggest running this build of agent in your environment until 2.18.5 is released. This should also contain fixes of the 2.18.4 build.

This build - 2.18.5 is do for release at the end of July, but this date could change if engineering need to push the date back, if they need to add other fixes to the build, etc..

Re: AppVolumes - Appstacks 2.15 vs 2.18.2

jigocz — Fri, 19 Jun 2020 06:36:48 GMT

yes, we have tested also with the Vmware Tools 11.0.6

Re: BSOD for Windows 10 with AppVolume agent 2.18.2

jigocz — Fri, 05 Jun 2020 11:02:00 GMT

Hello,

we have updated the appvolume agent in Golden image to version 2.18.4 and created a new desktop pool with one provisioned VDI VM and test user is logged in - with appstacks and writable volume attached.

We will leave the VDI Vms running for some time to see if the issue is reproducible there - and base on the results will collect and provide the required .vmem and .vmss files to opened vmware support case.

What do you suggest for upgrade the AppVolume manager server from 2.18.2 to version 2.18.4 please?

What is the compatibility between version 2.18.2 to version 2.18.4 ? - like we have Appvolume manager server running now from version 2.18.2, appstacks captured with template for 2.18.2, Writable volume created from template for 2.18.2, AppVolume Agent running from provisioned VDI VM with version 2.18.4..

Re: AppVolumes - Appstacks 2.15 vs 2.18.2

jigocz — Fri, 05 Jun 2020 10:59:35 GMT

Hello,

as part of our internal testing we have updated the appvolume agent in Golden image to version 2.18.4 (recently released by Vmware) and created a new desktop pool with one provisioned VDI VM and test user is logged in - with appstacks and writable volume attached => to check for appstacks assignment order with appvolume agent 2.18.4

==> new appvolume agent 2.18.4 does not solve the problem with appstacks assignement order / system variables.

The SupportCase is still opened with Vmware Support without further update till today.

AppVolumes - Appstacks 2.15 vs 2.18.2

jigocz — Tue, 02 Jun 2020 13:17:59 GMT

Hello,

let me share with you the experience while working with Appstacks created in AppVolumes version 2.15 and then upgraded the AppVolumes and Appstacks to version 2.18.2 - all appstacks has been re-created for Appvolume version 2.18.2

short info about our environment

We use direct appstacks assignments to user only.
The Golden image:
- Windows 10 image LTSC - 1809 - OS Build 17763.1158 windows updates to 04/2020,
- AppVolume Agent 2.18.2.27
- Vmware Horizon agent 7.11.0
- Vmware Tools 10.3.5 - build 10430147
after each appstack capture, the capturing (packaging) virtual machine is reverted back to the original snapshot,
the capturing (packaging) virtual machine has installed only the VMTools 10.3.5 and AppVolumeAgent 2.18.2.27
Appstack template used is 2.18.2
Writable volume used is 2.18.2 - uia_plus_profile

=> Our big problem now is that what was working with appvolumes version 2.15 is no longer working in version 2.18.2,

=> with appvolume agent version 2.15 we have assigned for example 11 versious appstacks, (captured from application template 2.15)

SAPGUI_7.50FP9HF2_x86
Python_2.7.8_x64
PuTTY_0.70_x64
PersonalCommunications_12.0.4.1_x86
OracleDataAccessComponents_12.2.0.1.1
OneDrive_19.043.0304.0003_x86
OfficeAccessDatabaseEngine2007EN
Office2016_16.0_x86
DB2ConnectServer_11.1.0.1527_x64
Chrome_71.0.3578.98_x64
AcrobatReaderDC_19.010.20069_x86

=> there is no any dependency that we would need to assign any of that appstacks in specific order, with some precedence, etc

=> how the appstack is assigned - attached it works without issue.

=> With version 2.18.2 all appstacks has been created from the beginning - captured from application template 2.18.2) see the example below

PersonalCommunications_12.0.4.1_x86_T2182
OracleDataAccessComponents_12.2.0.1.1_x86_T2182
SAPGUI_7.50FP9HF2_x86_T2182
Python_2.7.8_x64_T2182
PuTTY_0.70_x64_T2182
OneDrive_19.043.0304.0003_x86_T2182
OfficeAccessDatabaseEngine2007EN_12.0.4518.1031_x86_T2182
Office2016_16.0_x86_T2182
Chrome_71.0.3578.98_x64_T2182
DB2ConnectServerRuntimeClient_11.5.0.1077_x64_T2182
AcrobatReaderDC_19.010.20069_x86_T2182

=> it looks like there is a some new dependency with appstacks assignment order

eg. PersonalCommunications works only when it is assigned in first place, but then the OracleDataAccessComponents does not work, also seems that SAPGui does not work correctly and there might be some other appstacks affected

=> is barely impossible to find combination for the appstack assignment to find the correct order when the all assigned apsptacks will work correctly

=> also might be good to understand what has been changed in version 2.18.2 - this was no problem in version 2.15

=> what we have observed during our internal troubleshooting for Appstacks 2.18.2.27 and AppVolume agent 2.18.2.27 is that System Environment Variables under SystemProperties are propagated only from latest attached appstack,

=> while working with Appstacks 2.15 and AppVolume agent 2.15 are propagated all System environment variables under System Properties.

We have opened the Support case with Vmware, after initial call we are waiting for further instructions and troubleshooting session.

Has anyone observed this behaviour and if so, were you able to resolve it?

Thank you.

Re: BSOD for Windows 10 with AppVolume agent 2.18.2

jigocz — Thu, 21 May 2020 13:29:20 GMT

Windows 10 image LTSC - 1809 - OS Build 17763.1158 is windows updates for April 2020,
Vmware Horizon agent is installed with 7.11.0
some other programs - like antivirus has been updated too during Golden (Master) Image preparation.

BSOD for Windows 10 with AppVolume agent 2.18.2

jigocz — Tue, 19 May 2020 09:08:30 GMT

Hello,

we have upgraded the AppVolume agent from 2.15 to version 2.18.2 and started a re-deployment for all VDI VMs, we use Automatic Desktop Pool with Floating assignement, Linked Clone

The Golden image

Windows 10 image LTSC - 1809 - OS Build 17763.1158 windows updates to 04/2020,
AppVolume Agent 2.18.2.27,
Vmware Horizon agent 7.11.0
Vmware Tools 10.3.5 - build 10430147

Appstack template used is 2.18.2
Writable volume used is 2.18.2 - uia_plus_profile

After some time we see the BSOD for SVDRIVER.sys is happening across the environment.

Did you experienced the same issue? what troubleshooting can be done for that svdriver.sys?

Thank you in advance

SVDRIVER Parameters for AppVolumes agent 2.15 vs AppVolumes agent 2.18.2

jigocz — Thu, 14 May 2020 16:38:19 GMT

Hello,

while installed a new AppVolume agent 2.18.2 I can see that there is a change in SVDRIVER Paramaterers from version 2.15

The Parameters ReplicationLevel is in version 2.18.2 with different default value then in version 2.15
There is a new parameter ReverseReplicationList in version 2.18.2

I was searching around in the Vmware Docs - Configuring the SVdriver Parameters ==> Configuring the SVdriver Parameters <==

the listed parameters are not there documented.

Does anyone know or has some experience what the parameters do? what are the options there, recommended values, what are the implications, etc?

Thanks in advance.