PCoIP on HP t5740?

Similar Questions

• "Dual monitor Expand" doesn't work is not for t5740 with WES 2009.

  We do the following procedure to configure all our years TC bi-ecrans.

  1. flash the tC, customize it to our needs.

  2 join to the domain

  3. log in with Admin Creds, change default display settings: display properties-> settings tab-> "extend my desktop windows on the second monitor"-> apply

  4 validation EWF, logoff

  5. now, Login as any domain user for the workstation mode extended.
  works great for t5630 (xpe sp3) & t5630w (WES 2009) & t5740 XPF 2002
  

  BUT it fails with t5740 with WES 2009
  

  the above parameters are only to the Admin account, any other user domain/local get one active monitor.
  

  can write us any script/group policy settings to do
  

  Could someone help me solve this problem.
  

  Thanks in advance
  

  found an easy way without multi-display software

  Requirements: HPDM AGENT installed on TC

  c:\windows\xpeagent\hpdmAgent.exe

  c:\windows\xpeagent\hpdmmc.exe the set display = rate of 1280 * 1024 = 60 depth = 32 sm = primary r = pm

  put the following two lines of code in a file bat in logon scripts

  source: found this in the task log hpdm "display" - file and registry settings

• HP DM 4.5 SP2 cannot capture an image of WES2009 of T5740

  We use Altiris and have problems with PXE. To deploy images that we intend to migrate to HP Device Manager 4.5 SP2. Installed on a Windows 2008 R2 and FileZilla Server. EVERYHING works fine, but when I capture an image from a thin client WES2009 T5740 custom image will not capture. The thin client EBOOT 2 times and installs some files on the workstation. After the installation of the files, the thin client is reset each time in Windows. You see a HP backupground. A windows Device Manager is popping up and restarts the workstation. No idea why it does not work. If I capture an image Windows XPe to a T5730 capture with FTP works fine. With T5740 WES2009 won't yet make the FTP connection. I tried an old image of WES2009 and the last image of WES2009. It does not work.

  Today I installed the Device Manager in the production environment. The mentioned in the above 2 posts is a facility in the environment of the OTA. In production it works. Image captured from the Device Manager is saved with the option of shared folders.

• Client light HP T5740 + Broadcom Crystal HD BCM970015

  Hello

  I have the HP T5740 Thin Client, and I want to install Broadcom Crystal HD BCM970015 a half height mini PCIe card.

  question is do I have PCI Expansion Module AZ551AA Express4x or it can be installed without it?

  can not find documentation on the motherboard, which slots are available, where to install the Broadcom Crystal HD etc...

  Thank you

  Just open it and see.  There is a Mini PCIe location to downtown, which was originally scheduled for a WiFi inside card.  With the t5740 worm 1.04 BIOS update, the Mini PCIe slot was authorized to accept cards like the Broadcom Crystal HD.  The older BCM970012 is a card full height and does not.  The BCM970015 is a half-height card normally but Amazon sells a Variant that is full height.  Don't buy that.  You want the card half height card support with full height.  Simply remove the stand so it will be good in the t5740.

  Here is an example from BCM970015:

  http://www.Amazon.com/Broadcom-BCM70015-Crystal-hardware-DecoderHardware/DP/B008D96Z8Q/ref=sr_1_1?ie=UTF8&QID=1367596358&SR=8-1&keywords=BCM970015

• T410 AiO customer CAPS, NUM, and scroll keyboard stop does not work with PCoIP view desktop computers

  We have problems with our t410 AiO customers, where the CAPS, NUM and scroll stop lights on the keyboard do not work with view PCoIP desktop computers.

  I found the below information and a work around:
  If you use the Protocol PCoIP to display on a client system Ubuntu 10.04, the CAPS Lock, NUM Lock, and Scroll Lock lights on your keyboard do not work with desktop view. Although the lights do not work, the keys themselves work.
  Solution: Set the following configuration in a configuration file, such as/etc/vmware/config:
  mks.keyboard.useXkbSetNamedIndicator = 'TRUE '.

  The problem is this difficulty is already in place via the latest version of the HP, Z6A440, software that is installed within our Organization.

  What I discovered, is that the model that we initially bought for the test doesn't have this problem.  However, the models that we ordered since that time, DO have the problem and the solution above does not work as expected.

  The model originally ordered for test is still a customer of IOA t410... but there are 4 "under models' for customers of IOA t410... that we have to test is a H2W20AA, while those we receive and distribution are the H2W21AA model.

  No idea why, when connected to the desktop from view, that models of H2W21AA have this problem?

  H2W20AA is with Teradici PCoIP optimized, which can support PCoIP better, but H2W21AA is not with Teradici. That's the difference.

  However, the issue that you are experiencing does not matter in fact, we have not heard of this problem before. I would suggest that you do the following to see if there is no change:

  1. Go to download the latest VMware View 2.3.4 for t410, follow the instructions to install.
  2. If suggestion 1 does not work for you, try to connect to another VM group or set up a new machine virtual clean
  3. Call HP service center to save your problem for further investigation if the suggestion above did not work

