Provisioning desktop fails with App-v 4.5 client

[heinrich82]

Did anybode tried to provisioning a Windows desktop with App-v 4.5 client in the image?

I've tried it with Windows XP and 7 but after creating the desktop pool, provisioning fails.

In the View Manager I see a error: View Composer agent initialization state error (6): Unknown failure (waited 0 seconds).

We are using View 4 and also checked Vmware KB: 1011653.

The App-v 4.5 client is installed before the View Agent.

[AUPhil]

We have the same issue with App-V and messages from composer at

customization and user login. We can connect as usual from view,

and App-V appears to work, but every VM in a linked-clone pool

will show "error" in view admin (and so more machines will start until the pool limits out).

Surprisingly, using a v3 agent eliminates the composer msgs. Both v3

and v4 have issues with the userinit registry entry, although with v4 it

is only a trivial issue with a missing comma. Only v4 has the composer

issue.

Any Workarounds?

I found nothing about View 3 or 4 NOT supporting App-V clients in a linked clone (composer) pool.

[heinrich82]

Hello AUPhil,

We've tested a little bit and we have noticed that when you install App-V, disable all App-V services and then install View Agent customizing goes good.

The only thing you need to do is create a computer startup script which change the services and start them.

One problem then is we don't see which user logons which server, so persitent desktops is not working then. Also the View Manager cannot see Active Sessions.

I've spoked with VMware and explained the problem. They will look at it, when I have more information, I will let you know.

[AUPhil]

Thanks. In fact, we've been able find a workaround using your basic

idea to start services late. We suspect your report on remaining issues

may involve the "missing comma" problem in the userinit registry

variable.

In short, the following sequence appears to work around App-V problems

for linked-clone deployment:

1. Install App-V and view agent as directed.

2. Add the missing comma in userinit.

3. Disable autostart on the App-V client.

In limited testing, there are no errors from composer, view tracks

connections properly, and App-V works.

[heinrich82]

AUPhil,

After a lot of mail traffic between me and VMware, they told me that another customer had the same problem.

The customer discovered that installing the older agent(3.1.2) in the desktop allowed the two services to run okay.

I'm testing it right now.

Also Vmware have told me that it is a bug and they are trying to solve it.

Greetz Heinrich82

[GWalmsleyNICE]

Hi,

I am the 'other customer' referenced by VMware technical support. Using the V3.1.2 agent does allow the machine to compose, but you then have different issues with not having PCoIP etc.

I am going to try the fix of not having the App-V Client automatically starting.

I am glad they have told you this is a bug, as I have not been able to get them to admit it.

Graham

[GWalmsleyNICE]

Hi AUPhil,

In your workaround, step 3 to disable autostart on the App-V client, I assume this is the client that appears in the bottom right near the clock, and not the service?

Thanks

Graham

[AUDarrel]

It is the service where we disable autostart. I don't think show-appv in the system tray matters.

[GWalmsleyNICE]

Hi AUDarrel,

If I disable the service, then the machine composes ok, but obviously no app-v applications will work. Are you running a script or similar to re-enable the app-v services once the machine has composed, or are you setting the service to manual rather than disabled?

Thanks

Graham

[AUDarrel]

We set manual start for the "Application Virtualization Client", and in app-v the refresh is "on user login". No scripts or similar are used.

[JessicaD42]

Graham,

Should you require additional assistance and guidance, Microsoft does have an official Windows 7 Support Forum specifically for IT Pros located here http://tinyurl.com/7jq7ps . It is supported by product specialists as well as engineers and support teams. You may want to also check the threads available there for additional assistance and feedback.

Jessica

Microsoft Windows Client Team

[Zsoldier]

I did as stated in other posts and set the "Application Virtualization Client" service to manual, then added the following lines to a batch script that I have on the root directory of the gold image then set the pool to use that as a post synchronization script and this annoying error went away.

sc config sftlist start= auto

sc start sftlist

Configuration:

View Manager/Agent 4.0.1 Build 233023

View Composer 2.0.0 Build 210930

vCenter 4.0 U1 Build 208111

Chris Nakagaki (Zsoldier)

http://tech.zsoldier.com

Message was edited by: Zsoldier

[Manjari]

AUDarrel, just wanted to say thanks for providing your solution here. This saved us a lot of time puzzling over how to fix problems during AppV testing after a recompose! Setting AppV services to manual and publication refresh to "on login" has worked perfectly for us, as well. I generally stop the AppV services and then restart the VMware Agent service for good measure before I shut down the master template to take a snapshot.

[moreMILK]

hi all,

despite the delay, I think as a solution can be very valuable.

you can simply try to change start type from Automatic to Automatic (Delayed).

this should be sufficient the resolve the provisioning issue that your refer to.

I had the same problem and has been solved with this workaround, without script, policy or any other trick.

if someone will have the opportunity to try, please let me know.

enjoy virtualizing

Andrea

[brewercm]

This solution worked for me!  Thank you! 

Automatic (Delayed Start) of the Application Virtualization Client Service.