Why I really like the Windows 10 April Update

After working for a week with a preview of Windows 10 1803 (which will be called the April update), yesterday I had to swap my Surface Pro and I went back to the stable build.

The first thing I miss after going back:

I used Timeline a lot: Every time I used Windows-Tab to switch, I started a PowerPoint presentation that I have been preparing for a while.
Not even realizing that I did not search for the file itself, but that I left this entirely to the Timeline functionality.
In addition, I also used it a lot to quickly restore a session: You could already easily restore a number of tabs if you for example shut down your PC.
But now you can easily do this with tabs from a few days back, really the most ideal function to resume the activities of last Friday after a fun weekend.

Furthermore, the Focus functionality is really a huge advantage if you give presentations, although it is unfortunate that this is limited to applications that use the notification functionality of Windows.
The Focus functionality does not work in Chrome for example, because they use their own notification-engine.
What is noticeable however is that a lot of application developers already made use of this, I have not come across anything except Google Chrome.

It was so incredibly natural to use, that I really began to appreciate the functionalities when I went back to 1709.
By the way, the April update will be released tomorrow, so I can upgrade again.
I can not wait!

Read all services and scheduled tasks in your server environment (including Server 2003)

At one point we found out that many system administrators had used their own administrator account for Windows Services and scheduled tasks.
This became a problem only when a few colleagues decided to leave for another company. 

Accounts were turned off and all kinds of services fell out.
Among other things, an SQL server that turned out to run under one of these administrator accounts. 

To know for certain where these accounts were running, I wrote a script that can help with identifying these accounts.
Because scheduled tasks can not be read out with the powershell variant on server 2003, I used a legacy command and changed the layout of the output.
The script asks a number of questions (such as the domain, among other things) on the basis of which two files are generated with all scheduled tasks and services. 

I hope this helps you clean up these scheduled tasks and services. 

Here you can download the script: