Search This Blog

Friday, November 25, 2016

Windows Server 2016 will have different features in Standard and Datacenter editions

Windows Server 2012 R2 had the same feature set for Standard and Datacenter editions, the only difference was how many OS instances each edition allowed to run.

Windows Server 2016 is different - Standard and Datacenter don't have the same feature set. Check this link 

In which branch is Windows Server 2016 - current branch or LTSB?

There are many articles which describe update branches for Windows 10, but that's not the same for Windows Server 2016. I have heard a lot of people asking if Windows Server 2016 will have the same branch configuration as Windows 10.
So here is the answer - "Windows Server 2016 with Desktop Experience" and "Windows Server 2016 Core" will work as LTSB, that is the same way as previous Windows Server editions have worked.
But "Windows Server 2016 Nano Server" will work in current branch, that is it will receive full updates each 6 months or so.

"Available updates will be downloaded and installed automatically" in Windows Server 2016

If you check for updates in Windows Server 2016, then it always shows that "Available updates will be downloaded and installed automatically, except over metered connections (where charges may apply)."

If you change update behavior as described here, then it still shows the same.

Microsoft says that it is interface bug and it will be fixed in future releases.

Monday, November 21, 2016

Updated: How to change Windows Update behavior in Windows Server 2016

Previously I wrote about Windows Update behavior in Windows Server 2016.
So at this point there is no way to change Windows Update behavior from GUI in Windows Server 2016 and the default value is "Download Updates only".

To change this:
1. Open Command Prompt.
2. Type sconfig
3. Select 5, to configure Windows Update

4. Select on of three options - Manual (which never checks for updates), DownloadOnly (which is default and only downloads updates), Automatic (which downloads and installs updates automatically)

Force SCCM 1610 update to appear in console

If the SCCM 1606 update does not appear in console, then use this script and follow these steps:
1. Extract .ps1 file frrom downloaded .exe.
2. Run .ps1 with Powershell on SCCM Site server
3. Check for updates in SCCM console

Saturday, November 19, 2016

Configure Windows 10 Start Menu with group policies

Since Windows 10 v1607 there are group policies to configure Windows 10 Start Menu and there is no science there (, it's a four step process:
1. Configure Start Menu as you wish.
2. Export it to .xml file using Export-StartLayout Powersehll cmdlet.
3. Copy it on a share where users can read it.
4. Configure this group policy User Configuration / Computer Configuration > Administrative Templates > Start Menu and Taskbar > Start Layout

The thing to note is that at this point group policy works only in Windows 10 v1607 and in Enterprise and Education versions.

WSUS doesn't synchronize after reinstalling on SCCM sever and causes 100% CPU

I have had several times when it was necessary to reinstall WSUS on a SCCM server, you can do it and it is not a very complicated process. But the last time I did it - on a Windows Server 2012 R2 box and SCCM 1606 after reinstalling WSUS did initial sync and then failed.
In addition to it I saw 100% CPU usage for 10-15 minutes and then it stopped, also causing WSUS service to stop.
The problem for this is that WSUS initially has lots of request to process and lacks resources. So you have to configure WSUSPool application pool to have enough resources. Follow these steps:

1. Open IIS Manager;
2. Go to Application Pools, select WSUSPool
3. Select Advanced settings
4. Modify these values to
Queue Length = 3000
Private Memory Limits = 7843200 or 0 (which means there is no limit)

Windows 10 v1607 capture with SCCM fails with error code 0x00004005

I have been doing OS captures with SCCM created capture CD for ages and it always has been an error prone process, but that's not true with Windows 10.

In this situation there was necessary to create additional local user account in the captured image, which was the problematic part in the end.
I did everything as usual - prepared the image, inserted capture CD and let the process capture the WIM image. But syspreping the image failed with error 0x00004005.
Further digging into c:\System32\Sysprep\Panther\setuperr.log revealed error 0x80073cf2 and error message that some modern apps like Twitter, Candy Crush, BingNews "was installed for a user, but not provisioned for all users".

At first I tried to remove these apps, but there always appeared new appp which was installed for a user, but not provisioned for all users". I didn't want to remove all apps. So after little bit of playing around I was able to avoid the error when doing capture with built-in administrator account and deleting all other user profiles before capture.

Friday, November 18, 2016

Ste-by-step: Move virtual machine from local disks to highly available Hyper-V cluster

By accident someone had created a virtual machine on server local disks, not on Cluster Shared Volume (CSV). So this VM was not highly available, but had to be.
Process to make VM highly available actually was not so difficult and consisted of to steps:

1. Move VM files to CSV disk. To do this open Hyper-V Manager, right-click VM, select Move, in the Wizard select to move virtual machine storage

then select to move all VM files:

For the new destination specify the Cluster Shard Volume.

2. From the Failover Cluster Manager console right-click Roles, select Configure Role. For the role type select "Virtual Machine":

In the next step you will be able to see the VM that is not yet higly available. Finish the Wizard and VM will be higly available. That's it!

The only thing to note is that for Windows Server 2012 Hyper-V cluster the VM can be online, but for Windows Server 2008 R2 clusters the VM must be offline.

Wednesday, November 16, 2016

Windows 10 Feature update installation fails with error 0x80240020 when using SCCM servicing

Finally I had a chance to test out Windows 10 Servicing in SCCM, so everything was set up and on my Windows 10 v1511 machine I had deployed an upgrade to Windows 10 v1607, but it failed with error code 0x80240020. Event log wrote 0x80240022 error.
Anyway, I resolved this by deleting all the files in C:\Windows\SoftwareDistribution\Download directory. After this I was able to successfully update Windows 10 to v1607.

Windows Update logging has been moved to Event Viewer in Windows 10 v1607

In previous Windows versions if you had problems with Windows Update, the first place to look for detailed information was C:\Windows\WindowsUpdate.log file.
In Windows 10 v1607 WindowsUpdate.log file doesn't log any information, instead logging has been moved to System log in Event Viewer.

WindowsUpdate.log now says:

Windows Update logs are now generated using ETW (Event Tracing for Windows).
Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.

For more information, please visit

Tuesday, November 15, 2016

SCOM 2012 R2 Agent push fails with Error Code: 80004021

If  you are pushing SCOM 2012 R2 agent and it fails with error code 80004021 and error description is "The operation attempted is not supported"

Then one of the possible causes for this is that there is already SCOM agent on the server. In my cause there was Operations Management Suite (OMS) agent, which was installed for testing purposes.
To solve the error uninstall OMS agent.

Monday, November 14, 2016

SOLVED: Windows 10 v1607 LTSB does not activate from KMS server

If you are using Windows 10 v1607 LTSB and they do not activate against your KMS server even if Windows 10 v1511 are successfully activating, then you have to:

  1. Install Windows 10 v1607 KMS key on KMS server;
  2. Apply hotfix KB3172614