The Desktop Experience for Non-Core Windows Server 2016, e.g. Standard/Datacenter, is no more a feature to add/remove.
Today a new update appeared in WU . It was KB3176495 (Cumulative Update for Windows Server 2016 for x64-based Systems (KB3176495)) . It's nice to see the OS build updated to 14393.51 .
i applied the cu hotfix ( .cab file applied using the DISM command ) that was posted in win 10 thread and my server 2016 datacentre x64 now at 14393.82 and running fine
I originally posted this under W10 Dedup thread but I guess it is also relevant here. I was testing WS2016 with larger-than supported files (1TB+) and I'm consistently seeing chunk store corruption. Can anyone confirm? My scenario is writing multi-TB files with pseudorandom data (about 1:50 dedup ratio) to test image-based backup. Pretty much all large files cannot be fully dedupped and Scrubbing shows chunk store corruption. WS2012R2 dedup works fine on same hardware, though throughput is slower. About 1TB+ files - this is semi-supported on WS2012R2, if you write files in one run and never modify them. WS2016 14393 patched to .82 (though there are no dedup component updates) HP EliteDesk 800 G1 with i5-4570 and 32GB RAM. 3* HGST UltraStar 6TB Striped storage spaces. (HDD passes SMART selftest and chkdsk /R)
Wait, a filesystem that has a "supported" limit but doesn't enforce that limit and corrupts instead? LOL!
The dedup is not a file-system, is something that runs on top of it, and given some kinds of files have the bad habit to grow, the enforcement cure could be even worse than the problem meant to be fixed. That's assuming the corruption faced by the user above is a direct consequence of the larger file.
I'm thinking that this is still a bug, as huge files used to work fine in previews and WS2012R2. There have been discussions in varius backup vendor forums. To enforce limits - WS2016 is supposed to skip 4TB+ files or skip data over 4TB (TPs used to skip files but RTM is supposed to dedup up to 4TB, WS2012R2 will go beyond that). Also it is suggested that 1TB+ files will be supported if they will not be modified after creation. Data corruption is a bug any way you look at it. I guess we'll have to wait and see, there have already been plenty of updates for server components in CUs.
That's possible but probably has nothing to do with large files them self Personally I faced a corruption on a couple of relatively large files (35 GB or so VHDs) while I'm sure that tp4 or tp5 fixed some corruptions on data coming from 2012 R2, that 2012 R2 was unable to correct (those errors were the result of few bad physical sectors) Back to the corrupted VHDs (still mountable but not copiable elsewhere) I can't tell a lot, given all of my other files were duplicated with the great drivepool, and possibly it fixed other eventual mess done by the deduplication. Whatever I'm moving back the data to 2012 R2, because a small incompatible driver. So my test with 2016's deduplication for now are on hold.
Just as an initial guideline for data backup and deduplication: no_short_urls_allowed/hfllkzr Please bear in mind the information handling system is still incipient. All the best.
In case of backup/archive scenario, I'd recommend MS DPM guidelines goo.gl/14VuGy It has some nice extra registry flags to modify behavior for specific scenarios.
Hi guys. I upgraded my hyper-v 2012r2 system that's running storage spaces tiering to 2016, and if i rightclick my powershell icon in my taskbar and choose to run the powershell.exe as admin, it won't let me. If i rightclick and tell it to launch powershell ISE as admin, it works. It also works if i run the powershell.exe as my normal account and not admin. Does anyone else have problems running powershell.exe as admin too? I'm wondering what/how that may be, because that cannot be right. I need my powershell, and it's clunky to have to use the ISE. Oh, and i chose to install 2016 with the desktop experience and the datacenter edition. Thank you!
go to Command Prompt(Admin) and then use the following command changing the path and filename to whatever you use DISM.exe /Online /Add-Package /PackagePath:c:\updates\windows10.0-kb1234567-x64.cab
As seen from the Microsoft website recently the RTM of this build will happen on August 23 2016, and a supplement update will be released end-September.
I'm using server 2016 for education and home storage. I notice that suspension it's not possible anymore. Anyone knows a workaround for it to work ?