MSTSC and PCoIP VMware View

Similar Questions

• Question of VSI/VMWare View 4.5 connection

  It is perhaps a silly question, but it is a question that I encounter.  I've set up a small test environment to try to test the capabilities of my server using LoginVSI and ESXi/VMware View 4.5.  I have a few VMs work and but when I went to start a test but I am running on an issue which prevents me from run LoginVSI.  The problem is that I seem to be only able to connect to a client in by pitcher no matter if I use the command line or from the client application to view.  It seems that I can make a pool by VM and try to do the test in this way with a user by the pitcher, but that seems to be a wrong way to use the pools.  Y at - it a specific setting I'm missing to allow multiple users to log on to the VMWare View Client by machine or is this an intentional design decision that cannot be changed?  Thank you.

  There is an unsupported command line that allows you to run more than one user per machine.   The command line variable is - standalone.   I've never used seen it mentioned in another post, http://communities.vmware.com/message/1655745#1655745.

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

  Twitter: http://twitter.com/mittim12

• VMware VIew 6 (PCOIP): Windows Client and web browser connects, Android and Ubuntu - don't

  Hello colleagues!

  VMware Horizon Client 3.4.0 build-2769709

  VMware View 6.1.1 construction-2769403

  VMware vSphere 6.0.0 2776511

  That's what's wrong: used SecurityServer and connecting to the server. External connection - via a router. When it is connected to a vmware PCOIP Protocol (Internet) outside of the view with a Windows client and a web browser, it works fine. But when connecting from Android or Linux (Ubuntu 14) load the desktop does not occur. Android immediately displays the message 'connection to server lost', Ubuntu delivers all messages - I'll be back on the screen to select a pool table.

  Which connection via MS RDP connection protocol is correctly to all customers.

  In the settings ConnectionServer in PCOIP Security Gateway set up the external address of the router.

  Redirect them router ports:

  -TCP 80,443,8443,4172,32111

  -UDP 4172,32111

  Any ideas?

  In security settings server in 'URL of PCOIP' was FQDN, but it must be the IP address.

• Test environment for VMware View 7 - PCoIP Protocol does not work properly

  We test VMware View 7 with as many Thin Clients and customers zero (Teradici)

  When we try to connect via RDP Protocol, it works fine. When we try to connect via the PCoIP Protocol, desktop display seems to blink (about 2 times per second) and display resolution is not acceptable. So, there is a problem with the Protocol (broker or Office VM)

  There are no firewall in the middle.

  Desktop virtual has a clean install.

  So... anyone have the same number? or similar?

  How much video Ram?

  You can increase the video Ram.

• VMware View Agent 5.2.0 PCoIP over WAN fails

  Recently, I did an upgrade on VMware View VMware view horizon 5.2 4.6 square.

  After the upgrade the 4.6.0 view agent in virtual machines of my parents to view agent 5.2.0 and rebuild the office pools, external PCoIP does not work. Can I open a session in the 5.2 Client view, see the list of office pools, select a pool, the desk at work close and try to open remotely. After 1 second, this error appears:

  Error: Overview of VMware View Client: The connection to the remote computer has ended.

  What does not work:

  • External/WAN via PCoIP for workstations with the view Agent 5.2.0

  What does not work:

  • Internal/LAN via PCoIP for workstations with the view Agent 5.2.0
  • Internal/LAN via RDP for workstations with the view Agent 5.2.0
  • External/WAN via RDP for workstations with the view Agent 5.2.0
  • External/WAN via PCoIP for workstations with the Agent View 5.1.3 or lower (tested up to 4.6.0 Agent view)

  I even tried to build a new pool of desktop Windows 7 in a new OU in the active without optimizations VDI directory or group policy. I tried with and without the firewall Windows is activated. In any case, this new office pool works externally via any Agent from view but the view Agent 5.2.0.

  Is it the 5.2.0 Agent view have the same firewall/port that the Agent View 5.1.3 requirements? What else can I test or try to get external PCoIP for desktop computers to work with the view Agent 5.2.0?

  Finally, we discovered the problem / solution. We on a security apparatus of Palo Alto Networks that blocked traffic PCoIP 5.2.0 but not PCoIP 5.1.3 traffic.

  According to a backline Vmware engineer:

  "A change was made to the ephemeral TLS connection that is used to establish trust and to negotiate parameters for subsequent UDP traffic network. This change allows the customer to use their own certificate for TLS server for this connection. For more details of what happens during the installation of PCoIP, and how this changed view 5.2, see KB 1038762. »

  It seems that Palo Alto Networks did not like this change. When we removed our Palo Alto of WAN device, PCoIP 5.2.0 connections could be created. We finally had create a rule to allow the category: private-ip-addresses and URL: pcoip - by default-sni. Once this change has been made, connections WAN PCoIP 5.2.0 started working.

