thanks guys, I know about adding flash from the adobe site, I am just confused that it appears flash is present but I cannot find any reference under control panel or anywhere else, also it appears the security update for flash installs but it does not actually change anything?!?! lol.............seems there is some policy or something blocking flash om my server 2016 datacenter Adobe-Flash-For-Windows-onecoreuap-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Yeah, one for IE, the other for Edge. As for icon under control panel of Server 2016... I never noticed it.
Adding the flash player from the adobe website "as usual" doesn't work, you need the full installers linked above. Package installed in the windows image and package installed and available are two different things. I'm not on w server atm but try to see if it's listed using the command Dism /online /Get-Features in case you see it Dism /online /Enable-Feature /FeatureName:Name_of_the__feature to install it
By the way, this 1610 VLSC Windows 10 edition is the very same as 1607 MSDN one: SW_DVD5_WIN_ENT_LTSB_2016_32BIT_xx-xx_MLF_X21-07420.ISO SW_DVD5_WIN_ENT_LTSB_2016_64BIT_xx-xx_MLF_X21-07421.ISO Anyway, Enterprise is always Volume with the GVLK package.
hmm, if thats the case, it appears flash packages are present on my system, but why does ms offer security update for flash player for SERVER 2016? hmm, just noticed that for KB 3202790 for server 2016, it says the following "The vulnerabilities discussed in this bulletin affect Windows Server 2016 Technical Preview 5" I wonder if they changed anything regarding flash between the tech preview and final code base?!?!
The question is "why the package is in the server image, if then is not installed?" But everything is in the image will is updated no matter if you have it installed or not, and is the right way. Assume you decide to enable the essentials role, it will start w/o old flaws since the minute zero. On pre-Vista system you had to install the feature from the install media, and obviously it was old, so you had to rerun windows update to get the latest updates for such feature. On XP you had smaller downloads, but you had to face minutes or maybe hours of services running on outdated binaries. The latest W10/Wserv2016 cumulative update is over 1GB and it's so big also because everything on the install image is updated.
I'm planning to install SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_English_-2_MLF_X21-22843.ISO soon, @abbodi1406 am I correct in assuming I can extract the OEM folder from your v10 KMS script to the sources folder of the media and it will be activated once installed, or did I read the ReadMe incorrectly? Thanks.
About the Hyper-V vs. SLAT issue mentioned some days ago: This is expected behavior. When you install Hyper-V, the host OS is moved into a VM also (the primary partition, or in Xen terms DOM0) and no longer resides on the hardware. Once this is done, you lose some of the hardware based features like SLAT (your OS is a VM and some CPU functions are not passed through)...also Hyper-V requires SLAT. You can get around this by creating another boot option and loading Windows without Hyper-V. Hyper-V in Server 2016 will allow nested virtualization, but there's no announced timeline when this will be released on the client Hyper-V. Reference: no_short_urls_allowed/pcud263
Yes, you are right. It may be the IoT EnterpriseS. I have that too. But I was talking about the VLSC and MSDN. Thanks anyway.
The WSL (Lxss) works with KB3200970 on Server 2016, but not EnterpriseS. Edit: It's this package that renews the components and hence disables it Package_3150_for_KB3200970~31bf3856ad364e35~amd64~~10.0.1.5