Hello,

We have been running Horizon View 6 with vGPU enable (K1 and K2 cards) to support our CAD/Engineering team and we continue to get complaints that the 3D/Graphic performance isn't up to par.

We have tried various GPO settings to see if we can get the performance out of these VMs utilizing the PCoIP protocol..  We have plenty of resources for the VMs to access, however the users who are connecting are on a 6MB MPLS network. VMs are configured with K160 and K260 profiles.

In efforts to see if I could improve performance, I setup View 7 with the Blast Extreme protocol to see that would help vs. PCoIP.  A couple of the users informed it was about the same for graphic performance, but they noticed an improvement in file open times (not sure about that).

I keep coming across YouTube videos of 4K videos being played over Blast Extreme but to me that is not a big deal.  My engineers need to navigate, rotate, walkthrough various 3D models.  Are there "optimal" GPO setting for Blast Extreme Protocol I need to be adjusting based on the bandwidth available to the users?  The site where the VMs are hosted at have a 100MB MPLS connection.  I am wondering too if their is something inside the NVIDIA Control Panel for the driver that needs some tweeking as well.

Also, I was under the impress that the Blast Extreme protocol went over the 443 port and not 8443.  Is this true?

Greatly appreciate any direction, suggestion and support.

Thank You

We have an agent unreachable issue but it is only affecting one connection server of the pair that we run. Some of our View desktops go agent unreachable following a restart but only on one of the connection servers. On the other server they are fully available and work OK. I've checked for connectivity between the desktop and the 'bad' connection server and that seems fine even when the unreachable status is shown.

Restarting the View Agent Service on the desktop seems to restore the agent connectivity but obviously this is causing some issues.

Has anyone encountered / solved a similar issue?

Hello Experts,

Recently, I installed Horizon View 7 for a client and on their parent images uninstalled the old version of the view agent and installed the latest 7.0.1.  So an odd thing is occurring, out of 90 users, 30 of these users are showing the following warning in the View Admin event logs after 15 minutes of logging on and happens every day to the same users.

The Pending session on machine %Machine name% for user %username% has expired.

Also, on the connection server, the logs show this message:  "Client does not support idle session handling.  Desktop SSO times out in: Never. Application SSO Times out in: Never.”

I originally thought it was the SSO timer since that was set to 15 minutes, so I changed it to NEVER and the warning still shows up for these same 30 users.  The users experiencing the issue are using Teradici Zero Clients firmware version 4.8.0. 

Also, this is happening in different pools so it is not pool specific.  Has anyone experienced this with the new Horizon View 7.0.1?  Could this possibly be a bug since no one is experiencing login issues?

Thanks

Hi,

When I install the VMWare Horizonclient using the following command, it doesn't add the server.

The user has to add it through "New Server" option. Is there a way to fix this?.

VMware-Horizon-Client-4.3.0-4710077.exe /s /v"/qn ADDLOCAL=Core,TSSO LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1 DESKTOP_SHORTCUT=1 STARTMENU_SHORTCUT=1 VDM_SERVER=horizon-dev.MY.com /l*v "%TEMP%\log.txt""

Thanks

Horizon 7.0.2.  Windows Server 2012 R2 RDS farm configured for remote applications.  Clients and farms configured with PCoIP.  Applications virtualized with App Volumes 2.12.  UEM 9.01.

With 4.x clients, we sometimes experience issue where View Client goes full-screen with ribbon bar along top when access an app.  Seems to occur on first launch of application (ie Chrome or Word).  Once application is closed, then opened again, the app is presented in it's own window as desired.

We do not see same issue with 3.5.x View Client.

I've seen this issue on both Windows 7/10 and MacOS clients.

Hello!, Haven't found a thread about this, so, I'm launching it , A customer is migrating from Citrix VDI to Horizon and wants to use the same VMs (were created on vSphere) but now with the View agent. As far as I know, tue best practice is to start with a fresh OS installation, but he needs to migrate about 400 individual desktops to Horizon with View, Is this possible and/or supported?

Cheers!

We are upgrading Horizon 7.0.0 to 7.0.3 - Is there an Access Point Upgrade?

It's an appliance we deployed, I'm guessing the appliance is the same in 7.0.0 as in 7.0.3

Just wondering what steps are needed concerning the "upgrade" of  Access Points, or if none are needed.

Dear all,

one of my staff said she could not connect her desktop vm22 and the view client said "the view agent reports that this desktop source is unable to accept connections". my view administrator displays that “the pending session on machine xx for user xxx has been expired” . but i then assigned another user to the same desktop, everything looks fine.

