Horizon Client includes additional features to help you use remote desktops and published applications on your local client device. Gestures and Navigation Aids VMware has created user interaction aids to help you navigate conventional Windows user interface elements. Using the Sidebar After you connect to a remote desktop or published application, you can use the sidebar to open other remote desktops and published applications. Adjust the Screen Resolution for Remote Desktops and Published Applications You can adjust the screen resolution manually for remote desktops and published applications.
Using Full-Screen Mode If you are using a Surface Pro 4 or Surface Book, you can display remote desktops and published applications in full-screen or windowed mode. Full-screen mode is enabled by default. Configure the Local Zoom Feature With the local zoom feature, you can pinch your fingers together and apart on a touchscreen to zoom in and out inside a remote desktop or published application.
Where these documents are saved depends on your company's network environment. For example, your documents might be saved to a home share mounted on your local computer. Enable Multi-Session Mode for Published Applications When multi-session mode is enabled for a published application, you can use multiple sessions of the same published application when you log on to the server from different client devices.
Prevent Screen Lock After a certain amount of idle time, the client device might dim the display, activate the lock screen, or power down the display to conserve power. You can set an option to prevent screen lock for a remote desktop or published application. Multitasking You can switch between Horizon Client and other apps without losing a remote desktop or published application connection, and you can resize the Horizon Client app so that it takes up part of the screen alongside another app.
Real-Time Audio-Video is compatible with standard conferencing applications and browser-based video applications. It supports standard webcams, audio USB devices, and analog audio input.
You can use a Microsoft Display Dock to connect your Windows 10 smartphone to an external display and mouse. With this feature, you can use Horizon Client just as you would use it on a desktop PC.I am running the latest version of Fusion, After logging in both VM's go to a black screen. This occurred after latest Windows update.
Black screen when logging in to a Horizon virtual desktop (1028332)
I have tried suggestions from other posts but none of them seem to help. I am looking for some more ideas. This is a known issue related with Windows 10 Fall Creator's Update, we are currently working on this, and in the meanwhile, would you please try to disable 3D acceleration and see if it helps. For now, we are running a beta so if you get in touch with support and report this issue we can enroll you and get you the newer tools which should resolve the issue.
I just paid to upgrade to VMWare Fusion 10 today presuming this would fix the problem, only to find it didn't. I reached out and was contacted by a representative from VMware and we setup a remote desktop session where he got onto my Mac and tried to help me out. He tried to repair one of my Windows 10 VMs but after numerous attempts he told me he was unable to fix it and I had 2 options - 1. We tried option 2 and it works only because the new VM was created using an older version of Windows Windows updates had to be disabled.
It is also not the greatest solution because it is a re-creation of my original Windows 10 VM and not exactly like my original.
He acknowledged there were known issues with the file system and I didn't understand how this related to the the video drivers being corrupted. When he created my new VM, he had the filesystem set to full allocation mode to address the known issue.
My latest position is that I am going to get another backup drive and backup what I have right now. Then I am going to take option 1 and restore my full system from my last good system backup before the corruption the Windows 10 Fall Creators update.
Horizon View: Black screen after vSphere 6.5 upgrade (PCoIP / Blast)
And then go from there disabling Windows updates and wait for a VMware solution to come soon hopefully. I wish the VMware and Windows people had worked together and tested this before the Windows 10 release. Perhaps they did.
Regardless, I am very disappointed. I am sorry that everyone else is having to deal with the problem because it is a big time and money waster and we expected more from VMware based on their past performance. I'm just a bit annoyed I paid for the upgrade thinking that would fix it and I'm having exactly the same problem with no real solution in sight. I'll maybe open up a support ticket then. Hi, just tried it earlier, first it was 8. It did not work, still getting a black screen after login.
The windows 10 is a build and after getting the black screen I can alt-control-del to sign out to get back to the main login screen which works. I tried booting up in safe mode and I can go to the desktop screen but everything is missing, when I try and click on the windows icon, it takes a long time then throws a windows explorer execption.
Tried turning off 3D acceleration and also retina unity feature. Even changed the ram etc to see if it was causing the issue. So now I am stuck with using the shift restart on windows 10 login screen and rolling back the windows version then clicking the advanced option of do not update for a limited period.We have been using VMware Horizon View 5. Black Screen for 10 secs and then the connection breaks. Other VMs are fine. Any help will be appreciated.10 Top Troubleshooting Issues for VMware Horizon
Please see the following blog post it's likely to be down to the order of installation of tools and the agent. Horizon View 6.
Install View Agent. This worked well and could be an easy step for Linked Clone Pools. Questions left are. We do have Manual pools with significant number of VMs, and following the above process for each VM individually will be very painful. Do we have a better method to handle Manual Pools? An interactive tools upgrade, deselecting the SVGA driver in the wizard is likely your best bet.
You can try updating the tools install manually with this option first and then doing your agent update and see if that works. Unfortunately, this is kind of the issue with manual pools. If you have the full horizon suite, you could use mirage for the manual desktops. If you manually deselect features in the tools install, automatic updates in the future won't add features you removed. This is an issue with VMware tools and not the view agent. It's an incompatibility with the current tools SVGA drivers and agents older than 6.
I believe there should be a FIX for this somewhere as we might have to Update the VMware Tools quite often, and every time this lengthy process would be hassle. If you move to 6. As you mentioned earlier, you have not had this issue in the past with tools upgrades and right now, we have to assume that VMware won't have this happen again soon. The fix right now is in fact to upgrade to the latest 6.
I recommend you testing 6. I have had issues with a few apps breaking after installing the 6. Is this the correct approach? Because we have quite some big environment with lot of stand alone VMs and customizing the VM Tools upgrade individually will be a hassle. In my experience with the current version of view, yes.
However, I would test that all of your applications still work with the 6. I have been having some problems with applications crashing with any agent newer than 6.Then 1 or 2 minute later, the session is disconnected. If we reset the machine, then the conection is perfect. We can connect to this machine a lot of times without problems until we refresh o recompose the machine. Then the black screen appear again until we reset the machine. We try to install vnc in the desktop to see if we can connect via vnc when we have a desktop with black screen.
In this situation, via vnc the conection is perfect. We can work with the desktop normally, but via view client, the black screen goes on. So I just wanted to confirm that part. Also to confirm, are you adding the Server instance as a RDSH farm then adding a desktop pool that uses that farm? The blank screen only happen after login via PCoIP. The sessions disconnects after login after some seconds via RDP.
Are you running any firewalls in your environment? We started seeing this issue happening intermittent in our environment too, this fixed it for us:. When we reset reboot the machines, then desktop connects perfect via RDP and PCoIP, and when the desktop is refresh o recompose, the problem is there again.
Please enter a title. You can not post a blank message. Please type your message and try again. This problem was in connection server 6. We update to 6.
Any help? ESXi 6. I have the same question Show 1 Likes 1. This content has been marked as final. Show 6 replies. Hi grossag.After we updated one VM Windows 10 to the latest versionevery morning we had to restore the VM of 10 days back to get it working.
It's been a while since I deployed a new one, but as I recall there are steps that take a long time. Well so far this has been as easy as a drunk falling off a stool. I did think of a question though. I am still using the free ESXi licenses.
Do I need to use my Essentials license on the hosts first or can I do it after? I would get vCenter running, license it, then add the hosts and license them.
It'll probably license them when you add them. Then like Rod says Then one of the few things to check is the VMware Tools Do you get the black screen from an RDP session as well as from the console?
Do you see any messages indicating MKS is unable to connect? If so, you may have a port blocked that needs to be open. Failed to perform post-backup application-aware processing steps Details: RPC function call failed. Function name: [BlobCall]. Target machine: [Win RPC error:There are no more endpoints available from the endpoint mapper.
Code: ". Get answers from your peers along with millions of IT pros who visit Spiceworks. Dear all, After we updated one VM Windows 10 to the latest versionevery morning we had to restore the VM of 10 days back to get it working. ESXI 6. Best Answer. Ciscoguy Jul 19, at UTC. We found 6 helpful replies in similar discussions:. Fast Answers! Bryan Doe May 15, Is that normal? Was this helpful?In a recent project, I just run into the problem that a vSphere upgrade from 6.
The users just got a black screen after connecting to the desktop pool. After switching them to RDP as display protocol it worked directly fine again. Screen DMA is disabled by default in virtual machines that are created in vSphere 6.
Download  VMware Horizon Clients
View requires screen DMA to be enabled. If screen DMA is disabled, users see a black screen when they connect to the remote desktop. When Horizon 7 provisions a desktop pool, it automatically enables screen DMA for all vCenter Server-managed virtual machines in the pool.
In my case the environment has been on version 6. Not possible via the HTML5 client btw argh! Please note, that you need to power off the VMs first before you will be able to modify this setting. Thanks a TON! Anyhow, just want to say thanks for the post!
Thank you! Adding this entry fixed it! You saved me time! Thanks again! Quick question, we migrated to VCenter Server Appliance when we went to 6. Notify me of follow-up comments by email. Notify me of new posts by email. This site uses Akismet to reduce spam.
Learn how your comment data is processed. Home About Contact Follow me on Twitter.Everyone has a laptop or a Surface, with the Horizon View Client ver. They open the client, connect to their assigned VDI vm machine. Everything works fine, except 2 to 3 times a day sometimes more, sometimes over 2 daysthe screen FREEZES for a second or two, then all black, then within 30 seconds to 2 minutes, it pops back to normal. All users make use of 2 to 3 monitors including their laptop screen.
The mouse and keyboard are not affected, as you can see if you were typing or mousing during the incident. We use a master image, then clone that for all our VDIs, so everyone should have roughly the same settings and devices. We are using vmware ESXi 6. We don't like RDP anyway. Please, any suggestions, advice, tips? How about where to look to see the screen freeze recorded in a log?
This is not going to be easy to troubleshoot.
Does it affect all View users? All users of this configuration laptop plus external monitor? Are all these users on the same network? I would say that this is something vROps for Horizon might help with as it gathers diagnostics for each PCoIP session, including latency and dropped packets. The thought is that 60 seconds of not-connection or packets arriving out of order which PCoIP also considers a "loss" are causing this.
The remaining entries in the log look just like a startup sequence for all the monitors. His log is clean from the Imaging Timer expiry. We are a CAD shop, we gots to have the 3 monitors, high resolution is our bag. The problem was much worse using Horizon5, on Horizon6 which some people are on, it's a lot better, but the disconnects bother a lot of our users.
We have all Alcatel 10gb switches both on the backbone and to each cubey, of course the users computers don't have 10gb NICs in them Our network is not that complex, only make use of 4 VLans. One of your users is going to love