I have done this and had no issues, as the previous posted mentioned 5.5U1 is required.
One thing to check is that the console needs to be on a separate GPU then the one used for vSGA.
I have done this and had no issues, as the previous posted mentioned 5.5U1 is required.
One thing to check is that the console needs to be on a separate GPU then the one used for vSGA.
I'm having this exact issue, and can't find a solution yet.
On all previous versions, the last previously accessed pool would be highlighted, and the user could just hit "enter". Now nothing is highlighted, and "Connect" is greyed out.
Uninstalled and re-installing the client didn't help.
Any ideas?
Yes recently upgraded to ESX 5.5 IU1 so that has been done. I have rebooted the host many times and the service won't stay started. The conole needs to be a separate GPU you mean in the bios setting the primary and secondary? I would think that I should see something in the xorg log to help figure this out but there isn't anything in that log.
Just upgraded View from 5.3 to 6.0, and have problems logging on to security gateway with Windows and Mac clients. HTML5/Blast via browser works just fine -> Logs in, and show me the available desktops, and of course lets me connect to them.
Logging on directly to connection manager works fine with client in LAN. Logging into security gateway via LAN gives same error.
Event log in connection manager confirms me logging on, but no trace of connection dropping.
Really don't get this, since the session fails/disconnects right after autentication (do not complete the logon, stuck in login dialogue).
Tested with 2.3 and 3.0 clients.
Have generated a support bundle on the security gateway and looked at most of the logs, and don't see any obvious stuff there.
IPSec tunnel between sec.gateway and connection manager is okay.
Anyone else seen this and have a couple of hints before I "go deep"? :-)
Hva rebooted all servers and desktops, as well as clients, and don't understand the "reconnect" message, since I do a "fresh" connection.
br
Oivind
This might be an easy task and I might have missing some steps here because I know it works before.
But now, it seems like it's broken and couldn't figure it out what cause it.
I wonder if I need to upgrade to 5.3.2 from 5.3.1 first?
This is the issue that I'm having after doing several tests with no success.
On the Golden/Master Image PC, I have set the Visual Effects to Custom and checked the "Use Visual Styles on windows and buttons".
BUT
After recompose process, when a user logged in to their desktop, most of them will get "Let Windows choose what's best for my computer" button checked.
What did I do wrong?
I'm using Persona Management and Floating Desktop (Delete after log off/shutdown).
I haven't run the Persona Management scripts again for a long time.
I wonder if I have to re-run it again? Is the sysprep broken probably?
Any advise would be very appreciated.
Thank you guys.
I just downloaded and installed this module AMD FirePro™ Unified Driver
Sooo question...is this card only supported in an R720? The driver page would lead me to believe that. Might want to call AMD to verify, especially since the below link (updated TODAY) says "For vSGA compatibility, please refer to the partner support page to ensure your server is compatible with your vSGA certified graphics card."
http://www.vmware.com/resources/compatibility/pdf/vi_vsga_guide.pdf
BTW the module is actually called fglrx, not pciPassthru. I can start the xorg service on my 5.5 U1 box, but the service fails to keep running because I don't have the card, which is expected.
To me it sounds in the PCoip Gateway Configuration http://kb.vmware.com/kb/1036208
You could use the Client_adm Template and change the behavior through Group Policies which should be fairly simple
Hello Guys
i want to try the new 6.0 Feature with RemoteApps. I added my Terminalserver 2008 R2 into the View Infrastructure. I have updatet the Agent to 6.0. I have added RemoteApps. But i cant connect to the RDP Server Desktop or one of the Apps. I get the Error RDP Protocoll is missing. The Event Log shows only a cant connect to Pool with RDP. I cant see any error on the Terminalserver. I see that the Server is up running in the view console.
We uses a Secure Gateway to connect. We have opened the needed ports. RDP Works i mean with 5.2... but not now.
Have someone an idea where i can log deeper in the logs?
thanks
Bye
Marco
Hello Marco,
I wanted to check that you installed Remote Desktop Service Roles on the 2008 R2 Box and after that you installed View agent on that please verify page 83 https://pubs.vmware.com/horizon-view-60/topic/com.vmware.ICbase/PDF/horizon-view-60-setting-up-desktops.pdf
Hi
yes we do it in this way. The RDP Server is our "old" Terminalserver we uses since 3 years we have only installed the vmware agent on it.
I resolved my Problem.
RemoteApp only works with PCoiP.
And from my Mac i cant connect to a normal RDP Server with RDP.
Solved
Yeah, that's what I tought too, but since there's no config changes related to this (upgrade), and connection drops before I even get to choose what desktop I want to connect to, I'm not so sure that this is a PCoIP isolated problem.
Does the client communicate over PCoIP when it authenticates and requests the list of available desktops? Isn't that done over SSL? I tought the PCoIP tunnel was initiated when the client connected to a spesific desktop.
--
And just testet with an iPad -> Works just fine. Can logon, and connect to desktops successfully.
So, again, not certain that this is a PCoIP problem.
In the client log in Windows, I get this:
BrokerItem::Connect : [User] Enter ConnectToServer:view.XXXXX.no.
2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::SSLSettings : SSL 2.0: Disabled
2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : SSL 3.0: Enabled
2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : TLS 1.0: Enabled
2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : TLS 1.1: Enabled
2014-07-02 10:19:08.084+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : TLS 1.2: Disabled
2014-07-02 10:19:08.084+01:00 DEBUG (1628) [WinCDK] SSLSettings::GetCipherControlString : SSL cipher control string from registry: AES:!aNULL:!eNULL:!EXPORT:@STRENGTH
2014-07-02 10:19:08.084+01:00 DEBUG (1628) [WinCDK] SSLSettings::GetSSLSettings : Cipher String from client: AES:!aNULL:!eNULL:!EXPORT:@STRENGTH
2014-07-02 10:19:08.175+01:00 INFO (1628) [WinCDK] BrokerItem::Connect : [User] Exit ConnectToServer:view.XXXXXX.no.
2014-07-02 10:19:08.175+01:00 INFO (1628) [libcdk] TUNNEL INTERRUPTED: Could not establish tunnel connection
--
Running the 2.3 client on another machines throws this message:
Error reading from tunnel HTTP Socket: An established connection was aborted by software in your host machine.
Message was edited by: Oivind Ekeberg
Hi
Hope someone can help
Does anyone know if you can use this plug in to allow users to connect via a external connection??
Hey,
leaving redundancy aside, is it possible to have a single Connection Server that enables internal AND external users to access the virtual resources?
For external access I have a Security Server paired with my Connection Server. This works perfectly if I enable the PCoIP Secure Gateway option on my Connection Server and enter the public IP address of the Security Server.
But with this configuration internal users are not able to connect (enumeration of resources works, but connection fails).
If I disable the PCoIP Secure Gateway option, internal users can access, but not external users via the Security Server.
Any input is appreciated.
Thanks a lot!
Well, figured out that I might as well could do a reinstall of the security server.
And, that's when I found the issue!
During reinstall wizard, I noticed something that dodged the radar yesterday, and that was the portnumber on External URL. During upgrade yesterday, this got changed to 8443 in some way (I know I didn't type it in), and after correcting that to 443, everything now works just fine.
Problem solved! :-)
Yes that should work fine, have a look at the GPO:s on howto set the external URL and External PCoIP IP.
// Linjo
It should be doable. So when connecting internally it seems that ad authentication and pool enumeration work but then you fail on the connecting to the desktop. Does it go through if you switch the protocol to RDP?
The clients have to be able to utilize the IP specified in the PCOIP External URL. Why not use the external assigned IP on the security server side but on the paired (internal) connection broker use the internal IP as the PCOIP external URL?