JackMac4's Posts

Yes, you'll want to disable redirection for this adapter and let it present itself as a second monitor for the Horizon Client.
Does it not work for both HTML and thick client?
Have you added a global entitlement for the physical desktop?
Precisely. We normally try to ensure backwards compatibility, but we don't guarantee it.
I don't believe it's supported. There's a level of obfuscation with many USB devices, so for example an audio device is usually presented as a generic usb audio device. Depending on the device, I... See more...
I don't believe it's supported. There's a level of obfuscation with many USB devices, so for example an audio device is usually presented as a generic usb audio device. Depending on the device, I could see the nested session having trouble identifying the device. I'd have to double check with our USB gurus, but I don't believe USB redirection was ever designed for nesting.
Are you tunneling through the Connection Server or making direct connections?
With Horizon 6.2 just released it should work with RDS for USB storage devices over the client drive redirection channel, but devices still don't work I believe.
Specifically what Grid K2 driver are you running?
In my 6 years working with Horizon/View I've never heard of a major KMS issues. There are customers that run redundant with SRV records that you indicated, but KMS does a pretty stand up job and ... See more...
In my 6 years working with Horizon/View I've never heard of a major KMS issues. There are customers that run redundant with SRV records that you indicated, but KMS does a pretty stand up job and I've never once had a customer have it impact their environment. Not saying it couldn't be a problem, just saying I think that's why it's not a priority...it "just works" 99.9% of the time from my experience. Normally activation issues are related to customers accidentally using MAK, which is not supported.
I think you're likely reaching the Windows limit on cloning. Yes, there is one. Rather than clone your base copy, why not just create a baseline shapshot. That will save you a SID regen and might... See more...
I think you're likely reaching the Windows limit on cloning. Yes, there is one. Rather than clone your base copy, why not just create a baseline shapshot. That will save you a SID regen and might make things working.
You're asking to do nested USB redirection which will not work.
I would take a look at the Thinprint logging to see what is happening to the job. You can enable it by looking at this KB. VMware KB: Enabling ThinPrint logging in VMware View Manager
In general, the Clients will work with any version. There are some specific things that can require newer clients but in general clients are backwards compatible. The newer the version, the more ... See more...
In general, the Clients will work with any version. There are some specific things that can require newer clients but in general clients are backwards compatible. The newer the version, the more features that will work depending on the CS/Agent. We always recommend running like versions or in many cases the newest client. The Agent and Connection Server should remain in the same version family unless making the upgrade transition. If your quesiton is, can I run 3.5 while I make the jump from 5.2 to 6.2, the answer should be yes.
CentOS 7 is not supported yet, but 6.6/6.5 should work. The official distribution at Download VMware Horizon Clients should work with those OSes. In terms of getting it to install in CentOS7 are ... See more...
CentOS 7 is not supported yet, but 6.6/6.5 should work. The official distribution at Download VMware Horizon Clients should work with those OSes. In terms of getting it to install in CentOS7 are you running the installer under su I presume? The newly released guide might be of help to you https://www.vmware.com/pdf/horizon-view/horizon-client-linux-document.pdf
The connection server is the one, but you also have to specify that port on the client when you connect. Replace the Default HTTP Ports or NICs for View Connection Server Instances and Securit... See more...
The connection server is the one, but you also have to specify that port on the client when you connect. Replace the Default HTTP Ports or NICs for View Connection Server Instances and Security Servers I'm assuming you also did the remap? Change the Port Number for HTTP Redirection Make sure that the connection server is pointing to the new location and the client as well. The agent should be fine.
View and Mirage are separately managed, except that you can set the mirage server for a View desktop pool.
Yes, that is correct. the SS's are paried to a CS, but once you've connected to the broker, it can channel the SITE B's desktop over the back channel and present it to the site A external client.... See more...
Yes, that is correct. the SS's are paried to a CS, but once you've connected to the broker, it can channel the SITE B's desktop over the back channel and present it to the site A external client.
You don't need to split the luns per replica. I would put all your replicas on SSD, and yes they can share a LUN across many pools. You'll just want to have multiple LUNs that the pool(s) can ... See more...
You don't need to split the luns per replica. I would put all your replicas on SSD, and yes they can share a LUN across many pools. You'll just want to have multiple LUNs that the pool(s) can balance over. Create as many LUNs as you need to spread things out, but really think about spindles and IOPs. 128 is a guideline, but not a hard rule. It's all about having enough IOPs to serve the requests you'll get during peak use. I would go with SAS if you can, but SATA is acceptable - it just all affects user experience. Consider using SATA for task workers or people that don't generate a lot of storage use. Trial and error and user acceptance would be good to go through here if you haven't yet.
Centosuser wrote: so in this matter i can't use port 443. 443 is been used for exchange already. its not possible to change the https port of the horizon to a different port than 44... See more...
Centosuser wrote: so in this matter i can't use port 443. 443 is been used for exchange already. its not possible to change the https port of the horizon to a different port than 443? http://kb.vmware.com/kb/2032761
Hofkicks wrote: I am updating my test environment this week so I will post my results before Friday. FYI, I reached out to the TSE on your case and got the relevant bugs and I think he ... See more...
Hofkicks wrote: I am updating my test environment this week so I will post my results before Friday. FYI, I reached out to the TSE on your case and got the relevant bugs and I think he may be confusing this with a very similar issue with View 5.3. Based on what I quickly read, I don't believe an upgrade will resolve the issue, but I can't be 100% sure as of right now. My recommendation would be to try the upgrade, and if it doesn't resolve the issue, reopen the case and let them know the issue is different. If the TSE you speak to needs any more details of what you're dealing with, have them reach out to me directly and I can show them.