When going to apply updates, there should at least be an option to check for updates if updates are already found. This was previously an option through Server 2012 R2 and is no longer possible. Because of this, changes to available updates may not be received by the client computer until after the update list is applied and the server is rebooted. Given how locked down the update interface is now, even having that option automatically happen in the background would be great.

In my environment, I use WSUS to patch all of my servers. This month, KB4041691 was installed as both a CU and a Delta (the delta appears to have been a mistake). I didn't realize this until after the fact, but this means that the update was installed twice and caused my servers to not boot. The patch was expired 7 hours after being released, however any server that had checked into WSUS before that expiration still had the Delta as a required update. If the server had checked back into WSUS before applying the updates, it would have realized that the update was no longer valid. This would have saved several hours of troubleshooting. I ultimately had to use the recovery options to remove the update which caused the server to not boot using information from https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/monthly-delta-update-isv-support-without-wsus

If have some issues with Dism after a new Installation with Windows 10 1709 and Upgrade from Windows 1703 to 1709.

Get-WindowsCapability : Error "Get-WindowsCapability". Errorcode: 0x800f0954
Line:1 Zeichen:1
+ Get-WindowsCapability -online
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-WindowsCapability], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.GetWindowsCapabilityCommand

Some Lines from Dism Logfile:

DISM OS Provider: PID=7180 TID=6088 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

DISM Provider Store: PID=7180 TID=6088 Failed to load the provider: C:\Users\ADMIN~1.TES\AppData\Local\Temp\38977CD8-C67C-463B-8721-E72E5E46A990\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

DISM Provider Store: PID=7180 TID=6088 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

2017-10-19 17:39:03, Error DISM DISM Package Manager: PID=7180 TID=6088 Failed enumerating capabilities - CDISMPackageManager::GetCapabilityCollection(hr:0x800f0954)
2017-10-19 17:39:03, Error DISM DISM Package Manager: PID=7180 TID=6088 Failed to get capability collection. - CPackageManagerCLIHandler::ProcessCmdLine_GetCapabilities(hr:0x800f0954)
2017-10-19 17:39:03, Error DISM DISM Package Manager: PID=7180 TID=6088 Failed while processing command get-capabilities. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0954)
2017-10-19 17:39:03, Info DISM DISM Package Manager: PID=7180 TID=6088 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2017-10-19 17:39:03, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0954

Thanks

I work in a software company as a systems engineer for many years, and I always had a problem: "How do I track the status of all Windows servers that install, some of which are of primary importance that they are always very efficient and online?"
I started searching online, and actually there are several services which offer a monitoring system. But they all have the same problem, or are very confusing, or require the opening of some doors or cost absurd figures.
Then I began to search through the Windows Server tools, but nothing.

It was essential that it was simple, clear and clean.
So, I made a website, where I can monitor their status!
Servers sends information every X minutes to my web server.

I used all microsoft tools, Powershell to read important information and report data to the website and task scheduler to execute it. (Alarms include Server Offline, Ws Backup fail, Hdd space low, High cpu usage, high ram usage, raid degraded, hyper v replication failed and others)

So I wondered…

Why not integrate this service in Windows Server 2016 rules?
I could share it with microsoft if microsoft wants....

Whilst working through some of the DNS records for our network, we noticed we were seeing some records from 2015. We tried to sort the 'Date' column in ascending/descending order and found that the fields were not formatted as 'Date/Time' but rather as a text format as the timestamps were sorted in ascending order of the first 2 numbers of the date.
As an example:
Timestamp 1: 05/04/2015
Timestamp 2: 01/02/2017
Timestamp 3: 15/03/2016
Timestamp 4: 19/06/2015

When sorted in ascending order by timestamp, the DNS records SHOULD be organised in the following format:
1: 05/04/2015
2: 19/06/2015
3: 15/03/2016
4: 01/02/2017

However, they are sorted thus:
1: 01/02/2017
2: 05/04/2015
3: 05/03/2016
4: 19/06/2015

We took a look at one of our 2008 servers and found this was the case there also.