Hello, Everyone.

Here comes the update

I tried to restart the tftp whcih @Tom Elliott mentioned below.
I did edit my dhcp config just the exactly the same as @Wayne-Workman 's reply below.
And I also add one more line refer from @Uncle-Frank 's reply below.

I tried those methods separately, but didn’t work out well.

However, when I combine those methods together. Fog server finally run and I can upload and download images to the machine now.

Thank you everyone who contributes in this post.

Note: there is a login fail problem with this particular setting. To resolve this issue, change your password through the database to modify your password.

Thank you for quickly reply. I realize how the fog server works now.

But I still have some questions.

Without using the resizeable option, is Fog server still able to deploy Windows 10 to a smaller hard drive?

For example, if I make a clone A from client A is 500 GB hard drive with Windows 10 operating system, and I select the non-resizeable option. Can I still use clone A to deploy another client B with 250 GB hard drive?

@Sebastian-Roth

Is there anyway to get working around with this problem?

I do not want to waste the space on the hard drive.

Thank you

Hello, Everyone
Here is some of my system’s background

Client computer:
HP EliteBook Laptop with Window 7 64bit (Works)
DELL Vostro 3540 Laptop with Windows 10 64 bit (Failed)
Fog Server computer:
Desktop with Ubuntu 14.04
Fog Server version: 1.2.0

I recently sucessfully upload and download the Windows 7 from the client without any problems.

I got another client run Windows 10 and I did a little bit search on forum that Fog1.2.0 is able to deploy Windows 10 with option of Windows 7.

However, I only got those 275MB in the server and those files in the /images

Is there anyone know what is that ?

Note: This problem exist with my Windows 7 client before, but an reinstall fix it. Win10_Test is the file I upload from the client,
Please ignore Think_Image.

Let me know if I need to provide any other information.

Thank you.

Hi,

Sorry about the late reply.

I resolve the problem by reinstall the fog server as my supervisor impose my computer for emergency usage so he wipe out all the drives.

I will try to test other method and if I have further questions I will post on the forum.

Thank you everyone.

There is no error, however it seems that the fog server only deploy the “system reserve partition” (275MB) to the new drive without the entire Windows 7.

True. I should double check my later one. It’s only 250 GB and my original one is 400GB.

Is there anyway to overcome it? I tried the resizeable option, however the fog server only make the image of System Reserve (around 275MB) from my client computer

Thank you @Uncle-Frank and @Hanz .

Sorry about the misunderstanding @Uncle-Frank , I reboot my laptop again and get in to the debug mode and type in the command

fogpartinfo --list-parts /dev/sda

All I got is this message

Error: Can't have a partition outside the disk!

Hi, @Uncle-Frank . Here is what I got from the client computer after I deploy a debug task from my fog server.

After I run the commnad fogpartinfo

Thank you everyone,

Sorry about the confusion. I upload the client’s image first on to the fog server and pull out the original hard drive from the laptop then puts a formatted new empty disk into it.
@Uncle-Frank Thank you for your explanation.

I have those files in the /images/HPEliteBookGFLAP84

and here is my d1.mbr file

d1.mbr

Sorry, I should state clear
Here is my background info

Client computer:
HP EliteBook Laptop with Window 7 64bit
Fog Server computer:
Desktop with Ubuntu 14.04
Fog Server version: 1.2.0

The “BOOTMGR is missing” message display after I finish download the windows 7 image and reboot my client computer.
Those are the steps that I went through

1. create task at Fog GUI to deploy the window 7 image to the client computer. (Around 15 GB on the server)

2. restart client computer to get into network boot

3. Client computer get into normal process

4. Then the client shut down itself. It didn’t continute to process any further

5. I reboot the client computer, then the error message pops out