Today I will cover a topic that will fall into multiple subject and that not many blogger talk about; How to plan and deploy a lot of Windows 10 IoT terminals
In my test I used the new HP ThinClient (t430) that is bundle that way;
- Windows 10 IoT Enterprise for Thin Clients
- Intel® Celeron® N4000 with Intel® UHD Graphics 600 (1.1 GHz base frequency, up to 2.4 GHz burst frequency, 2 MB cache, 2 cores)
- Integrated: Intel® UHD Graphics 600
- 4 GB DDR4-1866 SDRAM (1 x 4 GB)
- 32 GB Flash memory
- Intel® Dual Band Wireless-AC 9260 802.11ac (2×2) Wi-Fi® and Bluetooth® 4.2 Combo
The look is that way; as you can see it’s really small and built to be flexible where to install, like able to fix them to the back of the monitor if needed.
It’s a handy device for place like a public library
These thin client advantage is that they come shipped with some management software and come with the full Windows 10 feature set. The Windows IoT for that model is an Windows 10 Enterprise LTSB build 1609.
Pre deployment, you have some questions to ask yourself;
– Where the user profile would be stored ? Roaming profile, Mandatory profile, Redirected folder, etc…
– As by default the system drive is locked (HPWF or UWF), do you plan to write exception for the user profile if it’s not a roaming profile ?
– How you will plan to deploy software, HP Device Manager, or with GPO ?
– As the device ram can be limited, and the system drive locked, do you plan to deploy a RDS server to deploy additional applications to the users ?
Some limitation you need to know before the deployment;
– The HPWF or UWF by default use a part of the RAM to store the files activities, which can limit what you use on the terminal.
– If you use a locked drive, you need to think for antivirus update, where you store them, so the machine could store the data (Write filter exception or thawed space)
– Windows Update need to be planned as by default the terminal does not update itself. So you must do sequential task usually to allow the Windows update install to stay inside the machine.
As you can see, to deploy such solution bring some questions, but in the end to think it before a deployment is the best course of actions, as it will lead to good user feedback in the end.
Thanks, and stay tuned for other articles coming soon !
I will talk next on how to deploy the machine + autojoin to the domain (part 3), how to manage and control the write filters with example (part 2) 🙂