FOG Not resizing partition Windows 10 v1909

[Derek Newbold]

@Boyan-Biandov I forgot to ask in my last post, what does your partition table look like in your image that you use your script on? I see you have it set to resize partition 2.

We have 3 partitions (although the FOG partition information files lists 4 hmm) and it’s the 3rd partition that needs resizing.

Would we need to change the script to 3 or does the numbering start at 0 so 2=3rd partition?

[Sebastian Roth]

@Derek-Newbold said in FOG Not resizing partition Windows 10 v1909:

We have 3 partitions (although the FOG partition information files lists 4 hmm) and it’s the 3rd partition that needs resizing.
Would we need to change the script to 3 or does the numbering start at 0 so 2=3rd partition?

I might comment on this quickly so you don’t get this wrong. You actually have four (4!) partitions on your drive. You only see three because Windows disk management console is hiding one of them (I think it’s probably sda3 in your case). I am not exactly sure if powershell actually sees 3 or 4 partitions in your case. You might want to open a powershell window as Admin and run Get-Partition first to get a list of all partitions on all disks. It also prints the size of each partition and with that you should be able to find the right one to resize.

Now back to why FOG doesn’t expand to full size for you in the first place. From the partition listings you posted it looks all fine to me. So there is no obvious reason I think. Your inits/setup being one and a half year old might cause this issue. There have been a lot of fixes and changes in the inits since then. While chances are high this is fixed in the latest already I can’t promise you anything. What I can say for sure is that we won’t backport any fix to 1.5.4 so if you want to see this fixed you need to update.

Not exactly sure but you should be able to just use the latest inits and kernels to run with your 1.5.4 install. There are a few things to consider. If you are keen to give it a try, let us know.

[sudburr]

For a sysprep solution look here.

<extendospartition>
	<extend>true</extend>
</extendospartition>

[Boyan Biandov]

@Derek-Newbold You’re correct, the ps1 is called from C:\Windows\Setup\Scripts\SetupComplete.cmd but since it is a power shell script it can not be pasted into the bat file, so I use powershell.exe -executionpolicy bypass -file “C:\Windows\Setup\Scripts\expandhdd.ps1”

As for partition numbers, this was a trial and error process, the disk only has 2 partitions, windows reserved and the OS so that is how it came about.

I do agree that if your OOBE bombs out due to disk space issues then my suggestion won’t work, the HDD expansion happens downstream

[Derek Newbold]

@Sebastian-Roth @sudburr @Boyan-Biandov

Thanks everyone! We’ve changed our image capture to a fixed disk size now and we already happened to have the <extendpartition> bit in the unattended.xml file. This arrangement is now working for us and the partition has been automatically extended on our test machine.

We don’t really need the ‘Single Disk-Resizable’ if we can get the partition to extend in another way. Our VM that we capture is set to 100GB and all our destination computers have SDD drives larger than that.

I will look into updating FOG when I get some time to focus on it properly. Unfortunately for us we have difficulty updating/installing FOG through our Departments internet filtering/firewall which we don’t have full access too. I could connect it up to a direct internet connection, but that could involve a different IP address being required. I was told FOG doesn’t really like the server having it’s IP address changed, so I wasn’t sure if I should attempt to do that or not.

[Sebastian Roth]

@Derek-Newbold said in FOG Not resizing partition Windows 10 v1909:

I was told FOG doesn’t really like the server having it’s IP address changed, so I wasn’t sure if I should attempt to do that or not.

While it’s not as trivial as change the Linux IP settings and ready set go it can still be done and we have documentation on that: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

[Derek Newbold]

@Sebastian-Roth in that guide one of the first steps is to re-run the installer after changing the IP address of the OS and in the /opt/fog/.fogsettings file.

My problem is that once I change the IP address and network connection back to what we normally run FOG under, I lose my direct (unfiltered/firewalled) internet access, so I’m back to not being able to run the installer. Is there any way around that?

Sorry this post is probably going a bit off-topic now.

[Sebastian Roth]

@Derek-Newbold said in FOG Not resizing partition Windows 10 v1909:

Sorry this post is probably going a bit off-topic now.

Yeah, we should probably open a new topic on this? Will you? We also have a community script that does the IP change for you: https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

Though this is not well maintained and I can’t promise you anything right now. But we can work on this if you would like to assist with testing and report here in the forums.

[Derek Newbold]

@Sebastian-Roth thankyou! I’ll open another topic if need be when I get a chance to look at upgrading FOG.

[Boyan Biandov]

@Derek-Newbold FYI I have seen ton of people running FOG in AWS with totally public IP and that works outside of any firewall issues, of course those instances involve people who have access to the local sites DHCP so they can update the tftp option in their scopes with the public IP

In my case it’s a private IP but I do have access to the networking side of things so sites throughout the organization can boot fine from HQ FOG server.