In the previous article series about deploying Windows 10 IoT terminal I talked about the global use in the Introduction, and secondly how to protect the C drive for unwanted change.
Now in this article I will bring subject, how to publish application to those terminals and I will start by talking HPDM.
It exist some way that we need to think about;
– Application pushed by a remote server and using the remote server ressources; Remote App, XenApp (technically speaking you need the RDSCAL to run XenApp, as such I tell about it there, but overall you must see XenApp as a feature set over RemoteApp)
– Applications pushed by a remote server, but running on the terminal; App-V, MSIX, XenApp Streaming Client (depreciated)
– Applications pushed by GPO (.MSI)
– Application pushed by HP Device Manager (HPDM)
Now the fact that we protect the hard disk bring us some limitations, as such in my guide I suggest for Office, or such application to be pushed by RemoteApp (or XenApp). The limitation is not only the fact the hard disk is using a UWF, but by the fact on IoT terminal the SSD is often small, and we try to not overuse it by product update. With a central server you can update the program and each terminal would be using the latest version of the productivity’s suite.
I would start by talking of the HP Device Manager. On other articles I will cover other’s way.
We need to install it first and I suggest the latest version 5. We now need to have an account, and you need to ask to download, after we can got it free.
I will skip the install step as I want to focus on how to push the application correctly with the tool.
For the test I will push Google Chrome Enterprise.
At first we go inside the template menu in HPDM, and we want to push the file to the terminals;
We select the _File and Registry Template
Inside the template we click Add (Ajouter)
We click Deploy Files (Deployer les fichiers)
We click to add the Chrome Enterprise .msi
For the folder we select C:\TEMP, which is a special folder for the terminal.
We create an install.cmd (with that content), and we will push that file too;
Now we click Ok, HPDM will upload the file to its HTTP repertory and we click Generate.
After that we create a script action;
We save that, and now we do another template, a Sequence Template.
Inside the sequence, we need that;
- We turn OFF HPWF or UWF.
- Change Temp to C.
- We deploy our first sequence’s files.
- We change back Temp to Z.
- We turn ON HPWF or UWF.
The task should look that way:
And voila, we can now deploy to any number of terminals we want the needed local application they need ! That finish that article.
Take care, and see you soon in the next article for that serie 🙂