Important
To filter the blog, please use theses tag:
General news.
Website related post
website.
parental-control about technology.
technology post.
Note
All blog links are archived here.
Hi everyone
On IoT terminal often the hard disk is small, and there is a activity that can be a pain in such device, it's to install a cumulative update.
The last update I did I had in example 7gigs of free space, and the uncompressing of the patch did fill the space completely to make the update fail.
To show the problem you can see these printscreens, please remark the free space available;



In my example in my struggle to install the patch, which is by itself 1.6gig, I tried to run the patch from the network, but voila, it's not possible. You would receive such 0x80070003 error.

The tip I give today is to make an ISO with the patch, so you can mount the .ISO from a network share to trick the system.
I my case as Windows can't make the ISO natively, I got a free tool to make the job, wincdemu. A lot of other tool exist to make that work by the way.

After the tool is installed, you can just right click your update folder, and select the Build an ISO image option.

You can name the ISO like patch.ISO.



At that point you can wait.

Thanks everyone, hope the tip help some
Hi everyone
Today I wanted to share a quick tip if you want to allow your users to set their own resolution.
By default the unified write filter allow some registry key, but when a user set a resolution, that setting currently impact all users sessions, so that specific setting is inside the HKLM.
As the seeting can change depending on the terminal you use, I would give you the tip to find the correct keys.
I used process monitor, and I log what SystemSettings do in the registry when you click to change the resolution, in example;

As you can see, the registry key might be long, you can select to easilly copy it;

Inside the terminal after, add the exception for that registry key hive;

Thanks for the reading
Hi everyone, today I waned to share a small tip that not everyone know; how to send the famous key stroke CTRL-ALT-DELETE to the remote system in Remote Desktop.
It's always useful, in case you want to bring the task manager, or to try to recover from a unresponsible session.
ctrl+alt+end is the prescribed way to do this.
A small tip it's, but it's handy to have :)
You can see other shortcut there; Remote Desktop Tips and Tricks
Hi everyone
Today I wanted to share a small problem with Windows 10's newer build, 2004.
Login script that use net use no longer seem able to be used, the mapping no longer work.
To work around the issue you have two possible's way;
Add a timeout in the script's beginning;
timeout /t 60
or add a delete script first before the mapping;
NET USE * /DELETE /YES persistent: yes
Be sure that setting is set too, set it if not already before trying to make the workaround;
Computer Configuration
» Administrative Templates
» System
» Logon
» Always wait for the network at computer startup and logon
Some other mentionned that Enabling SMBv2 could help, but it all depend on your environnement, as in my case it happened between Windows 10 2004 client and a new DC in 2019.
Hi, Today I wanted to share a small tip if you want to enable local write for the HCU / HKEY_USERS registry hive with UWF enabled.
By default UWF does not allow to exclude the HCU/ HKEY_USERS, you will got error if you try to exclude those registry path.
The tip seem small, but it's not intuitive to do it with UWF. The tip is to exclude the NTUSER.DAT folder where those settings are wrote. c:\users\ if you want to exclude all user profile, or just c:\users\userx\ntdata.* where you want to exclude the registry.
With such exclusion it would be mandatory to exclude that registry hive;
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
That exclusion would make sure Windows will remember each profile created inside the computer.
Thanks everyone