[DISCUSSION] Windows Server Build 16299

Thank you. It was solved.

 

Have you ever tried to port other Server Role or Feature than Dedup to Windows Client?

 

yea but never succeed

 

Which Role or Feature? I'd like to have it a go too. Thanks.

 

sry dont have good/another suggestion for feature that can be helpful

 

Server x86 can be achieved with Server x64 certificates on Windows 10 x86. And you may need PatchPae or modified ProductOptions for 64 Gb memory. No Server Roles/Features of course.

 

Terminal server is great feature to port

Btw does making 32 bit server core with win 10 32 bit is long time work compare to liting win 10 to similar form for ur opinion ?

 

server core 2016 is nearly all amd64 - remove most WOW64 packages and most Gui packages (You can comprare the packages between ServerCore and Server). What do you think?

 

You need to login to view this posts content.

 

Server 1709 is ACor edition, what to compare with?

 

Hello help my for
fr_windows_server_version_1709_updated_jan_2018_x64_dvd_100498124.iso
Link dead ?
thank

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

thank you

 

Is 14393 ServerHyperCore certificates compatible with ServerACor 16299?

 

Can I suggest a very interesting idea?
We don't have Terminal server in WS1709 (16299) as well as in WS1803 (final build expected in couple of weeks).
That is still quiet a well known fact, so kind of boring... But, as of Windows 10, version 1803 we have a new client SKU: ServerRDSH (winver reports as Windows 10 Remote Server).
Inside this SKU we have a role, called Remote Desktop Services Application Server

If I extract packages with SxSextract, I can get few quite interesting items:
Microsoft-Windows-TerminalServices-AppServer-Client-Package
Microsoft-Windows-TerminalServices-Collaboration-RelayTransport-Package
Microsoft-Windows-TerminalServices-CommandLineTools-Package
Microsoft-Windows-TerminalServices-MiscRedirection-Package
Microsoft-Windows-TerminalServices-MiscRedirection-WOW64-Package
Microsoft-Windows-TerminalServices-Publishing-WMIProvider-Package
Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package
Microsoft-Windows-TerminalServices-UsbRedirector-Package-amd64
Microsoft-Windows-TerminalServices-WMIProvider-Package-amd64
RemoteDesktopServices-Base-Package-amd64

I am quite interesting in porting that to WS1803. Assuming that someone would repeat the heroic trick to add GUI to ACor version for 1803, RDSH role would be quite valuable, as would allow me to publish RemoteApp for multiple users per one server, and in 1803 (ServerRDSH Client SKU at least) I can RemoteApp UWP apps (like Edge), which can't be achieved in WS2016 (aka 1607, 14393)

 

Win server have this feature it need to beenabled

 

Windows Server 1709 and 1803 are Core only, they don't have RDSH role, which is available only in full WS2016. But which can't do magic with Edge and UWP apps