VMWare Horizon Client on El Capitan

Macbook Pro Retina 15", Mid 2015, 2.2 GHz Intel Core i7, 16GB RAM, 256GB SSD

OS X El Capitan Version 10.11.2


I use the VMWare Horizon Client (version 3.5.2) to connect to corporate VDI desktops. I'm having a number of issues.


- The VDI desktop consumes all of the connected displays, be it 1, 2 or 3 displays. I find no way to assign the VDI desktop to a single workspace or monitor. I use the Macbook display, one HDMI connected monitor and one monitor connected via a Thunderbolt to DVI adapter.

- The client appears to disconnect when the Macbook goes to sleep. But it doesn't always disconnect cleanly. On more than one occasion I was unable to restart the desktop without intervention from my sys admin.


Lastly, and this is not a VDI issue per se, when I connect my Macbook to the corporate network via Ethernet or wireless, I am just flat unable to print to only of the printers on the corporate network. The Mac is not joined to the domain, is unable to see any printers, and I have to roll the printer add by hand. I am able to define a printer by IP address or FQDN, but all attempts always results in the printer printing the Postscript code and not the print job. These are Ricoh enterprise class printers.


Any and all help would be appreciated in either of these matters. Thank you.

MacBook Pro with Retina display, OS X El Capitan (10.11.2), null

Posted on Jan 8, 2016 11:11 AM

Reply
12 replies

Jan 8, 2016 12:19 PM in response to Bobby Ess

I have found the newer Horizon clients to be, less than optimal. I have reverted back all the way to the View client, as a preference, since it seems to stay connected longer, better, and with fewer issues, over the Horizon client. Currently using the v1.6 View client...happily.


Printers - I set all of my users up on IP based. Very few issues. The users/Macs are members of a domain, and are connected hard wire, but do not use the MS Print servers. In one or two cases, I have used Bonjour for some of the high end HP or Ricoh printers.

Jan 19, 2016 9:53 AM in response to Cmoore01

Thanks so much for your reply (and apologies for the late reply on my part. For whatever reason, I did not get notified of your response). I'm at my wit's end on printing. I've tried all protocols, vendor specific drivers and generic PS drivers (in all combinations) and all I've managed to do at this point is waste about a ream of paper.


Do the View clients have the issue with consuming all connected displays?


Thanks again.

Jan 19, 2016 1:04 PM in response to Bobby Ess

I have had far fewer issues with the view client, and I prefer the v1.6 over the 1.7 or above. I use the View client and have it opened on the side monitor of my iMac, and use the iMac for everything not specifically requiring a windows client (End user Support). I switch back and forth between the Client and the mac all of the time.


Printing, I am at a loss on how to help. I have Ricoh MP5002, 5004 and 2852 series models, all connected to a Windows Print server for the Windows clients (and my VDI), and for the mac users, I connect either IP or through Bonjour. It should be fairly simple for your sysadmin to configure the Ricohs to advertise in Bonjour. I set mine up without looking in any manuals. Might try a reset of your print system on the mac, after verifying you can see the printers in Bonjour, or IP. I print IP on my iMac to the Ricohs, not bothering with the printers on the print server. The issues I have seen with the Rico's is the print job is sent to the printer...and nothing. This is mostly why I set up Bonjour on the printers. IP sometimes was a little flaky, but Bonjour seemed to work more consistently. Trying to use a windows print server with a mac was problematic at best, even with the mac as a member of the domain. Apples to oranges, it seemed like (pun intended).

Jan 19, 2016 1:39 PM in response to Cmoore01

I did that earlier to no avail. I am a VP of IT here at our company and I have several folks on the floor with (unauthorized) Macs on their desktops. I tend to look the other way at this as long as they do their job. These are heavy, tech savvy engineers and no one has figured out the printing piece. My guess is that the Windows print server has some configuration abomination that is preventing us from hitting the printer via IP without intercepting it and nuking it.


I could not agree more - printing should not be this hard. I'm convinced it's our environment here at work.

Jan 19, 2016 2:20 PM in response to Bobby Ess

hmmmm...think you could convince the network folks to allow Bonjour? I know way back when when I played with my routers, and switches, I tended to block all unwanted protocols, to include Appletalk and Bonjour, just because. Wanted a minimum of protocols flying around on my network. For sure, block it at your perimeter, but internally, see if you can get it opened. If for no other reason than to test to see if you can print. Doesn't work, filter again. Does work, have the network/security folks explain why it is blocked internally. The organization I work for is very, very security conscious, and we block a lot at the perimeter, but not so much internally.

Jan 19, 2016 5:28 PM in response to Bobby Ess

Bobby Ess wrote:


I am able to define a printer by IP address or FQDN, but all attempts always results in the printer printing the Postscript code and not the print job. These are Ricoh enterprise class printers.

This would indicate that the printer does not support Postscript. Ricoh has their own printer language and for some models, Postscript and PCL is an option. So as a test you could try adding the printer on the Mac using the Generic PCL driver that is included with the OS. Note that this driver only prints in B&W and at 300dpi by default, although you can change the resolution to 600dpi via the driver settings. If this does print then you know the printer supports PCL at least.

Jan 20, 2016 4:55 AM in response to Bobby Ess

Some success. I had tried adding the printer using the PCL driver previously using IPP but to no avail. SInce I had access to the Ricoh configuration page, I found the WINS server address and added this to the Mac thinking that if I'm not going direct IP to the printer, there might be some interaction here required. I added the WINS server, added the printer using HP JetDirect protocol and using the generic PCL driver. The printer now prints out a black and white printout. Some success. Finally.


Thanks to Cmoore01 and PAHY for all of your help.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

VMWare Horizon Client on El Capitan

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.