Posts made by Derek Newbold

Hi Sebastian,

Thankyou for your prompt reply, and for helping with this problem. Sorry about the delay in getting back to you, I’m from Australia so there is probably some time difference!

I have gathered all the information you have asked for and attached it to this post except for screenshots of capturing the image. Please let me know if you can see anything from this information or whether you need me to recapture my image again to take some screenshots of the capture process.

I have also checked that the image is set to resizable and OS ID is set to Windows 7 (as you can see in my screenshot). I assume this is all correct?

administrator@NHS-FOG-01:/images$ ls -al /images/ADOBEIMAGEWIN7
total 79658372
drwxrwxrwx  2 root root        4096 Jul 21 22:28 .
drwxrwxrwx 16 fog  root        4096 Jul 21 22:28 ..
-rwxrwxrwx  1 root root           5 Jul 21 21:56 d1.fixed_size_partitions
-rwxrwxrwx  1 root root     1048576 Jul 21 21:56 d1.mbr
-rwxrwxrwx  1 root root         190 Jul 21 21:56 d1.minimum.partitions
-rwxrwxrwx  1 root root          15 Jul 21 21:56 d1.original.fstypes
-rwxrwxrwx  1 root root           0 Jul 21 21:56 d1.original.swapuuids
-rwxrwxrwx  1 root root    25477300 Jul 21 21:56 d1p1.img
-rwxrwxrwx  1 root root 81543607445 Jul 21 22:28 d1p2.img
-rwxrwxrwx  1 root root         190 Jul 21 21:56 d1.partitions


administrator@NHS-FOG-01:/images$ cat /images/ADOBEIMAGEWIN7/d1.fixed_size_partitions
:1:2


administrator@NHS-FOG-01:/images$ cat /images/ADOBEIMAGEWIN7/d1.partitions
label: dos
label-id: 0xf8268334
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=      204800, type=7, bootable
/dev/sda2 : start=      206848, size=   204800000, type=7


administrator@NHS-FOG-01:/images$ cat /images/ADOBEIMAGEWIN7/d1.minimum.partitions
label: dos
label-id: 0xf8268334
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=      204800, type=7, bootable
/dev/sda2 : start=      206848, size=   204800000, type=7


administrator@NHS-FOG-01:/images$ cat /images/ADOBEIMAGEWIN7/d1.original.fstypes
/dev/sda2 ntfs

Server

• FOG Version: 1.4.3 SVN Revision 6075
• OS: Ubuntu 16.04

Client

• Service Version: 0.11.12
• OS: Windows 7 Enterprise Service Pack 1 64bit

Description

I have recently upgraded our FOG from 1.2.0 to 1.4.3 and also updated the client on my Windows 7 image. My image from before the upgrade was set to ‘Single Disk - Resizable’ and when capturing the image it used to resize the main partition (C:) to as small as possible, and then when deployed it would resize it again to use all the space on the destination host.

Now since the upgrade I tried to deploy the image to a computer that had a smaller hard drive (128GB) than what I had set on the VM that I created the image on (140GB capacity, approx 80GB used). The imaging failed basically saying that the destination host drive wasn’t large enough, however it was never a problem before due to FOG resizing/shrinking the C:\ parition before capturing it.

So as a test I shrunk the partition in Windows to about 100GB and recaptured the image. The image now deploys to the computer with the 128GB drive however it is not resizing the C:\ partition (or any other partition) to use up any free space on the drive.

I hope this all makes sense, does anyone have any suggestions on what is causing this behavior and how to fix it?

Thankyou in anticipation!

[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]Hi,[/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]We have been using FOG installed on Ubuntu to image computers and have now started creating an image as a Hyper-V virtual machine (an image created as a virtual machine was a recommendation to us, and we are running Hyper-V hosts so we created it as a Hyper-V virtual).[/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]We are having trouble getting the kernel that FOG is using to read the hard drive of the virtual (and it won’t pass the Disk check of FOG’s Compatibility test), so we assume that the drivers in the kernel don’t support what the Hyper-V virtual uses.[/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]We have now tried to compile a new kernel (3.10) using the .Config file that FOG supplies and the command ‘sudo make xconfig’ which brings up a Kernel Configurator, but where it says ‘Microsoft Hyper-V guest support’ there is no tickbox next to it to include it in the kernel? Have tried ticking ‘Virtualization Drivers’ and ‘Virtualization’, and then compiled the kernel, but it hasn’t seemed to fix our problem. We are trying to do this on an installation of Ubuntu 12.04.[/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]Does anyone know how to include Hyper-V support in the kernel, and whether or not it will actually be a solution for our problem? Any other ideas?[/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]Please bare in mind, we do not know much about Linux/Unix operating systems and have never compiled a kernel before.[/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]Thankyou for any help![/SIZE][/COLOR][/FONT]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]-Derek[/SIZE][/COLOR][/FONT]