• Automation of VMWare View with PCOIP 5.0

  Hello

  I am trying to automate the execution of applications in VMWare View Client (PCOIP). However, I'm stuck with sending the keys to applications. I tried in vain on the keyboard to screen, SendKeys, keyboard hook to this effect. I also read VIX API documentation but I don't think that it works for me because I don't have administrator rights. Please notify.

  Kind regards

  Amjad Ali

  I'm not sure I understand the question either, but I had some success using AutoIT (http://www.autoitscript.com/site/autoit/) for automation in the past. Using this, you can compile a script as an executable to run in the virtual machine.

  If you do not have rights admin on the virtual machine, you can still use the Run value in the registry for the current user to start an application when you connect. Have you tried to put the path to the executable file that you are trying to launch in the HKCU\Software\Microsoft\Windows\CurrentVersion\Run?

  You might be able to use both of these ideas and set the path to an AutoIT executable in the HKCU Run key to get the automation level you are looking for.

  Dave

• Two monitors configured using PCoIP does not cover both monitors for VMware View

  Occasionally, I've experienced the symptoms described in KB1027899, when usually the first time of connection for the day that I select multiscreen and the screen is divided in the Middle the 2 monitors using PCoIP. I end up disconnecting and reconnecting to the virtual machine a few times, which is a valid solution, but I'm still curious about why this is happening.

  I am running VMware View 5.0.0 build-481677, on a Wyse R90L with Windows XP Embedded, I use VMware View Client 5.0.0 build 481677 and VMWare View agent on a box of Windows 7 5.0.0 build 481677. We lack vCenter and ESXi 5.0.0 in all areas as well.

  According to the article, this happens because there is not enough video memory configured for the virtual computer. The problem I have is that if I force the pool offices use PCoIP and 128 MB of video memory, I can't RDP to the workstation as the Protocol is locked, I need to still be able to do. I tried manually increase the memory video, but view reconfigures to match the settings of the pool.

  Is there a way to increase the video memory without changing the required logon Protocol? Or is there a fix in a different way to this question?

  Thanks a lot guys.

  Joe

  Have you tried to change the configuration video pool to be 2 monitors with 2560 x # instead of the default resolution to see if that solves the problem?

  Datto

• VMware View 5 PCoIP get a black screen on wide AREA network

  Hello community,

  I got a VMware View 5 Infrastructure with a vCenter Server, a connectionserver of view and some clients such as VMs.

  Internally, everything works - connections PCoIP and RDP do their job very well.

  Know that we want to publish the vDesktops over the WAN. Users must connect to the virtual machines in their laptops or iPad (or iPhone) at home. So, we have configured our firewall to open the IP Wan (194.209.166.xy) to the internal IP (192.168.199.xy). A DNS entry for view.xy.com shows the IP WAN. If the WAN connection to infrastructure display RDP works - but PCoIP connections shows a black screen after 10 to 30 seconds after logon. We never see an interaction of oder break Windows. The screen is black after the logoninformations in the client view.

  We have configured the connectionserver display settings as described in some articles here... 7

  The external url HTTPS: https://view.xy.com

  checkbox activ: tunnel connection secure user desktop

  PCoIP external url: 194.209.166.xy:4172

  checkbox activ: use pcoip gateway secure for pcoip Desktop connections

  We have forgotten to do some settings or is it an another workaround to work with PCoIP over the WAN?

  Kind regards

  Freddie

  Cross video related to the above article. It describes exactly the configuration you are working. If you have any questions on this subject, let us know and someone on this forum will help you.

  Select this option.

