Save BONES for thin client

Similar Questions

• How to configure the mode of kiosh for thin clients on windows server 2008

  I have an eight Thin Clients who will use RDP to access (Terminal Server Services) Remote Desktop Services on a Microsoft Windows Server 2008 R2 Standard. I would like to set up a group of users for these Thin Clients to be in a mode Kiosh so that they have very limited capabilities, can not download and run anything, unable to save anything in the computer except on the desktop and when they log off and back on everything, they had disappeared because the mandatory profile is loaded again.

  I'll have another group that more access is needed.

  Kiosk.

  Post in the Windows Server Forums:
  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer/

• HP t620 Flexible Thin Client: Windows 10 IoT Ent. Client light-load Multi Touch

  Customers light t620 (Std/MORE) running 'Windows 10 IoT Enterprise for Thin Clients' supported multi touch? Or alone only?

  Having a hard time finding a definitive answer online.

  Thank you

  The answer is Yes.

  See Page 5... http://WWW8.HP.com/h20195/v2/GetPDF.aspx/c04312126.PDF

  "Smooth, immersive experience with technologies like advanced multi-touch and Windows® 10 applications"

  -Keith

• Thin Client configuration documentation?

  I have searched the VMWare Web site, lived my administration guides, etc... but don't found no link to the effective documentation for creating connections for Thin Clients.  I see light client equipment compatibility Guide everywhere... but no information on how to connect them to my VMWare View VDIs.  Can someone point me to the documentation?

  What is my goal... I want that my Dell FX160 customer light to start, what he does with Windows XPe and then connect immediately (without prompting) to a Virtual Machine... keep this active link and allowing users to log on / off power if necessary.  It is a medical environment, where there are many many users by Virtual Office...

  All documentation that will help me in this way is appreciated...

  Hiya,

  You must install the latest VMware View Client (now it is 3.0.1) you're XPF to the device. Log in as an administrator and install View Client. Create two scripts in XPe.

  Create a file view.cmd with the following text.

  off @echo : View "C:\Program View\Client\bin\wswc.exe VMware." GoTo view

  Place it wherever you like, for example c:\BatchFiles

  Create a view.vbs script with the following in it. Place it where you like C:\BatchFiles for example.

  Set WshShell = CreateObject ("WScript.Shell") Chr (34) WshShell.Run "C:\BatchFiles\view.cmd" & Chr (34), 0 Set WshShell = Nothing

  Open Regedit and go to;

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

  Change the Shell to explorer.exe to the new path of shell and Windows script command, for example wscript c:\BatchFiles\view.vbs

  The above code was published on the website of VMware view Blog to

  http://blogs.VMware.com/view/2009/02/VMware-view-client-as-a-shell-for-XPe-and-XP-Pro-clients.html

• Thin client recommendation or Advisor

  I realize that this issue is somewhat subjective, but I'm hoping to get some good recommendations. We are looking in a VMware View deployment, but we are not familiar with thin clients. We hope to standardize on 1-3 types of thin clients, hopefully with the same provider. Our thinking is that we would have a client who is good for 98% or our users, for "power users" who need a more powerful client and one for the lab machines which were not yet as much as regular users. We are also thinking about a type of 'portable' thin client for some users who currently have laptops (maybe).

  I did some research and Wyse seems to be a good brand, but I want to be sure before I recommend something to the top of the line. My main concerns in a thin client are ease of management, security, ease of use (both for administrators and users), saw the transformation of power needed to run tasks users want to (which includes the possibility of two monitors), having the ability to multimedia unloading for the client and the server, and the PRICE.

  I found a Wyse V10L for about $320 (running Wyse ThinOS) and a V90L for about $415 (running Windows XPe). I don't know what benefits (or disadvantages) we are running a "thin" compared to Windows XP or XPF OS. Also, I wonder how much memory difference allows a thin client. It seems that many of them come with 128 MB of RAM, but that does not seem a lot. We do not know whether we should target a customer who has at least 512 MB RAM, or if it really matters that much.

  I hope that gives you an idea of what we are looking for. I'd appreciate any advice or information on the brands, which OS is to use (or not), what to look for in terms of processing power or memory, etc.. We do not spend more than $500 on a thin client that receive us so close an office price, although I realize that the life expectancy of the thin client must be superior to that of a desktop computer, in theory.

  The HP product can do what can do the Wyse, but they have not officially released the software to do it on the t5545, only the XP embedded customers light up to now. That should be coming this month, and yes it does not Add ' l $$$.

  For the Wyse, you don't need a server to Add ' l to do the TCX things... and they do not need to be in Active Directory. There are consoles for thin clients two sellers, but those who are for asset tracking/remote management help more as they are for authentication.

