Articles on this Page
- 01/09/19--15:26: _Re: Desktop Disconn...
- 01/09/19--15:32: _Re: UAG 3.2.1 - Rad...
- 01/09/19--17:55: _Re: Desktop Disconn...
- 01/10/19--04:06: _Modify CPU and Memo...
- 01/10/19--04:12: _Re: Modify CPU and ...
- 01/10/19--05:13: _Re: Modify CPU and ...
- 01/10/19--05:17: _Re: error occured d...
- 01/10/19--05:41: _Re: error occured d...
- 01/10/19--07:23: _Re: Modify CPU and ...
- 01/11/19--06:09: _Disabliing RDP
- 01/11/19--07:22: _Re: View Mandatory ...
- 01/11/19--08:33: _Re: UAG 3.2.1 - Rad...
- 01/11/19--12:11: _Re: Disabliing RDP
- 01/11/19--12:13: _Re: Disabliing RDP
- 01/11/19--12:37: _Re: Disabliing RDP
- 01/11/19--13:22: _Re: Disabliing RDP
- 01/11/19--09:27: _Re: Does anyone exp...
- 01/11/19--20:20: _Re: Disabliing RDP
- 01/12/19--04:03: _error horizon view ...
- 01/12/19--04:37: _Re: error horizon v...
- 01/09/19--15:26: Re: Desktop Disconnected
- 01/09/19--15:32: Re: UAG 3.2.1 - Radius Prompts for token first
- 01/09/19--17:55: Re: Desktop Disconnected
- 01/10/19--04:06: Modify CPU and Memory of floating pool Desktop
- 01/10/19--04:12: Re: Modify CPU and Memory of floating pool Desktop
- 01/10/19--05:13: Re: Modify CPU and Memory of floating pool Desktop
- 01/10/19--05:17: Re: error occured during vCentre Operation
- 01/10/19--05:41: Re: error occured during vCentre Operation
- 01/10/19--07:23: Re: Modify CPU and Memory of floating pool Desktop
- 01/11/19--06:09: Disabliing RDP
- 01/11/19--07:22: Re: View Mandatory Profile
- 01/11/19--08:33: Re: UAG 3.2.1 - Radius Prompts for token first
- 01/11/19--12:11: Re: Disabliing RDP
- 01/11/19--12:13: Re: Disabliing RDP
- 01/11/19--12:37: Re: Disabliing RDP
- 01/11/19--13:22: Re: Disabliing RDP
- 01/11/19--20:20: Re: Disabliing RDP
- 01/12/19--04:03: error horizon view : all the reactive machines are occupied
- 01/12/19--04:37: Re: error horizon view : all the reactive machines are occupied
The issue is that Horizon Client 4.10.0 dropped support for TLS 1.0 which all versions prior to 6.2.1 used. The last Horizon Client to officially support 5.3.x was 4.4 which was released on 16 March 2017. There is a workaround available for iOS but I haven't seen one for Mac. Jon Holloway or kdenike is there a workaround for Mac or Windows that you can share?
Horizon View 5.x went end of general support on 2016/09/14, end of technical guidance on 2018/09/14 and end of availability on 2013/09/30 for View Enterprise. I would urgently advise upgrading to 7.x given that Horizon View 6.x goes end of general support in less than 6 months (2019/06/19).
It depends on your RADIUS server and what it's configured or capable of doing. We use Duo, it first prompts for AD username/password and then the user receives a MFA push to their device/SMS/phone call.
The only workaround for the desktop clients is to stay on the 4.9 client. We do have a workaround for the mobile clients which I am sharing as customers reach out. We really want to work with them to upgrade their Horizon server. Apple, Microsoft and Google are also dropping TLS 1.0 (and 1.1) early next year. Customers will be much better off if they do this work now.
Excuses if there is already thread about this.
I have request to change the memory and CPU of all VDI desktop.
It is floating pool and desktops are refresh every time user logoffs.
Would you advise best way to approach this?
e.g. Would below be the right approach?
1. I have to shutdown the master image. Change CPU and Memory. power it on.
2. Take snapshot
Any changes are required in the pool settings ? I guess I have to ask user to logoff?
Is there a KB on it ?
You're correct, just remember to shut down your VM before taking the new snapshot.
No changes to the pool settings are needed, but you will need to recompose and point to the new snapshot.
I`m also thinking about using new pool as only a few people need more RAM.
In this case, can I clone existing parent machine? but then the snapshot would be consolidated.
Or I have create new parent image, bring image to same level as old parent VM ?
This can be due to a number of things. Does the error show anything else? If not you can check the logs of your composer server under c:\programdata\vmware\view composer logs
Hello and welcome. Please take a moment to read the post in my signature below and then respond.
You can clone the original image without any issues (you could even use the same parent, pointing to different snapshots as the vm config is also part of the snapshot, but that could make it harder for other admins to understand).
We only use PCOIP in our environment. I would like to disable the RDP service on all the VM's using group policy. Any side affects? Mainly doing this because security scans are complaining about self-signed certificates, hash values etc...
WMIC PATH win32_UserProfile WHERE LocalPath="c:\\users\\%username%" GET Status
If the output of this command is 4 your profile is mandatory.
Thanks for the response.
We use Symantec VIP for radius auth which provides a numeric token that doesn't match a users AD password, so still get challenged at the connection server end.
I'll head down the IDM route then. Was hoping not to increase the infrastructure to support remote access to desktops but I'm sure we'll end up leveraging other features of Workspace in the future.
This document should be what you're looking to doing. This is only for desktops and not possible with published apps (rdsh) servers.
I've seen that article, but I don't think that will disable the RDP service and the scan will find that RDP is still active. I just want to disable RDP all together. I'm not sure if there are any consequences.
The horizon agent needs the service to be running. You cannot stop it.
If you still have the windows firewall enabled, you can block incoming traffic to remote desktop. Outside of this create a test pool and test it, I don't think there is anything that specifies the effect of this. If you need concrete clarification you may want to open a support ticket. What we did was place our virtual desktops its own firewall context on the network and just prevent rdp from everywhere.
We too are experiencing a similar issue - the gold (or master) Win10 1809 image works fine - I can reboot it and it completes the reboot in less than 30 seconds (about 26 seconds). However, any linked clones we create take upwards of 30 minutes for a reboot to complete! I've tried:
- Linked clones using EFI
- Linked clones using BIOS
- Linked clones with EFI & Secure Boot
The other interesting thing, is if I used vSphere to console to a linked clone VM where no one has logged into, and reboot the VM, it takes about 2min. 30 seconds - however, once someone logs into the VM and reboots, it takes anywhere from 15-30 minutes for the reboot to complete. It doesn't matter if it's using BIOS or EFI (secure boot is turned off for EFI).
I have a support case open with VMWare to try and figure this out - if I find a solution I'll definitely let you know.
EDIT: we're also running ESXi 6.7 U1 w/Horizon 7.5.1 (both composer and connection servers) w/latest VMWare tools from the hosts.
Our Nessus scan reported the same 6 or so rdp related findings. We applied a group policy that disables rdp and haven't seen an issue.
Please kindly help me to resolve my issue with Horizon View. I setup Vmware Horizon View 7.1 and i created a manual pool. But when i tried to connect on my VM in my Vmware infrastructure since my horizon client, i get this error " Unable to start from the pool for user '$myuser ': all responsive machines are in use. When i check events on Horizon view i see that "all the reactive machines are occupied".
Since i try solve it but i can not. I'm new on Horizon view
If the pool is completely manual you may have to assign each user to a desktop.