• VMWare View 4.6 PCoIP tunneling problem. UDP is not get tunnel

  
  Hello

  I have the black screen "classic" - question.
  So, when I try to connect to a virtual desktop, I am well auhtenticated, I can select a pool of offices, but once the bureau is launching,
  I just get a black screen and afterawhile it times out.

  I read the manuals, the document http://communities.VMware.com/docs/doc-14974 , written by Mark benson; Watched the video; Checked and re-checked the 3 magic steps;
  Blog reading Sláger, Paul http://paulslager.com/?p=1300 and still I'm stuck. I read the (some the) logs from the login view, view Security Server, View Client and Agent of the view server.
  None of the newspapers I read gave me all significant errors that would have solved this for me. Admitted, 'full' newspapers - trace State, there's a lot that wasn't exactly clear to me.

  I have simplified our mitigation debugging environment to be as follows:

  See connection to the server,
  running on Windows Server 2008 R2 (Datacenter) 64-bit VMware View Server connection 4.6.0 - 366101,.
  Checkboxes for both "Tunnel secure HTTPS: connection to Tunnel secure usage on the desktop" and "PCoIP Secure Gateway: use PCoIP PCoIP Gateway Secure connections to desktop" have been checked.

  View secure server,
  running on Windows Server 2008 R2 (Datacenter) 64-bit VMware View Server Security 4.6.0 - 366101,.
  has been paired with the login server and the two aswell "HTTPS Secure Tunnel: external URL" as "PCoIP Secure Gateway: PCoIP external URL" has been set to a virtual IP address in the firewall external dmz with a dst - nat on the real IP address of the Security Server.

  The reviews are pointing to the virtual IP address of the Server Secure View.

  Since it is not a production environment, I installed a bunch of Wireshark to see traffic;
  I ran traffic snooping on the view connection server, see Security Server, View Client and the virtual desktop connected
  at the same time and have verified that traffic TCP PCoIP on get 4172 port of talked about between my security server host <>client - and the
  securityserver <>- virtual desktop just fine. TCP traffic seems to be in the tunnel. But what bothers me is the wireshark on the virtual office reveals that the virtual office is trying
  to talk subject port 4172 - UDP back directly to my reviews host IP traffic. Because this is not allowed by the firewall, the virtual office propably does not work...

  But all scenarios describe only the Security server could handle all pcoip-traffic with the agent of the view (as shown in the documentation of the Architecture in Figure 5-6), so that no direct connection between the Client of the view and the view Agent is necessary... I can't work. But it is possible, right?

  Any ideas what I could do wrong?

  Help really appreciated.

  It works in the way that you described in your original post. There is no obligation for the virtual office send UDP responses to the client. They will be sent on the Security Server, which will forward them to turn to the customer.

  Something must be configured incorrectly.

  Check very carefully the UDP traffic in your wireshark traces. The client, you should see 4172 TCP for the VIP of your SS. You should then see 4172-UDP to the same VIP. You should see the UDP of SS response to the customer data. The destination for this data answer UDP port must be the source port used for the UDP request. The source for the response data port must be 4172.

  Then check your wireshark SS track. You should see the same customer traffic and you should see a similar PCoIP conversation between the SS and the virtual office. From the virtual desktop, the SS looks like a customer. PCoIP UDP must be sent to the SS, when it is properly configured.

  Client - TCP 4172-> SS - TCP 4172-> Virtual Office

  Customer - UDP 4172-> SS - UDP 4172-> Virtual Office

  Customer<-UDP 4172--="" ss=""><-UDP 4172--="" virtual="" desktop="" (the="" 4172="" here="" is="" src="" port,="" the="" dst="" udp="" port="" will="" be="" the="" source="" port="" of="" the="" udp="" request="" packets="" above)="" 4172--="" virtual="" desktop="" (the="" 4172="" here="" is="" src="" port,="" the="" dst="" udp="" port="" will="" be="" the="" source="" port="" of="" the="" udp="" request="" packets="">

  If you have verified that you can connect to the same virtual desktop with PCoIP then this problem will not be something to do with the virtual office or agent of view etc.

  Check your display settings, network, firewall and NAT.

  Select this option.

• VMware View - RDP works, PCoIP mit error

  HI Leute

  ICH habe bei meiner VMware View Architektur das problem, dass ich beim Verbinden uber den View Client nur das Protokoll RDP use kann. DAS will work wunderbar. As soon as ich aber das PCoIP Protokoll auswahle, kommt also Fehlermeldung beim Verbinden:

  Dieser Office steht zurzeit nicht available. Try later Rubis, eine connection Sie mit diesem herzustellen office, oder wenden Sie sich an your Systemadministrator.

  ICH use VMware View 4.6, mit zugehorigem vCenter Server und connection to the server. Alles ist auf dem could Stand. Am is nicht mit einem Security Server. Lafut're too im trainee alles Moment.

  Die virtuellen Maschinen, die ich mich verbinden laufen auf mit Win 7 x 64

  Hat eine idea, wo yesterday someone das problem konnte liegen? Habe ich vergessen oder please konfiguriert something?

  ICH würde mich freuen, wenn einen Losungsansatz had someone.

  Grüße

  Bopa

  OK, so I ran it through a translator and got the below.

  People in the back, I have the problem with my VMware View architecture that I can use the minutes RDP with the connection by the Client to view only. Will work wonderfully. As soon as I select the PCoIP minutes however, the following error message is delivered with connection: this office is not available at the present time. Try again later connection with this desktop computer or contact your system administrator. I use VMware View 4.6 with partner vCenter server and connecting to the server. Everything is on the latest terms. I'm not however with a security server. It lafut so for now everything in-house. Virtual machines, on which I connect run me with Win 7 x 64 does anyone have an idea, the problem could lie where here? A I forgot something or configured incorrectly? I would be happy, if someone had a solution. Greetings

  So, it sounds like RDP works but you are having problems with PCOIP and everything is internal.    Have you checked that PCOIP is not blocked by any firewall?  It uses the port 4172 so make sure that you unlock that.    Also is this a problem with this particular machine or all of your machines?

• Ports and Destination for VMware View Client

  Hi all

  I'm looking for a quick bit of help if possible please...

  Environment: VMware View 4.5

  Question / Info needed:

  Two companies having a bond of trust between data transfer etc. and resources share. We need access to a site through their firewall in the bond of trust to connect to the VMware View VDI Office.  Customers using VMware View Client.

  The question is, if we get the site to enable port 443 to our broker connection I assume this will not be enough?  It must be possible to:

  443 to connection broker

  32111 (redirect USB) to?

  9427 (multimedia redirection) to?

  4172 (PCoIP) to?

  3389 (RDP if used) to?

  This may all sound a bit novicy but I need to be 100% before you go test.

  Thanks in advance.

  So using the brokers of the connection in direct mode without any security server.   I think that it would look like this.

  443 to connection broker

  32111 VDI Desktop

  9427 multimedia redirection) to?

  4172 VDI Desktop

  3389 VDI Desktop