• Thin Client T510: Do not support the SMB for no image preload on Linux platform

  Hello world

  I have a problem with a Thin Client T510 (C4G87AT #ABA), this one came with Windows CE and today I flashed with a USB to thin Pro 5 (T6X52011). When I want to deploy the image I captured (wallpaper, RD Session etc...) I have the following error:

  2015-08-19 15:30:43 [error details]:... /... / Task/linux/ImageTask_Thinpro.cpp@384: Metheod of the Image is not compatible.
  .. /.. / Task/linux/ImageTask_Thinpro.cpp@1624: do not support SMB for no image preload on Linux platform.

  When I look in the console HPDM, I see the T510 and connected

  Agent version: 4.6.3670.21244

  HDPM 4.6 SP5

  OS: T6X52011

  My OS: Windows 8.1 x 64

  Can someone help me please? Thks and have a nice day.

  Hi, thks for this Council. Theres is how I fix.

  Firstly, the master repository has change from D:\HPDM\HDPM to D:\HPDM on the server, so the configuration was not good at the moment. Another thing, the password of the user hpdm has changed in Active Directory, but not in the configuration. I changed all the settings for in line with the current configuration and capture Images of thinpro news works very well and deploy this new works pictures well too but Deplopyement of old images does not work.

  I'll open another thread if I need assistance. In this case, I'll mark as fixed.

• I made a form for my clients, I did this form with a button "submit" button, the button will save the form and send it, I did the URL to go to a different (different to mine) e-mail address but when I distribute the form and it is complete

  I made a form for my clients, I did this form with a button "submit" button, the button Save the form and send it, I did the URL to go to a different (different to mine) e-mail address but when I distribute the form and it is supplemented by my clients it send to my email address not the URL how to change this.

  No matter how you have configured the Send button when you use the feature distribute the form. There are some e-mail address is in your identity preferences (Edit > preferences > identity) and use it. If you can change the email address it or not to use distribute the form and the button send the value you want.

  One thing that happens when you use the feature to distribute the form is the form is enabled Reader, you can do separately, but you really shouldn't do if the form must be used by others. The dispenser a form must activate using their copy under license of Acrobat Reader.

• Choosing the thin client just for our solution! (health care)

  Hello community,

  I can't try to define the best thin client PCOIP solution so that I work at the hospital.

  We are currently working with Vmware view 4.5 with Oracle sunray thin clients/broker

  It works very well with smart card authentication, but we want to feature implend instead of RDP PCOIP

  and get rid of the sunray broker because he dousent enters our landscape.

  Now that we're about to go upscaling (from 100vm to 1000vms) as possible, we are looking for the right thin client

  We tried the new dell Fx130 & 170 with the dell Detos reference edition

  However, we feel its underdeveloped and it can not handle the Pre-os how smart card authentication

  customers current sunray are skillfully to (follow me desktop) and lacks a disconnect button.

  Ideally:

  1. We do not want a built-in windows machine since it's patching/security on the thin client
  2. It's a simple thin/zero client that we can manage a centralized management point.
  3. who has PCOIP functionality
  4. A biometric capability / card smartcard/proximity (if necessary with another agent of connection)
  5. and has a material disconnect as button
  6. Follow me / roaming Office

  Can someone help me in the forest of solutions and thin clients or push me in the right direction?

  Any help is appreciated!

  This can be done with the power button. Push, little time to disconnect it take longer to power off of NC

• Thin client for virtual desktop

  This Thin Client would agree to operate the virtual office?

  HP GY227AT; Thin client HP Compaq t5730 - Tower - 1 x Sempron 2100 + / 1 GHz - RAM 1 GB - no HDD - Radeon X 1250 - Gigabit Ethernet - Win XP Embedded

  What is the minimum/recommended specification for a thin Client Solution typical?

  Rgds,

  Jamie

  Welcome to the Forums - if you are referring you can use this Thin Client with VMware View, the answer is Yes according to the compatibility guide - http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=vdm

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Cable virtual thin client for xp

  I have a virtual machine running Windows XP. I have a thin client, which must be copied using a crossover cable, connected to a XP Server. How can I do this with virtualization?

  Jumpered the value Network Adapter to the Virtual Machine and connect the cable to the Ethernet of the host card

• 3.1 client for Linux thin clients

  Its great that you can do all this with light customer Windows, but what of us, guys who have Linux thin clients who don't get to play with all these cool features?

  We release publicly on the Linux client sales literature because it goes directly to the partners of thin client.

  WP

• T610: thin client, multi-imaging platform

  Hi all

  IV ' e hoping to put this in the right place and someone can help or point me in the right direction.

  I'm looking for information on Thin Clients and Device Manager (HPDM), specifically on best practices on building and image capture, cross-platform and imaging would be advantageous.

  I am currently using HPDM Imaging for my thin clients t5470 and t5470e, t610, t620.

  I'm looking for a few docuemntation on recommended Configuration of HP for Imaging. is it to make a "gold" image or it can be pre-determined by HPDM like Microsofts SCCM or WDT?
  
  It would be fantastic if I could get it down to a single Image of WES7 for most of my Thin Clients if possible.

  Thanks in advance.
  J

  HPDM provides no functionality of creating an image, tt just do capture and deploy.

  The factory image include all drivers are built by HP R & D WES, there should be no one who can help you, but as far as I know there is no document to save the steps in detail. I suggest that you raise a ticket to impact to HP for help.

  MDT can not be used to deploy the image provided by HP. When building the image, no matter it is an original image or Thinupdate captured image, HP has done little customization in/after imaging process. I don't think that MDT can identify and carry out even these customizations.

• View 4 thin client hardware supports PCoIP

  If my thin client is windows-based os, there is no difficulty when we improve the mode 4. But what happens if my thin client is thin-os, such as wyse S10? do I have to replace it with a new model like P20 or seller will provide a new firmware?

  Hi Dingding,

  You can still use your existing endpoint hardware after and upgrade to view 3-4 of the view, as RDP is still available as a graphic distance communication protocol in View 4.

  If however, you want to upgrade to PCoIP, then you will need to worry about your endpoint equipment.

  PCoIP software, you can use VMware View 4 Client for Windows, which runs on Windows XP, Windows Vista and Windows 7. (And maybe even Windows XP Embedded)

  If you want to use your Wyse with PCoIP devices, you must wait for Wyse provide updated models. The P20 is the only model that Wyse announced so far. Wyse in the future will also support PCoIP on thin BONES.

  Here's an announcement from Wyse on PCoIP:

  http://www.BusinessWire.com/portal/site/Google/?ndmViewId=News_view&NewSID=20091110005514&newsLang=en

  Christoph Wegener

• HPDM: HPDM can't see any of my thin clients

  A few months ago, I set up a server HPDM on Win 2012r2 and light HP 12, mainly mt245 clients. I could see all the thin clients with HPDM, I even used it for the Image of each of them.

  Yesterday, I went to add a new abd mt245 the image. All TCs went from HPDM and it does not find it again. I tried to walk to the beach. I tried to manually add as well as at the foot of the range of the exact IP that the TC has to say things. I ping the TC from the server and vice versa.

  The Windows Firewall is turned off completely.

  Any thoughts?

  Thank you

  Travis

  Well. I thought about it. I forgot to click on the name of the gateway on the left. Stupid sound is not automatically select one on its own.

  Travis

• Thin Client T5000 series password reset

  Hello, I bought a few days there are some thin clients to someone.

  These has always his password to get into the bios.

  All thins are T5000 series.

  Dous anyone know how to remove this password? / or clear all default settings?

  -J' looked for a reset jumper, but did not. One jumper is near the audio output, but I guess that's not what I'm looking for.

  -removed battery CMOS for a few minutes, did not help (maybe I should consider longer?)

  Thanks in advance,

  Drosaert S.

  Thanks Hanspuppa, that worked.

  Suddenly, I realized that, as you say, some capacitors may still have some fees top just after their closure.

  So I left the Jules Destrooper unplugged for a whole night, and after that I removed the CMOS battary for 1 hour. That's all.

  Thanks for your help...