background:

1. I am using view 6.0.   

2. This user used to assigned another desktop vm06. it took a long long time (more than 30 minutes) to login (agent set not delete local persona) , This Morning when she tried to connect(already logged in before, here just reconnect),  she got "there is no available gateway for this display protocol". So i assigned her to another desktop vm22

Is there something wrong with this user account or something else. Need your help!!! Thanks in advance!

I am unable to click on the HTML Access Client and get to my resources on the connection server through Chrome i get a "Failed to connect to Connection Server" But again this only happens in Chrome. Any suggestions?

Thanks all!

My server is Windows Server 2012R2, after finished the Horizon View 7 server install, couldn't open the Horizon view admin page. I check the netstat, and the port 443 didn't opened.

Check the vdm log in the /programdata/vmware/vmd/logs, a lot of warning in the log files.

I tried the Windows Server 2008R2, tried the Horizon View 6.2, and the warning is same.

The warning information is below, and I upload the log file.

2017-02-20T07:54:09.518+08:00 INFO  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [CertificateUtils] Adding bouncy castle security provider

2017-02-20T07:54:09.674+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.768+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.815+08:00 WARN  (0C8C-0C60) <SwiftMQ-ConnectorPool-2> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.877+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.924+08:00 WARN  (0C8C-0304) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:13.565+08:00 INFO  (0DB8-0DB0) <localhost-startStop-1> [BrokerMessageSecurity] Changing message security mode to: ENHANCED

2017-02-20T07:54:13.565+08:00 INFO  (0DB8-0DB0) <localhost-startStop-1> [BrokerMessageSecurity] Generating new broker message security keys

2017-02-20T07:54:13.565+08:00 INFO  (0DB8-0DB0) <localhost-startStop-1> [BrokerMessageSecurity] Switching message security ENHANCED by default

2017-02-20T07:54:14.221+08:00 INFO  (0DB8-0CEC) <SwiftMQ-ConnectorPool-1> [CertificateUtils] Adding bouncy castle security provider

2017-02-20T07:54:14.284+08:00 WARN  (0DB8-0CEC) <SwiftMQ-ConnectorPool-1> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:14.924+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:14.971+08:00 WARN  (0C8C-04F4) <SwiftMQ-ConnectorPool-5> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.018+08:00 WARN  (0C8C-08D4) <SwiftMQ-ConnectorPool-6> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.065+08:00 WARN  (0C8C-0304) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.112+08:00 WARN  (0C8C-0358) <SwiftMQ-ConnectorPool-4> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.315+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:15.596+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:16.596+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:16.800+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:17.800+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:18.034+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:19.034+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:19.393+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

Hey all,
I'm having trouble getting external access for a desktop pool running View Agent 6.0.2 after upgrading the infrastructure to 6.2.2.

Internally works fine (after the usual tweaks), but nothing good on the other side of the PCoIP Secure Gateway.

Event logged in the View Administrator is: "No Co-management availability for protocol PCoIP"

Hoping someone out there has had to do this before! :-)

Can anyone locate this new version on the VMware downloads page or am I blind?

The release notes are out but the download page does not seem to be showing it

Hello,