• NAT and VMware View

  I am

  try again using VMware View, where a person uses a VPN to

  connect to my view of the Park, but my connection to the server is running NAT, and

  the client tries to connect in my Park he cannot get the virtual

  machine. Are there restrictions? Any tips?

  If you have found this information useful, please consider awarding points to 'Correct' or 'Useful'*.

  Exactly THAT PCOIP do not work on the Security server.  If your using VPN and connect to a broker internal conection it should work good as new NAT could shake things.    Should be a simple test however.

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

  Twitter: http://twitter.com/mittim12

• VMware View 4 - PCoIP - scanning is very slow

  When you scan from a USB scanner from a heavy client without VDI, it takes 7 seconds. When you use VMware View with PCoIP 4.0, it takes 52 seconds.

  Any suggestions?

  Rgds

  M

  I sent an email to teradici support and they checked the speed was closer to the USB 1.1 instead of 2.0.   If you PM me your email I'll send you the conversation

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

• VMware View 4 - newspapers PCoIP

  Hello

  Where can I find PCoIP logs (logs from VMware View Client 4.0) in thin or thick client?

  M

  Please watch it on thick Client where the Agent is installed in C:\windows\temp.

  Or also in C:\Document and Setting\All Users\ApplicationData\VMware\VDM\logs.

  MCP, VCP

