Shreyskar's Accepted Solutions

It is supported for normal horizon deployments as well. Cascade mode support was introduced in UAG for organizations where DUAL DMZ mode is mandatory. In this deployment mode, a Unified Access Gateway is deployed in the outward facing DMZ and acts as a Web Reverse Proxy. Then, another Unified Access Gateway is deployed on the internal DMZ, and acts as a Horizon edge service. External users connect through the first DMZ layer, then the second, before accessing the internal network. If you don't have any such compulsion in your org, you don't need to setup cascade mode deployment. 

In most of the scenarios 'Run flexengine as GP client side extension' is preferred over running it as 'logon script'.By running FlexEngine as Group Policy Extension, settings that User Environment Manager manages are applied earlier during the logon phase rather than when running FlexEngine from a logon script.It also works better while handling windows Multilanguage User Interface. However in special scenarios, you can run DEM as a logon script. -OfflineImport parameter is OPTIONAL parameter when you run DEM through logon script instead of 'group policy client side extension'. This parameter is required only if your computers goes offline.

Hi BSKris > For PCoIP connections you need to enable below group policy in PCoIP ADMX template: Enable access to a PCoIP session from a vSphere console: PCoIP General Settings > For Blast you need to set Screen blanking GPO: VMware Blast Policy Settings Screen Blanking Specifies whether to have the desktop VM's console show the actual desktop that the user sees or to show a blank screen when the desktop has an active session. The default is to show a blank screen.

UEM 9.2 which is quite old and end of general support now.Not related to current issue but wanted to update you to upgrade UEM to 9.11 . Do you see the same error for all the shortcuts created on desktops Or is it happening for specific ones? What if you manually create a shortcut while you are connected to a session and delete it? I suspect you will not be able to even 'rename' the shortcut if it is a permission isuse. Desktop is getting redirected and user should have full control over it. Try disabling any third party antivirus or security software and check. Confirm the security permission on the shortcut once. If issue still persist, check if UAC is enabled or not. If it is enabled, disable it with the help of your AD team and test.

Hi vmmedmed In Horizon Administrator, select Users and Groups, Click the Remote Access tab. Do you have any user/group added here? If yes, remove all from here and test again. This setting ONLY allows access to specific users/groups from external network restricting access for all other users and groups regardless of the entitlement set on desktop pool level.

Hi virgo731 Persistent disks must always be reconnected to the OS that was used when they were created.You cannot detach a persistent disk from a Windows 7 linked clone and recreate or attach the persistent disk to a Windows 10 linked clone. But you can migrate your users profile from Windows 7 desktops to Windows 10. You can also use 'Robocopy' to copy the user data. Migrating User Profiles with Horizon Persona Management User Profile Migration Overview

You are correct. vGPU is not yet supported with linux based instant clones. If you want to use vGPU powered linux VDIs, you need to stick to dedicated VMs. vGPU is supported on the Linux distributions and NVIDIA graphics cards listed on Supported Products :: NVIDIA Virtual GPU Software Documentation

High level steps to migrate connection server to 2019 OS will be as follow: > Take a snapshot of all CS, composer server including composer DB backup and connection server ADAM database VMware Knowledge Base > Install windows 2019 CS as a replica to existing 2012 server. > Once installation is finished, make sure replication is working fine between both servers by running repadmin command. This is critical before moving forward. VMware Knowledge Base > Do the same for remaining 2019 servers. > Decommission existing 2012 servers following VMware Knowledge Base . This should done as early as possible otherwise ADAM database may get corrupt since 2012 and 2019 server will be using different AD LDS schema and keeping both in replication for longer run may cause conflicts. > After this you can migrate composer to 2019 server as below: On new composer server, prepare the ODBC connection and create a system DSN to point to view composer DB. On the old server, stop view composer service. Install view composer on new server and point it to the ODBC. Once installation is finished , login to view admin page. Navigate to View configuration > Servers > Edit > View composer >Edit and put the new server FQDN name and reauthenticate with user name and password > Click on 'Verify server information'    > Ok. Test the provisioning now. In case of any confusion or doubt, please contact vmware support.

