Open 115-tpoe opened 2 years ago
I have a similar issue, but am only using Profile disks on my Server 2019 boxes. The same script works fine on profiles created by our Win10 VDI machines.
I wonder if there is something different about VHDs created by Server 2019?
I'm looking at the minimum size given by the disk itself. You can look manually by mounting any disk in disk manager and looking at the minimum size. If the current size is less than the minimum size I can't shrink it. This is to do with complicated NTFS partition reasons.
On Fri, 4 Mar 2022 at 15:53, Mikey-b941 @.***> wrote:
I have a similar issue, but am only using Profile disks on my Server 2019 boxes. The same script works fine on profiles created by our Win10 VDI machines.
I wonder if there is something different about VHDs created by Server 2019?
— Reply to this email directly, view it on GitHub https://github.com/FSLogix/Invoke-FslShrinkDisk/issues/55#issuecomment-1059283026, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE365OZAKH56DXZXKJKEGELU6IWWPANCNFSM5NIWW6VQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
We use the script for FSLogix Profile and O365 Container. Both are in the same directory and the script is started via task scheduler at night. Unfortunately, the O365 disk is from start on never handled, only the Profile disk. For each O365, even in test scenarios, "Skipped, already minimum" is displayed.
We have already checked and tested a few things, but still without success. Do you have any idea?
OS: Windows Server 2019 Used parameters:
C:\<Scriptpath>\Invoke-FslShrinkDisk-ps1' -Path <ContainerPath> -recurse -Logfilepath C:\<LogfilePath>\log.txt"
We also tried out the
-RatioFreeSpace 0
parameter, same issue