Slow Provisioning

[krismcewan]

Anyone else got issues with Non persistant desktops being provisioned really slowly?

our client seems to be taking about an hour to Destroy the previously used 12 desktops and reprovision them.

The enviroment is an education facility and to have the desktops destroyed after each session is key to their security plan. Unfortunately as there can be up to 5 sessions a day and 200 clients this issue will cause so many problems.

Any help appreciated

VCP, VTSP4, VSP4, MCSE, MCTS, IBMBCE and anything else I can learn.

[Linjo]

What version of View is your customer using?

Full or linked clones?

On what kind of storage?

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[krismcewan]

It has View 3.1.1 all round.

Storage is ISCSi Sun san

memory on 2 VDM connectors is 3gb. CPU is 2

vCenter for the desktops is 3gb and 1 cpu.

Antivirus was running and we have uninstaled that.

VCP, VTSP4, VSP4, MCSE, MCTS, IBMBCE and anything else I can learn.

[admin]

What is the size of the drive for the desktops?

-Ivan Weiss

Please award points for "correct" or "helpful" answers if you find the information I have provided to be useful.

[Linjo]

Full or linked clones?

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[krismcewan]

Desktops are around 10gb for the Gold Build and yes they are all linked clones.

San is ISCSI and connected with 2 1gb connections fully redundant. Core network is 1gb and 100mb to DTU's

vCenter controlling Desktops is Virtual as is the 2 View connection brokers these are on the exisiting Vi3server enviroment. the VSS is Physical.

Upping the memory on the Vcenter and View Brokers have speeded things up slightly.

Chris

[krismcewan]

Ok the provisioning is still slow.

have a few things to check like Datastores, San I/o's but its still takign an hour to delete and reprovision about 12 machines.

[patten_aaron]

There could be a number of reasons why things might be slow. Could you post the event log from the connection broker? That would give us a task list and time line to inspect quickly. Generally you have a couple of distinct processes that have to happen in a serial manner:

1. Power down desktops

2. Destroy desktops

3. Copy new replica (only if rebalancing, refreshing or recomposing)

4. Deploy new desktops from replica

5. Power on and Register new desktops

6. View Agent connect to broker and become ready for client connection

When you look at the tasks in your environment is there one of these tasks taking an extremely long time or is everything slow?

~Aaron Patten

Please award points for helpful answers. I got kids to feed

[krismcewan]

Well it seems there is a problem with Composer 1.1

A VMware Consultant in Scotland

If you think I'm right or helpful award me some points please

[cdickerson]

Try setting the PnPtimeout like explained in this post. I usually use 90 seconds.

http://communities.vmware.com/message/1226270#1226270

-Craig

[krismcewan]

there is a new View Version just out that seems to correct this

3.1.2

A VMware Consultant in Scotland for Taupo Consulting

www.taupoconsulting.co.uk

If you think I'm right or helpful award me some points please