Hi MrJeff85 Though it is not supported, but based on error stack it seems installation is failing while writing to hosts file. Change the permissions for the hosts file (C:\Windows\System32\drivers\etc\hosts) on the system from read only to read/write and check if it helps.

Hi MaxStr Run the command from this location on one of the connection broker : C:\Program Files\VMware\VMware View\Server\tools\bin vdmadmin -A -d desktop-pool-name -m name-of-machine-in-pool -resetkey Note : To run the above command, open Command Prompt as Admin by selecting "Run as Administrator". 2. Restart the virtual desktop on which the command was issued. Check now if it shows 'Available' in View admin page.

HI nsousaarlingtontx You are looking at the right documentation Quick-Start Tutorial for VMware App Volumes | VMware Once you have assigned the appstack to the RDSH computer OU (RDSH only support computer-based assignment for appstacks: VMware Knowledge Base ), you can create a new application pool in horizon view and select the remote applications from the AppStack assigned to the RDSH server.

As mentioned in last comment both versions are quite old and no longer supported. You can try below and see if it helps, this will actually force the vcenter certificate to be trusted across all connection servers: Export  and save the vcenter certificate from the browser. Import above certificate in 'Trusted root cert authorities' on ALL connection servers and on composer server as well. Restart connection server services. Restart view composer services Check now if it shows green or allows you to manually verify.

Hi jamie20 Help desk tool is a part of Horizon connection server NOT horizon agent. You access it through View admin page and it is enabled by default during agent installation. Using Horizon Help Desk Tool Horizon Helpdesk Utility | VMware Flings

Hi JMARTIN16 The Windows Group Policy setting Do not show the 'new application installed' notification needs to be enabled, to prevent (occasional) popups of the "How do you want to open this file?"/"Keep using this app" dialog: This policy setting resides in Computer Configuration | Policies | Administrative Templates | Windows Components | File Explorer: Then you can configure FTA in DEM to open '.docx' extension file type with MS word always: Mark the post as helpful/correct if it answers your query.

Hi orgilplus If you are talking about 'Cluster' option while creating the desktop pool below,you need to select the vCenter Server cluster for the desktop VMs. Under this cluster all the VDIs will be provisioned. If you don't have any cluster in vcenter, you need to first create one and add your hosts under that: Details of all the options while creating a desktop pool can be found here Worksheet for Creating an Instant-Clone Desktop Pool in Horizon Console Mark the post as helpful/answered if it helps you.

Did you verify if port 443 is being used by any other application? This issue occurs if Port 443 is in use by another application. Routing and Remote access is a common service that may be using Port 443. This can also happen if the certificate friendly name is VDM instead of vdm, or if the certificate is not marked as exportable. Run netstat –ano If port 443 is used by another application, identify the process name of the application and disable the service that corresponds to the process. If there is any other SQL monitoring service Or routing-remote access service running on server which requires port 443 or 80, disable that. If the issue still persist, stop vmware view web component service > rename installpath\Server\broker\webapps\admin folder to admin_old > Start the service > It will create a new admin folder in this location. Try to access the page now. If issue still persist create a locked.properties file once (VMware Knowledge Base ) and see if it helps. If issue still persist, check the debug log under %allusersprofile%\VMware\VDM\logs\debug_xxxxx.log.It will tell you the exception when the page is failing. Also check if there is any recent windows update has been pushed to connection server. If so, remove the most recent updates and try again. Mark the post as helpful/correct if it resolves the your issue.

Hi JavierBernal In case of linked clones, a vCenter Server instance can be associated with only one VMware Horizon View Composer service. Hence only one-to-one mapping is supported here (Configure View Composer Settings ). However in case of instant clones, there is no such limitation, you can point same vcenter server to other horizon environment as well as long as your desktop pools are unique (name/ID) in both environment.