DISCUSSION: Windows Server 2016 14393 (1607)

You need to login to view this posts content.

 

From 1607 (OS Build 14393.67) to 1607 (OS Build 14393.51)

Spoiler

And if i want to have Version 1607 (OS Build 14393.51), all i have to do, is uninstall update windows10.0-kb3176931-x64_d28f260835859577040c854819902c66a3172d79, Restart pc, then update to Version 1607 (OS Build 14393.51) from windows updates.

 

You need to login to view this posts content.

 

No, it is for N only.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Ive been running Srv2016 for a while now with no stability issues that Ive noticed, but I have been trying to make something happen. I am running it as a desktop OS basically, and tossing a ton of programs to it, and have done a lot of heavy secpol, gpedit changes. Crossing fingers

 

It works perfectly on server 2016

 

@xinso

How do we extract these packages?

Mounting the install.wim file from Windows 10 Enterprise and searching e.g. for "Microsoft-Windows-Media-Format-Package"
reveals for example:

But I guess we neither need .mum nor .cat files...

 

Yes, it is exactly those .mum.

For more detailed infomation, please go to Aunty Mel's Cheap And Nasty SxS Package Extractor.

 

some1 tried to install classic shell on server 2016 core ?

 

I failed to convert Pro to ServerDatacenter hours ago. It does not accept key of Pro or ServerDatacenter, and ask me to search help for this error: slui.exe 0x2a 0x80070426.

But it is working fine without BOSD - except missing Settings and ServerManager.

 

Obviously.

Who minds to use the ugly stock one?

 

@xinso

Thanks for the detailed information about how to extract these packages! Any reason you removed that part afterwards?

I extracted all packages (x64) via your script from the en_windows_10_enterprise_version_1607_updated_jul_2016_x64_dvd_9054264.iso
image and tried to apply them to an installed 14393.0.160715-1616.RS1_RELEASE_SERVER_OEMRET_X64FRE_EN-US.iso (Server 2016 DataCenter)

Unfortunately I get some errors while doing this:

 

1. The base package must be installed before its language pack.

You can put all language packs in another folder like MUI.:

Code:

Dism /Online /Add-Package /Packagepath:"x:\temp\x64"

Dism /Online /Add-Package /Packagepath:"x:\temp\x64\MUI"

2. Microsoft-Media-Foundation-Package is for Windows 10 . Server has its own package - Microsoft-Media-Foundation-Server-Package.

Code:

Microsoft-Media-Foundation-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Microsoft-Media-Foundation-Server-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0

Microsoft-Media-Foundation-Server-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Microsoft-Media-Foundation-Server-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0

You can only install sub-packages which are absent for Server by comparing the sub-package .mums of extracted Media-Foundation-Package for both Windows 10 and Server.

For example: For those Codecs files, people talked about in previous posts, which are being absent for Server.

Code:

Microsoft-Windows-Multimedia-RestrictedCodecs-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum
Microsoft-Windows-Multimedia-RestrictedCodecs-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.mum

Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum

And for more accuracy, you can check further for sub-package of this package.

Well, I am not good at Codecs. This is the best I can do for now.

 

I have been Playing around with Windows Server 2016 activation, and i have been able to activate it to Windows 10 Pro, activated wth a digital license.

USING:

Code:

digital license, which was obtained by using / Windows 7 Pro / Windows Loader by DAZ / gatherosstate (GenuineTicket) / Windows 10 Pro - method.

Folders an File needed from Windows 10 Pro, to activate Windows Server 2016:

Code:

Branding
Licenses
Professional.xml

spp            (activated with digital license)

Product key,   (installed by Windows 10 Pro) which i backup using ProduKey

 

Most server features are tied with product policy, which is defined by activation key

 

This is why you would keep the Windows Server 2016 OS folders and File, which have been renamed.

Code:

BrandingSER
LicensesSER
ServerDataCenterSER.xml
sppSER ACTIVATED with SppExtComObjPatcher-kms

Then when and if, you want to use Windows Server 2016 side of the OS, use a cmd/script file to rename folders and file back to

Code:

Branding
Licenses
ServerDataCenter.xml
spp

and to install Windows Server 2016 key for activation.

NOTES:
This is a simple explanation on how you would use Windows Server 2016 side of the OS, but you get the idea.

The good thing about activation, is it can be Windows 10 Pro OR Windows Server 2016.

Code:

IF YOU KEEP THE NEEDED ACTIVATED SPP FOLDERS

 

OK