• T5740 new image question

  I have T5740 several clients with the version of the Windows Standard light 2009 5.1.810.WES0 image. I downloaded the new image V5.1.989 want to install using a USB key. The process hangs without giving me a message. The units have 2 GB Flash and 2 GB of RAM. This image is too recent for the t5740? If Yes, what is the most recent version of the image, I can use?

  Issued or resolved. I contacted HP and this is the resolution.

  1. switch to update the BIOS at the bottom of the link given.

  http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12454&prodSeriesId=3996155&prodNameId=4071329&swEnvOID=4044&swLang=13&mode=2&taskId=135&swItem=vc-93007-1

  2. after the Bios Update, please try to image 5.1.989 Rev unit and check for the issue and please make sure that you use a 4 GB FlashDrive on the unit.

• PCoiP: HPDM 4.6 How to deploy background logo company on Thin Clients

  Can someone advise please how to deploy our customers business desktop light of 4.6 HPDM background. I try to use the file and rgistry and deploy files and I know the location to deploy files but for the last 4 hours, he sat on the shipment and wallpaper is only 84 k. So far, it's faster to send our image to the device and rebuild them just who is tim consuming and not a means of practicle to deploy our context of society to more than 400 customers. All is well with our network that can send all the other jobs and thin images.

  They are T520, I was under the impression that PCoiP but apparently they have zero smart.

  The current logo is on/writable/misc/desktop devices

  I managed to bumble my way through it the last minutes by using deployment files using the model inasmuch and register, click Choose downloaded and transferred the image, added the path above and then applied to my test client and worked immediately.

  I suspect the previous path, I was trying to do, I just looked at the image and, but never clicked to be downloaded, so why the work was sitting on the consignment because it does not know what he sent.

• client light t5740 - agent HPDM

  Hello

  I was wondering if someone could remember where HPDM agent (for a thin client of t5740), specifically 4.3

  device recently returned repaired with HPDM version 4.5 HP, however this doesn't seem to be compatible with the version of HPDM (4.3) on the server.

  search for the error code: 14000052 gave me this idea, but others thoughts most welcome.

  Thank you.

  turns out that the bios of the thin client is not able to boot from a USB pendrive of 64 GB!

  a 2 GB key has worked — first time, no problem!

  moral of the story is - keep these keys GB 1 & 2... they can become useful at some point.

  see you soon

• Teradici PCoIP Hardware Accelerator support on C240-M3

  Teradici PCoIP Hardware Accelerator cards are supported on a C240-M3?

  Walter,

  Yes the Teradici Apex 2800 is supported with the M3 C240 and C220 M3.  See the PCoIP adapter interoperability Matrix Table in the UCS HCL

  ( http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html) for your version of MMIC and a specific version of ESXi where you need help.

  Steve McQuerry

  UCS - Technical Marketing

• Thin client HP t5740 + TravelScan 662

  Product name: HP t5740 Thin Client

  Operating System: WIndows Embedded Standard 32-bit

  Problem: try to find a Windows 7 driver for TravelScan 662.  Tried searching on the web and have the machine to search for updates of Windows without success.  Someone came across this problem and solved it?

  Scratch that; I have it.

  Found the driver here down.  The driver is for WindowsSE/ME/2000/XP/Vista 32-bit, but it works perfectly for Win7, too

• 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.

• Skyline view 6, failed to connect to deployed Linked clone pool with PCOIP?

  I can not connect to my pool bound using pcoip by the client or the web browser, however I can connect by customer and select rdp.

  Liked my statue of gold to clone a set-aside;

  • View agent
  • Member of domain with the static ip DNS address
  • VMware OS optimization tool
  • ipconfig/release
  • then snapshot and is used for specialized bound basin

  Made by basic deployment and use of vCenter customization specification (sysprep);

  Custom network setting, use DHCP and static DNS ip

  domain credentials: lots of domain and user name: administrator@fulldomainname

  Additional information is needed to help. Have you installed the tools or the agent first? Believe that desktop computers available in the administrator of the display? Do you think all the right ports open on the desktop? Haven't you view files customer newspapers and agent you can edit? What is the error message get you from the customer?

