##TOP## Download Windows 7 Embedded For Thin Client
Janvier Bender
So a little background. We recently upgraded our thin client mini-fleet from WYSE Embedded XP machines to Windows Embedded STD 7 WYSE machines in a standard domain environment. Found a couple issues we wanted to tweak and cannot due to the stripped down OS. Want the users to be able to lock the machines (we have separate processes for user auto-log off), but found:
I had an inclining about that earlier. I viewed the policy and passed over it thinking our domain GPOs are set to not configured as well as the local policy of the thin clients. Now thinking about it, that just might work. Will give it a try tomorrow and let know. Hopefully this works in conjunction with the reg key entry that will solve it.
I have used HP t610 thin clients in the past (still operating) running the HP Thin OS, which is a stripped down version of Ubuntu Linux. It will run the full Java jre, but you will have to be familiar with Linux and install it yourself.
This is the first post in Citrix Forum and hope it will not be the last. We are finalizing the deployment of XenDesktop/XenApp and migration from Dell vWorkSpace VDI Product. We are using Skype for Business 2015 and I would like to explore the best thin clients that are compatible with HDX in order to have a complete collaboration of Skype for Business.
We are currently using Dell Wyse Thin Clients DX0Q Windows 8 Embedded and planning to purchase couple of thin clients as well. Can you please help and advise so I can have smooth integration..? It would be helpful if someone could share a procedure in order to establish the integration, that would be much appreciated.
Hi.
Talking from a Skype for business perspective you can use any OS thinclient with RTOP. However, performance will vary especially for video calls where it is important the endpoint can do decoding fast either in CPU or GPU. For encoding you shouldn't worry as long you get a decent webcam that can do encoding on its own and the OS you run has a driver for this webcam.
Everything comes down to testing pretty much, there are so many combinations out that customers run successfully. A big hint for you is to look out when using Linux clients as headset/phone emulated devices that use advanced USB events might not work with linux drivers.
We have a bunch of thin clients that are running Windows 7 embedded with the write filter active on them. We have the CCM, CCMcache, CCMsetup folders, and the smscfg.ini file excluded so when things are written to these the changes are applied. We are currently running CM 2012 R2.
If you look at the thin clients the sccm client seems to be running fine. The only way to get the device to start talking to the server again is to stop the SMS host agent, delete the smscfg.ini file, and then start the service again. We have around 300 thin clients and I can't keep doing this manually.
Would either of you know or seen where these devices go into Service Locking Mode and only the Administrator can log on? I've done some research on it and pointed to possibly the clientstate.dat is the culprit matter but not all the time. I think I've narrowed it down being the ccmsetup.exe for CU4 on the client but until you take action to put the client with Write Filter disabled and leave it for awhile, it will keep popping up. I haven't been able to locate how to Commit with Write Filter enabled, do you know?
we just purchased a HP Thinclient, I think the name was ME06 and seems to run quite well for it's size and speed, we have however one issue, every time it reboots it goes back to the original settings everytime, default user is same as username and administrator is administrator etc etc.. we wish to change this and commit the changes...
HP thin clients that use Windows embedded as the operating system (OS) have a feature that causes them to revert back to the previous state upon reboot. With HP thin clients, if you need to change something in the OS, follow these steps to make the change.
Does the host the clients are running on have AV? And are the shares scanned on a regular basis? This could be a good halfway house, but won't be able to detect in memory malware, but to be persistent, malware must write to a file "at some point" and when this happens if you are scanning all the mount points used within the thin client, then you should be able to detect it.
In case of Windows-based HP thin clients (Windows Embedded Standard 7 either Windows 10 IoT Enterprise based) Windows Defender is included and enabled by default:Windows-based HP thin clients - Antivirus Software Support.
Even before WVD came to the forefront of the desktop virtualization market, thin clients were popular with many organizations for traditional remote desktop environments. This was due to thin client's ease of use, strong security and low cost.
Whether those thin client devices were based on Windows Embedded, Linux or a proprietary OS, it was incredibly simple to physically provision small thin client devices and maintain them via a centralized management platform. Further, users had no affinity to their devices because there was no personal data on them.
The same thin client benefits can help WVD environments today. The COVID-19 pandemic caused a massive number of workers to move their worksite from traditional offices to remote locations. Organizations sent these workers home with various types of devices, including laptops and desktops, but thin clients are typically the most cost-effective option.
The Linux-based devices from IGEL, NComputing and Stratodesk are generally more secure than Windows- and macOS-based endpoints. Microsoft provides a Linux SDK for WVD, which these three vendors use to build their own remote desktop client. There are also Windows 10 IoT Enterprise-based thin clients available from vendors such as Dell Wyse and HP. Windows 10 IoT Enterprise is basically a scaled-down version of Windows 10; its predecessor was Windows Embedded.
IGEL has taken a novel approach to thin clients. Rather than forcing their customers into a full hardware purchase, IGEL's offering focuses on software. Administrators can centrally deploy this software via system management tools or the UD pocket. It is a USB device that plugs into an existing endpoint and enables the user to dual boot to the Linux-based thin client that runs on its own IGEL OS. Thus, an employee who moved from the corporate office to the home office can just plug a UD pocket into a PC and get to work.
The approach that Stratodesk takes is also a bit different compared to the rest of the market. Similar to IGEL, Stratodesk has a custom OS that runs on endpoint devices via a USB device, and the Stratodesk NoTouch OS can work for numerous virtualization platforms, including WVD, Citrix and VMware. Unlike IGEL's offerings, Stratodesk focuses on the management aspect of thin clients with the USB add-on. It can function on full devices or even other thin client vendor's devices.
This vendor offers a wide range of thin client devices that organizations can choose from, but the vendor has devices that are built to work with certain virtualization platforms, including Windows Virtual Desktop and Citrix Virtual Apps and Desktops.
The RX420 thin client model and one other model in NComputing's RX line, the RX-RDP+ support WVD. The RX-RDP model doesn't offer WVD support. The RX line is built on Raspberry Pi and the two models that support WVD also support 5GHz Wi-Fi.
The thin clients that Dell Wyse offers range from the most stripped down to the feature-rich models. The Wyse 5070 thin client is probably an organization's best option to support WVD via Windows 10 IoT Enterprise, but organizations could also opt for the 5470 -- both the all-in-one and mobile thin client versions. In addition, Dell Wyse is rumored to have plans to include a Remote Desktop client in a future version of its ThinOS.
With HP's thin clients, organizations can also choose from a range of zero clients, mobile clients and desktop thin clients. The zero clients that fall within the t310 line come with no local OS, but the mobile and desktop clients come with the Windows 10 IoT Enterprise OS and a license to go with it. The mobile thin clients include the mt46, the mt45, the mt21 and the mt22, and the full desktop thin clients include the t740 and the t430 models.
As part of reviewing business and technical criteria for WVD endpoints, there are many considerations that may determine whether thin client devices are the optimal device choice. If they are, organizations must pick which vendor and model are best. In many cases, manageability and security are critical factors, so thin clients are optimal.
One important consideration for thin client devices is an organization's goals for the future. If an organization has deployed WVD as a short-term option with plans to adopt the more robust Citrix Virtual Apps and Desktops or VMware Horizon platform in the future, the same thin client may not be capable of supporting Citrix HDX or VMware PCoIP Blast. Similarly, existing thin client devices that access Citrix or VMware today may not be capable of accessing WVD.
In addition, thin client devices have limited functionality as a standalone device. Exactly how much functionality depends on the OS and specific device features and specs, such as memory, RAM, type of display support and ports for USB or other external devices. Even though some thin client devices physically look like laptops, they are not capable of full laptop functionality without internet access.
df19127ead