When first asked about this I thought this would be a simple thing but I seem to be finding it incredibly difficult. Basically on the logoff button I want to see an disconnect option, not Lock (if lock remains that's fine but ideally that can go too) but I just can't seem to find any settings for it.This is what I see on an uncontrolled start menu, yes I can remove restart and turn the Shutdown into a Logoff but crucially there is no disconnect which is what I need.

If I RDP onto the same Win 7 VM I get this, which is exactly what I want:

So it seems that it is a PCOIP issue that it is trying to be too clever and removing stuff that I am quite capable of clearing up using Group Policy. Is this a common thing? I can't find any way to control it using the ADM templates supplied in the Horizon 6.2 download package. The above screen shots are me logged on as an admin with no user policies applying.

BTW, I don't want any suggestions about using the Horizon client to disconnect or anything like that, I just want it to work like it does in RDP.

Many Thanks!

Hi,

I'm testing horizon view 7.

From a win7 parent I've created a linked clone pool, onnected to it using a win 8 client via pcoip.

It works but adding a printer to the client, it's not redirected into the agent.

In the agent I've tried to do:

tpautoconnect -d

tpautoconnect -v

Here I get:

Try ThinPrin Client on VM7_LINK2:4000.

Connected

Client Type --> [0x04]: Unknown client type.

Any kind of help will be appreciated.

Hello,

3 weeks ago i upraded my Horizon View infrastructure from 7.0.2 to 7.0.3

We have several desktop pool with Windows 7 and now an other one for testing Windows 10 (1607)

We have a problem with the Windows 10 Start menu (it doesn't appears when we click on it) not always but often.

This problem seems to be known with Windows 10 without considering virtualization

Our goldimage was optimized with VMware OSOT, and other standard recommandations like we made it with Windows 7.

We use linked clone in non-persistent mode with Vmware Persona. (share cifs on NAS,)
Since 2 years, everything works fine with Windows 7, all dedicated GPOs for Vmware View 7.0.3 are updated for the dedicated OU for W10 pool desktop.

In the last ticket (closed now), Support said us this problem will be fixed in the next release (7.0.3) but the problem is still there.

I just recreate a SR to VMware support,

Any idea ?

Your help, feedback or experience would be appreciated

Best regards

Daniel

(Switzerland)

Hi,

We are currently trying to supply linked clone desktops for our Developers.

They have come to me with a problem that they cannot leave their VDI to compile their solution overnight.

It seems that when they reconnect after some time while visual studio is still open it just crashes when they get in their VDI.

Anybody had this issue as well ?

FYI we are talking about Visual Studio 2013 on Win10 machines.

Hello all.  So excellent Friday.  Our VMware administrator was has either quit or was fired so now is on me.

It looks like he used his personal user account somewhere in vSphere or Horizon because I can not recompose any stations in Horizon 6.  When I try I get the server error "Internal View Composer error. Contact your administrator"

Researching that error lead me to the fact that the server is not able to find the AD container that the VM's are being placed in.  When I go to the Guest Customization tab when editing a pool I see that domain is listed using the former admins user account which is now disabled.

What I need to know is where is it getting this user account from and where can I change it?

Any help will be greatly greatly appreciated.  I have a support call in to VMware but they said it may take up to eight hours so hoping the community can help me faster.

Hi

According to latest release notes of 5.3 , if you use vDGA linked-clones desktops and you do a refresh / recompose the VM's should keep there vDGA settings

but this doesn't apply to the recompose operation , refresh however does work and keeps the vDGA GPU settings ??

/P

Got some good tip from a internal vmware pre-sale and the following solution did solve the problem , so basically remove the following lines on the master .vmx / parent and take new snapshot , then when you recompose it will keep the original vDGA GPU settings .. ;) "After you install the driver and detach the GPU device from the master template manually remove the passthru device entry and then take the snapshot For example the entries to be removed are pciPassthru0.id = "133:00.0" pciPassthru0.deviceId = "0x11bf" pciPassthru0.vendorId = "0x10de" pciPassthru0.systemId = "52c7a340-e91a-596d-e293-6c416aa07cc2" pciPassthru0.pciSlotNumber = "-1"    Message was edited by: Patrik

Is there a View (6.2.3) best practice that indicates that Windows 7 VDI desktops should be logged off by the VIew media pool settings after 24 hours if left in a disconnected state or else there may be corruption within the ADAM database? We are running our VDI environment on vCenter 6. Are there any best practices documented for this as well?

Thanks in advance...

Scott

Guys i know this horse has been beat to death before on other forums but i can't seem to find anyone that has posted with a problem like this.  I am running a Horizon 6.2.1 environment with windows 7x64 workstations on a network that is separated from the internet by a proxy.   I have a security server out in front of the proxy that has the appropriate firewall exceptions allowed (per the VMWare ports and protocols white paper) and everything seems to be hunky dory.  Here is where it takes a downward turn however.  I have about 80 users in a building in VA (i am located in AL for reference) that seem to randomly give errors in the connection server log that the pending session has expired.  The end users experiences the same effect as if the firewall ports were not opened properly, they get presented with the pool to choose from when they click the pool the windows launches black then closes and they get a generic display protocol error.  I can go into the connection server and see where they tried to connect to machine X, i can then manually restart that machine from vcenter and they are able to connect to it perfectly fine with no problems.  This is happening multiple times a day and it doesn't seem to have any rhyme or reason to it.  Once a user is connected, as long as the session doesn't time out from inactivity, the connection is stable and they can work all day without problems.  I have the connection server set to automatically log off after 60 minutes of disconnect and have asked the users to log off vs just close the window.  There doesn't seem to be any correlation, that i can see, between how the user terminates the session and them not being able to log back in later.  I also have tried having the systems recompose after log off but that introduces a slew of other problems and didn't seem to correct this one.

I have been trying to work this out for months now and this project is only growing and the problem is only getting worse.  I will take any help or direction that i can get at this point!  I have attached the error the end user gets