Haven't run into this myself (yet) -- interesting thign to mention.
I'd (naively?) assume that any "normal" disk/partition extension job should work ... no? (something to try on a VM / Lab machien you don't mind breakign a few times) .
I did wonder whether the 100 MB may be a bit on the low side.
1 of 1 people found this helpful
We ran into the same issue and through research we found an article that showed how to mount the partition and remove unneeded files.
We created the following bat file that can be pushed through LANDesk that will show the free space available on the partition before deletion, then it deletes the fonts and boot files for other languages, and then it runs the check for free space after. Both files are copied to the local C drive, named start.txt and end.txt. In future I will have it write the free space to the registry so I can see it in Custom Data, but for now it does the job.
Once run, the Windows 1703 edition can be successfully installed. We do have Kaspersky AV and have not seen any files from it on that partition, it appears it is just Microsoft install files.
The specifics of the bat file are listed below, feel free to use and modify.
Mountvol Y: /s
fsutil volume diskfree y:>c:\start.txt
rmdir cs-cz /s /q
rmdir da-dk /s /q
rmdir de-de /s /q
rmdir el-gr /s /q
rmdir es-es /s /q
rmdir fi-fi /s /q
rmdir fr-FT /s /q
rmdir fr-fr /s /q
rmdir hu-hu /s /q
rmdir it-it /s /q
rmdir ja-jp /s /q
rmdir ko-kr /s /q
rmdir nb-no /s /q
rmdir nl-nl /s /q
rmdir pl-pl /s /q
rmdir qps-ploc /s /q
rmdir ru-ru /s /q
rmdir sr-latn-cs /s /q
rmdir sv-se /s /q
rmdir tr-tr /s /q
rmdir zh-ch /s /q
rmdir zh-cn /s /q
rmdir zh-hk /s /q
rmdir zh-tw /s /q
fsutil volume diskfree y:>c:\end.txt
Thanks for that -- appreciate it .
This is a great work around. I did notice that Windows 10 installer will size the System Reserved partition at 500 MB when creating all new partitions on the hard drive.
Is there a way to do this in LANDesk provisioning?
Thanks for all your help.
Just run the actions, either as a package or "1 at a time" as commands during Provisioning.
So yes, you "can" do it. Where / how you chose to do so, up to you & personal preference.
Hi phoffmann, I'm struggling to partition a drive how I want it with a bigger system partition and still have the Deploy Image action work. Would you please be able to take screenshots of how it should be to be successful?
I've even tried mapping a drive and running a diskpart script (a recommended sample for W10 from Microsoft), which seems to create the partitions correctly, however the Deploy Image fails
I've also tried to create the partitions using separate iVanti steps, but it fails to create the Windows partition. I'm not sure what to put in into the size and offset for the primary partition, so I guess that's why this step is failing?
Changed the mount drive letter to W (from C), but no difference
Hmm - should work, and there's nothing leaping out at me as obviously wrong.
Try a fresh template, with just these actions against a VM. *Ideally* you should see the same behaviour here. If so, you can raise this as a support ticket & then dev can look into what's going wrong.
If it works fine on a VM, try it on different hardware ... could be a hardware specific issue potentially.
I just heard this was a known issue back is LDMS2016 and is still a known unresolved issue (we're on 2017.1 SU1), so it's a bit surprising, based on the fact you need a messy workaround to get a W10 feature update to install that it hasn't been addressed yet as a priority. Most people wouldn't even know of the workaround so they basically wouldn't be able to deploy Windows 10 without a giant problem when they come to install their first feature update.
We were able to get this working with the a diskpart script stored in \\core\ldlogon named UEFIDiskPart.txt with the following details and the following actions -
create partition efi size=500
format fs=fat32 quick label=System
create partition msr size=128
create partition primary
format fs=ntfs quick label=Windows