• PCoIP Raccordementvia security server view Horizon 6.2.1

  Given the problem with connecting to the office via a security server view VDI.  She starts to connect, is a black screen for about 10 seconds, then disconnects.

  This is my setup

  All ports are two-way.

  Public IP address is NAT for the Security server in the DMZ.  I have TCP 80, TCP 443, TCP & UDP 4172 open ports on the Security server.  (I tested by telnet to the public IP address on 80, 443, & 4172.  It works)

  From the Security server in the DMZ, I ports TCP 4001, 8009, 4172, 3389 UDP 4172 open from the Security server to my login server in-house.

  From the Security server in the DMZ I have ports TCP 3389, TCP and UDP 4172 open for VDI desktops.

  I am able to connect to computers correctly using the server for internal connection on PCoIP.  It is only on the Security Server I'm getting the black screen problem.

  Any ideas?

  I found actually just the problem.  I had to activate the secure gateway PCoIP and I had to enter the public IP address and the port 4172.  Initially, I activated it and he used internal connection server address it and it did not work so then I changed it to the IP address of the DMZ security server and it still doesn't work.  While I was reading upward on the setting that I saw that had to be the accessible public address.  Once he did that, he started to work!

• See 6.2 PCoIP mutli-monitor does not

  We have just updated from view 6.0 to 6.2.  Before the update everything worked ok.  Now PCoIP with multiple monitors does not work.  With multiple monitors RDP works very well.  PCoIP use the option full screen works.

  View agent sees the 2 screens as indicated by the customer. But he fails to set up displays.  The user sees the blue welcome screen for a few seconds and then the connection is closed.  The desktop view is running Windows 7 Ultimate.

  The following is in the log file pcoip_server on the desktop of the view.

  2016 01-05 T 08: 37:29.073 - 05:00 > LVL:0 RC: 0 IMG_FRONTEND: Calling open the display mode Tera2.

  2016 01-05 T 08: 37:29.073 - 05:00 > LVL:0 RC: IMG_FRONTEND 0: configure_displays: 2 views presented initially!

  2016 01-05 T 08: 37:29.073 - 05:00 > LVL:0 RC :-500 IMG_FRONTEND: configure_displays: warning - poster overlap: [LRTB]: [0,1279, 0,1023] X [0,1279, 0,1023]

  2016 01-05 T 08: 37:29.074 - 05:00 > LVL:0 RC: IMG_FRONTEND 0: resync_windows_topology: new api called successfully

  2016 01-05 T 08: 37:29.074 - 05:00 > LVL:0 RC :-500 IMG_FRONTEND: open_displays(): can't set screens, devtap reset.

  2016 01-05 T 08: 37:29.074 - 05:00 > LVL:0 RC: MGMT_IMG-500: cSW_HOST_IPC::enable_frontend failed. 10 remaining attempts. Try again...

  Does anyone have any suggestions.  I tried to re-install vmtools and agent of the view.  With reboots after each uninstall and install.

  Isn't the problem as far as I could determine with the agent of the view.  I have restored my environment view 6.0.1 and still the problem persisted.

  We have been updating vpshere U3 5.5 6.0 environment.  Only workstations where the vmtools has been updated have had this problem.  The suggestion of roneng was useful in helping to confirm the root cause.  But the version provided in the message information was not clear.

  For desktop computers running the most recent version of the vmtools version is 9.10.5.2981885.

  I have download the U3 5.5 vmtools from vmware https://packages.vmware.com/tools/esx/index.html download site

  the version is 9.4.15.2827462.

  After reinstalled vmtools with version 5.5 of U3 PCoIP worked with multiple monitors.

  Thanks to everyone for their suggestions.

• PCoIP disconnect session

  Hi guys,.

  I use view Horizon 5.3.2 and it works fine. I improved environment seen 6.2.0 build-3005368 and left of the VDI (linked clones), running on former agent 5.3.2.1887719 that everything was still working as usual. So I decided to upgrade my vCenter and ESXi environment 6.0 which was pretty smooth. I tried to connect to my VDI by PCoIP/Blast (HTML), but it disconnects after showing black screen.

  
  

  After that, I checked that my VM VDI of machine tools have been upgraded to the latest version. I removed VM Tools and also deleted view Agent. VMTool agent and view reinstalled in order so I can reconstruct VDI, but the problem is still there.

  
  

  I caught pcoip_server newspapers, but I can't find out what is causing the problem.

  
  

  Could someone please look at the newspapers attached pcoip_server and see what might be the reason for the PCoIP or Blast session disconnects.
  
  Kind regards

  
  

  Mobin
  
  

  Hi seb,

  Errors in the logs as the problem described in this article KB VMware: VMware View desktop connection causes a black screen

  It seems that the problem is an incompatibility with the graphics drivers between the Agent to view old and VM tools. Can help to upgrade the Agent version 6.x article view.

  I hope it helps.

  See you soon,.

  Javier