• Disable the protocols and encryption algorithms in VMware View connection server and security

  Hello

  In my recent deployment, I had a customer request to disable some protocols and encryption at the Server VMware View connection and security. I read some articles and found that this has been achieved by editing the locked.properties file. But when we have edited and replaced the file, users could not connect to the virtual desktop, so came back to us backwards and desktop computers worked fine.

  I found a few articles that we don't need to edit the locked.properties file in VMware view Horizon 6. If someone has done this please guide me through. Here are the details of the protocols and encryption algorithms that should be disabled

  Diffie-Hellman key

  Enable SSL v2/V3 and TLS 1.1 and 1.2

  Disable the RC4 encryption algorithm

  Select the secret of transfer (if possible)

  
  

  VMware view 6 is the connection to the server and security server.
  

  
  

  Thank you.
  

  Hello

  I implemented the following steps (from the manual):

  1. update the JCE policy files to take in charge the high-strength Cipher Suites

  You can add some cipher suites of high resistance for greater assurance, but first you must update the local_policy.jar and US_export_policy.jar files to each server instance and the security strategy for JRE 7 see connection to the server. You update these policy files by downloading the files to extend JCE (Java Cryptography) unlimited strength political jurisdiction from the Oracle Java SE download site 7.

  If you include some high-strength cipher suites in the list and you do not replace the policy files, you cannot restart the VMware view Horizon connection to the Server service.

  Policy files are located in the directory C:\Program View\Server\jre\lib\security from VMware.

  For more information on the download of the JCE unlimited strength jurisdiction policy 7 files, see the Oracle Java SE download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html.

  After you update the policy files, you need to create backups of the files. If you upgrade the instance of the view connection server or security server, any changes you have made to these files can be replaced, and you may need to restore the backup files.

  2. the changes that policies of global acceptance with ADSI Edit

  • Start the ADSI utility on your computer see connection to the server.
  • In the console tree, select Connect to
  • In the selection or type a unique name text box or a naming context, type the unique name
    DC, DC = vdi is vmware, DC = int.
  • In the type or select a text field or the server box, select or type localhost: 389 or the name of a fully qualified domain (FQDN) of the server computer to connect to port 389 followed view.

  For example: localhost: 389 or mycomputer.mydomain.com:389

  • Expand the tree of the ADSI Editor, OU = properties, select OU = Global, then select OU = common in the right pane.
  • On the object CN = common, Global = UO, UO = properties, select each attribute that you want to change and enter the new list of security protocols or cipher suites.
    I used the following settings:

  EAP-ServerSSLCipherSuites: \LIST:TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256

  EAP-ServerSSLSecureProtocols_ \LIST:TLSv1.1,TLSv1.2

  It is not the highest possible, but they work with all the features of our customers.

  • Restart the service of VMware view Horizon connection server (server connection and security).

  This is not Activate secret transfer (if possible) , but other points are covered.

  If anyone can give a tip to activate the transfer secret, I would be grateful.