VMware Horizon Community
roneng
Enthusiast
Enthusiast
Jump to solution

after upgrading view to 5.2 , linked clones pool fail to provision desktops

Hi all

I hope someone has an idea,

i was running 5.1.1 environment including composer, and deployment was working with no issues.

After upgrading to 5.2 (including composer) and the agents on the parent vm the linked clones deployment fails.

the vm's are created but the customization fails, if i do log in to them, i can see that there is no nic. which is weird.

now the vm does of course have a nic, but for some reason the os does not see it.

I am using windows 7 64 bit and vmxnet3.

if i revert to the old agent 5.1.1 it works.

Does any one have a clue?

Thanks

Reply
0 Kudos
1 Solution

Accepted Solutions
memaad
Virtuoso
Virtuoso
Jump to solution

Hi,

I think this KB address your problem http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200731...

Else do this  "Can you build new VM with e1000 network adapter and view agent 5.2 for testing."

Regards

Mohammed

Mohammed | Mark it as helpful or correct if my suggestion is useful.

View solution in original post

Reply
0 Kudos
4 Replies
memaad
Virtuoso
Virtuoso
Jump to solution

Hi ,

Do you see nic in device manager ?

Regards

Mohammed

Mohammed | Mark it as helpful or correct if my suggestion is useful.
Reply
0 Kudos
roneng
Enthusiast
Enthusiast
Jump to solution

Hi Mohammed,

No i dont see it in device manager.

I tried removing the tools and agent and reinstalling and that did not help.

Thanks

Reply
0 Kudos
memaad
Virtuoso
Virtuoso
Jump to solution

Hi,

I think this KB address your problem http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200731...

Else do this  "Can you build new VM with e1000 network adapter and view agent 5.2 for testing."

Regards

Mohammed

Mohammed | Mark it as helpful or correct if my suggestion is useful.
Reply
0 Kudos
roneng
Enthusiast
Enthusiast
Jump to solution

Thanks you very much

That fix did it.

Reply
0 Kudos