Custom Appstack

[mario_981]

Hi Everyone,

We had a requirement wherein we needed a custom appstack template of size 60GB.

We had a Windows Server 2012 R2 machine which we used to create the custom appstack template of size 60GB using the 20 GB default template.

Once all done with the creation of new template, we started the capture using 60GB template.

While installing the app , msi installer says error 2755 unable to detect the file. Then I ended this failed capture session and disconnected the appstack.

Once again I tried to install application but this time on OS directly, then no such errors were reported.

Then I tried to connect the good old 20GB template and tried a capture, even then I get the same error.

Anyone came across such scenario , Please suggest.

[Anobix67]

to not creep too far from the discussion point, what are you seeing as the video issue?

[VDINinja311]

Anyone know if the "fix" they put into the 2.16 Agent was just an entry for msiexec into the HookInjectionWhitelist key?

After comparing the contents of the HookInjectionWhitelist from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\svdriver\Parameters between a master image with 2.14.2 and 2.16 agents installed I have noticed there is a single difference. The master image with the  2.16 Agent has an extra line with *msiexec.exe||* . This doesn't exist on a master image with 2.14.2 agent installed.

Willing to bet this could be the "fix"...

[VDINinja311]

Can confirm that having a 2.14.2 Agent and adding the *msiexec.exe||* into the HookInjectionWhitelist key and installing the latest Cumulative updates does seem to work fine together. Going to keep testing to make sure though.

[VDINinja311]

To update, no ill effects have been found. We moved this workaround into production. App Volumes support probably wouldn't approve of this

[jamorris27]

This has definitely helped me.  I was at a stand still, and not able to update any of my applications.

Thank you!