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.
This article goal is to list all new feature per Windows 10 Build
)
Build 16226 - 22 June 2017***
Build 16215 - 8 June 2017
- Edge : X always available to close a tab (16226)
- Edge : Cookie and setting more easy to migrate from another browser like Chrome (16226)
- Edge : Now allow copy and ask in Cortana (16226)
- Edge : Favorite handling improved, gooing back to IE look and now allow easy editing like IE. Now allow pushing favorite for IT Admin, likein IE. (16226)
- Emoji 5.0 added (16226)
- OneDrive : Added setting Settings > Privacy > App-requested downloads (16226)
- OneDrive : File on demand feature added with a new onedrive client (On the Settings tab, select the Save space and download files as you use them box.) (16215)
- Touch Keyboard : Multiple tweak (16226)
- Core : GPU tab in taskmgr.exe added and you can display the process grouped per apps. (16226)
- Core : SMB1 removal for enterprise edition, depriciated for home edition (16226)
- Settings : Added Delete your previous versions of Windows straight from Storage Sense (16226)
- Settings : Remote Desktop new settings tab (16226)
- File Explorer : Share with update to Give access to (16226)
- Calculator : Added currency converter (16226)
- HyperV : VM Share option added, new file formt to support the feature ; .vmcz (16226)
Hi everyone
A small update, now we must be sure FRS SYSVOL share are migrated to DFRS to allow a 2016 DC RS3 to be able to dcpromo.
)
https://support.microsoft.com/en-us/help/4025991/windows-server-2016-rs3-no-longer-supports-frs
Windows Server 2016 RS3 can no longer be added as an Active Directory domain controller (DC) to an existing domain that is still using File Replication Service (FRS) for replication of the SYSVOL share.
Hi everyone
Today I will discuss a nonstandard way to migrate a Exchange 2007 to a Exchange 2016.
As we know it, we must say goodbye to Exchange 2007 because it mo longer receive support

The bestpractice is to install a 2010 to do a two step migration, but in some case if you can't, you could do a one step migration (for small customer)
That imply this;
You have to save all users email in PST.
I suggest to go PC by PC if you want to backup the Outlook autocomplete cache
There will be a downtime in the email flow.
The step;
The good side;
The bad side;
Thanks, that resume how to do :)
Picture took from; https://www.codetwo.com/admins-blog/time-to-say-goodbye-to-exchange-2007/
Hi everyone
I wanted to share a good new. Iam now a father of twin :) !
All went good, now you can wish me good luck for my night! hehe

Hi, today I will talk a small tip to force a user logout when a machine has been locked for a specified period of time.
The specific question I seen that I want to answer was;
There are machines in a shared lab. Sometimes someone will lock the machine with the intention of coming back, but for whatever reason they do not. Currently the machine is powered off so another user can use it.
What would be nice would be to set a timer, say 20 minutes, then have a button display that could allow the next user to claim the machine. It should logout the current user and present the login screen to the next user.
Is there a Group Policy setting or perhaps some other means (Windows Credential Provider) to force a user logoff when a machine has been locked for a specified period of time?
That small tip is handy for internet cafe or in any case where there is shared computer.
First of all, in a case of shared computer, a local administrator can force a logoff or a normal user can switch the user in that windows with the option switch user
For it's a workaround, but it would be to create a local planned task with a on idle trigger with a 30 minute condition and the task will run shutdown /l



If someone wonder if the tip will happen if someone watch a movie, and the computer is not locked, then we can validate on technet, and no, as;
Task Scheduler checks for an idle state using two criteria: user absence, and a lack of resource consumption. The user is considered absent if there is no keyboard or mouse input during this period of time. The computer is considered idle if all the processors and all the disks were idle for more than 90% of the last detection interval.