emik85
Contributor
Contributor
‎07-21-2022 12:36 AM

Horizon drive sharing

Hello!

I use VMware Horizon Administrator 8.4.0 build - 19067837 Version 2111, VMware Horizon Agent 8.4.0 build 19066669 Version 2111.1 and VMware Horizon Client 8.4.0 Build 18968194 Version 2111.

I have two shared folder form local pc

horizon1.png

When I first connect (by VMware Blast) to VDI (Instant clone) this folder don't rederect to vdi

horizon2.png

but if i close this vdi by button "cross" and reopen this VDI, this folder rederect to VDI by network disk.

horizon3.png

Thanks for your help !

Emil

Reply
0 Kudos
Mickeybyte
Hot Shot
Hot Shot
‎07-21-2022 01:16 AM

Hi @emik85 ,

I've seen the same behavior once at a customer. We finally found out it had something to do with the Horizon client installation. The clients had been upgrade several times over the time from versions 4.x to 5.x. We fixed it by uninstalling the Horizon Client, removing any traces from the client from the registry and from the C-drive (program files, programdata), reboot and then reinstall the latest version. 

Hope this helps for you too.

 


Regards,
Mickeybyte (ITPro blog)

If you found this comment useful or an answer to your question, please mark as 'Solved' and/or click the 'Kudos' button, please ask follow-up questions if you have any.
Reply
0 Kudos
emik85
Contributor
Contributor
‎07-21-2022 01:25 AM

Hello Mickeybyte

Thx for your answer, i will try your recommendation

Reply
0 Kudos
emik85
Contributor
Contributor
‎07-21-2022 07:05 AM

clear reninstall did not solve the problem.

rollback to horizon agent 7.12.0-15805436 helped

Reply
0 Kudos
FelixYan
VMware Employee
VMware Employee
‎07-21-2022 05:31 PM

Hi Emil,

From the description, CDR doesn't work for first remote desktop connection and it can work well on the reconnection. And you are using 8.4 Windows Client + 8.4 Windows Agent + Blast protocol.

  • What's the Windows OS version on Agent?
  • Have you tried this with 8.5/8.6 Client/Agent?
  • What's the behavior when switching to PCoIP protocol?

Suggest to use SR to track this issue as debugging log is needed to get the root cause.

 

Reply
0 Kudos
Mickeybyte
Hot Shot
Hot Shot
‎07-24-2022 11:42 PM

@emik85 

You might want to try the following on your VDI base image: 

  • uninstall Agent + reboot
  • uninstall VM Tools + reboot
  • install VM tools + reboot
  • install Agent 8.4 + reboot

Then push the new image to your desktop pool and try again.


Regards,
Mickeybyte (ITPro blog)

If you found this comment useful or an answer to your question, please mark as 'Solved' and/or click the 'Kudos' button, please ask follow-up questions if you have any.
Reply
0 Kudos