This document template is an action and decision log, used to track all actions and decisions taken during a meeting.
In addition to taking minutes of meetings, it’s a clever idea to keep a record of all actions and make sure everyone is aware of the actions they are responsible for.
And record all decisions of a person of authority, so that there is no doubt about who decided what.
By sending this list and putting it in a convenient place, it becomes clearer which actions had to be performed and who made the decisions. During a project, for example, it becomes easier to hold someone accountable if they have decided something they should not have been allowed to do. It is also important that if someone is absent for a long time, all the actions of that person are transparent, so that they can easily be placed with someone else.
In the case of a project, it is advisable to place all actions recorded during a project-meeting, in a project management application, with a reference to the document, so that all actions resulting from a meeting are also included in the day-to-day operations of a project.
This document template is an meeting agenda, used prepare for a meeting.
Every meeting runs smoother when you know in advance what is going to be spoken about. Apart from that, it is also a way to make sure that people prepare better for a meeting, by asking them to bring items to the meeting outside the agenda.
With this document template you can easily prepare for a meeting, making sure that everything runs smoothly. Make sure it is stored in a central place.
I love how this solution is this easy to implement, and how this brings the ease of a modern workspace with a fitting printing solution on the user end. The experience to the user is simply amazing, and I think is took some real effort on Microsoft’s end. So, they did nice work on that.
However, there are some limitations: Follow me or badge printing are simply not possible for now. Physically added paper bins can’t be added. Auto-stapling is not available.
I understand that these are added functionality by the printer manufacturers, but organizations have bought these machines fitting to their printing needs, you can’t take this away by implementing this.
And it’s all because you don’t have a native print driver. Don’t get me wrong, I hate native printer drivers. Without driver isolation on, you can destroy printing for so many clients. Especially in large organizations, this has been an enormous issue. Something you can’t blame Microsoft for, because it was simply bad programming on the printer manufacturers end. Alot of them where using legacy shared components (a lot of printer drivers used old HP LaserJet Components, which would conflict and make peoples print spoolers crash in the past).
I think a wide alliance with Printer Manufacturers is necessary to make this happen, since we can only implement this in doctors’ offices or organizations where there are as many printers as people.
However, I love how this really brings an end to crashing print spoolers and printer configuration issues.
As companies are getting increasingly paperless, this solution gets more fitting by time, I think. For legacy organizations, with comprehensive printing requirements, I think we may also have to start thinking about other ways to make sure printing is implemented in a fitting way. Being creative has been a real help before, a lot of solutions are available, so maybe this will be a big competitor too.
As you may know, Windows Core OS is the core operating system for many future variants of Windows. One of those is Windows 10X, the operating system that would become the primary operating system of Dual Screen devices initially.
Microsoft has recently announced that because of the Novel Coronavirus outbreak, plans to release Windows 10X for the Surface Neo and other dual-screen devices will be postponed and they will now focus on building the operating system for existing single-screen devices.
One of the mayor advantages of Windows 10X is also its Achilles heel. It will run Win32 applications in containers, where only Modern apps will run native in the operating system. This reduces the attack surface of the operating system since every application is sandboxed.
They also will be able to service the operating system faster and more reliably. Some even say that a simple reboot will suffice for Windows 10X, since the operating system can fully install the update in the background (like it does on Chrome OS devices).
This would be the best of both worlds: better battery life, a more secure operating system, fast servicing, more reliability (a win32 app will in the worst case crash the container it is running in), and still support for Win32 apps. Let’s be honest, only Win32 apps will be able to crash the entire operating system.
However, the big issue here is that it will be emulating an operating system for those containers, as we all know this reduces performance in some way. This really shows that Microsoft is still working towards a future where Win32 apps are history.
This script will list all members and owners per team. When you add -savedcred:$true it will save a credential file locally, which will give you automated access using that same account to your tenant. It won’t save your credential plane text, it will use credential vault, which should be perfectly secure. When using MFA on that service-account, make sure you use an app password.
It also list the object ID’s of both the users and the teams, which means you can use the exported CSV for other scripts (like removing a user from all teams).
When you Google ‘Edge Stable’ today, you’ll get the official download link for the stable version of the Chromium-based Microsoft Edge. I downloaded it and saw it had the same Chromium version-number als the beta-channel, which most likely means it will be released soon.
Here’s a screenshot for when it gets pulled (hopefully it won’t):
This script is made for automatically cleaning folders.
You can create a scheduled task to automatically clean a folder.
If you create a scheduled task using Auto_cleanup.ps1, you can clean a single folder (recursively). You can use the Path argument to define a path, and use the daystokeep argument to define the amount of days that files and folders should be kept. Example: Auto_cleanup.ps1 -path D:\folder -daystokeep 7
If you create a scheduled task using Master_Cleanup.ps1, you can define multiple paths and the amount of days files and folders should be kept within the path. Paths, amount of days and the name of the blockfile can be defined in folders.csv. Warning: contains example.
What it does
It deletes all filders and folders within a single (auto_cleanup.ps1) or multiple (Master_Cleanup.ps1 with folders.csv). It also creates a placeholder which says that all files and folders will be removed within the defined timeframe. it also gives the possibility to create a file to block the script from running (like for troubleshooting purposes).
Blockfile: define the name of the file that can be used to block the script from running
Path(mandatory): Define the path where the script needs to clean
Daytstokeep(mandatory): The amount of days that it will keep info
All arguments are mandatory when using Master_Cleanup.ps1
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!
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.
I have had an issue with WSUS on Windows Server 2016 which resulted into computers not reporting correctly to WSUS.
Thinking that I have configured everything correctly because computers where connecting to WSUS (they targeted the right WSUS groups from the Group Policy in the WSUS Console), they where not reporting their status to WSUS.
Actions Required To Troubleshoot These Issues In WSUS
However many don’t realize this, the most effective way to resolve issues is to understand the problem.
Don’t just start to search the web blindly, get to know the (basic) inner workings of an application
Locate all the logging, many applications have documented default logging locations
If necessary, increase logging. Many applications have options to add information to logging.
Check if requirements are met
What is WSUS
WSUS is largely built on IIS (Microsoft Internet Information Services), .NET Framework and MMC (Microsoft Management Console).
It uses WID (Windows Internal Database) or Microsoft SQL Server as its database engine.
It acts the same way as the publicly available Windows Update, but with WSUS you are able to deploy updates to your systems at your own pace and compliance requirements .
Off course you are able to offload your internet connection by downloading your updates locally, but that never was my primary concern.
You can even create an Internet-facing downstream server, so that your systems download your own approved updates even outside your office(s).
This way you keep your systems up-to-date and/or secure (which off course is largely recommended), without your systems being incompliant to your own requirements.
This figure made by Microsoft shows how WSUS works.
In the official Deployment Guide made by Microsoft, the first step it says is to ‘plan’ your deployment.
Immediately followed by requirements.
First check if requirements are met (Reference 1).
In many cases the requirements are never checked when implementing a solution.
Even when you deployed it yourself, dare to second-guess yourself!
Depending on IIS, .NET Framework and SQL/WID, WSUS can actually get issues from configuration problems of these services.
Make sure you don’t just check WSUS, check all the parts that make WSUS.
For this the requirements are important, because these services are a requirement for a reason: they are important to WSUS its architecture.
Best practices are never a requirement.
It can make sure an application/service runs at its best, but only requirements are needed for an application/service to run normally.
Logging you can find in the following locations:
Reporting to Windows Server Update Services on Client: C:\Windows\SoftwareDistribution\reportingevents.txt (this file is always there – even when using public Windows Update)
Log of retrieving updates on Client: Get-WindowsUpdateLog (generates a log file on your desktop from Event Tracing for Windows)
IIS on Server: c:\inetpub\logfiles (or check the inetpub location in IIS)
In the example I’ve set I said that computers had issues reporting.
I knew they connected to WSUS (otherwise group-targeting wouldn’t have worked), however they where not reporting status to WSUS.
This has led for me to check the reportingevents.txt on the client, since Windows Update was connecting to WSUS, just not reporting to it.
This is an example how you can use logging to support your first theories about the problem itself.
Coming to a conclusion
Coming to a conclusion with major WSUS issues can be a bit of a struggle.
WSUS is a complex product, reliant on many technologies.
A conclusion can’t be made before you know where the issues lie:
On the client or the server
In IIS or maybe SQL.
Make sure you know the issue, there always has to be a place where some error is reported in logging.
However targeting worked (computers where placed in the right Computer folders in WSUS), computers wouldn’t report.
When I looked into the ReportingEvents log in C:\windows\SoftwareDistribution folder, it showed a error “Windows Update Client failed to detect with error 0x8024401c”.
However this error wasn’t consistent (sometimes it did succeed, but it mostly didn’t)
It looked rather odd.
Browsing the web more people are talking about issues in IIS.
So I compared the Advanced configuration of the WSUS app pool in IIS (server 2016) to an old environment I have built (2012R2), I saw it had an Private Memory Limit of 1.8GB.
Changing this to 0 (unlimited), computers immediately started reporting.