I can't offer any advice on your upgrade problem as I have not experienced anything like it. As for an uninstallation script, it is not necessary. Once the deduplication package is installed, it appears in Control Panel > Programs and Features > Turn Windows features on or off > File Server Role > Data Deduplication where it can be deselected or you can do it from command prompt... Code: dism /online /disable-feature /featurename:Dedup-Core And if you REALLY want to actually uninstall it... Open and elevated Command Prompt and enter the following commands one at a time. Code: dism /online /remove-package /packagepath:Microsoft-Windows-VdsInterop-Package-amd64-10.0.18362.1.cab /packagepath:Microsoft-Windows-VdsInterop-Package-amd64-10.0.18362.1-en-US.cab dism /online /remove-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.18362.1.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package-amd64-10.0.18362.1-en-US.cab dism /online /remove-package /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package-amd64-10.0.18362.1.cab /packagepath:Microsoft-Windows-Dedup-ChunkLibrary-Package-amd64-10.0.18362.1-en-US.cab dism /online /remove-package /packagepath:Microsoft-Windows-Dedup-Package-amd64-10.0.18362.1.cab /packagepath:Microsoft-Windows-Dedup-Package-amd64-10.0.18362.1-en-US.cab
Let me rephrase it Microsoft-Windows-FileServer-ServerCore-Package is just a wrapper, when you extract it, it will contain two packages: Microsoft-Windows-FileServer-Core-Package Microsoft-Windows-VdsInterop-Package previously (10586 and earlier including Win 8.1/8.0), Microsoft-Windows-VdsInterop-Package was included with Microsoft-Windows-FileServer-Package
Yup I just extracted it. So I guess the 18362.1 pack that I made and shared here doesn't need the VdsInterop and ChunkLibrary cab files I included. I'm going to install in a VM and verify that the ChunkLibrary is indeed included and that the FileServer-ServerCore and Dedup packages are the only ones required to get data deduplication functioning and if so, even though no harm is done by installing the 4 cabs, I'll reupload my pack with updated installation instructions and add uninstallation instructions. I only added those 4 packages because I had asked for information on extracting them a few times and the only person who responded listed those 4 packages. I assume because whoever made the 17763.1 pack included them. Thanks for the information, bro!
anyone have instructions for pulling the required cab files from the Windows Server 2019 1909 build ISO?
You don't need to as the 18362.1 package I provided works for all 1903/1909 builds. And more specifically, Server 1909 builds contain 18362.1 dedup files as 1909 is a fake build created so MS didn't fall behind the bi-annual release cycle of the SAC.
So in my testing I used dedup on 300Gb data drive with quick turnaround of files on Win 10 1809 While it worked, it actually eat much more space than it saved. After less than a year, I got 14Gb free on that drive. Copied data elsewhere, formatted drive, disabled dedup on it, copied data back, 230Gb free (that means that there was over 200Gb of de-dup data itself being used) It works great on server file volume (where many users will likely have same/similar data), for for 1 user local data I do not think it makes much sense (unless that is stale data, rarely replaced)
Yes it works best for archival sets of ISO's, VM's and other large files that don't change much. It also seems to work very well for mp3 files. Though that kind of disturbs me as I like to think that I have varied taste in music that is reflected in my collection, yet 25+GB of mp3 files gets deduplicated to 44KB on disk!
First any server variant has to be released for the build, as the Deduplication packages are extracted from these.
The last server build was 19035, so no there isn't any dedup packages for later insider releases. If you really want to or need to use Data Deduplication, you will have to drop down to 1903/1909. I for one won't bother extracting any dedup packages until Windows Server 20H1 is in release parity with client editions.
Hey, I appreciate the info. Most of it has been stated in some form or another over the course of this thread. Which I have read the entirety of. Your post came across as crass and sarcastic, which my friend is simply not the way we do things on MDL. I suspect that much of the reasons for mp3's getting almost entirely stored in the chunkstore has much to do with the very same reasons behind them not compressing in archives. They are already solidly compressed. My surprise came from a personal thought process that was in retrospect, illogical. Again, welcome to the forums. Drop the holier than thou attitude and convey whatever information you chose to in a polite manner and you'll get along fine here.
Thanks as always for keeping this updated. Finally bit the bullet and updated Win10 to 1909 from 1803 (or whatever ungodly build I was on from nearly 2years ago). Glad I can get dedupe running again right away.