Posts made by chetansays

@george1421

Can you show how to restrict for specific IP range please?

I have 2 more Vulnerabilities on FOG Server, can you please help on that as well.

@george1421

Results for showmount command

Export list for 127.0.0.1:
/images/dev *
/images *

Can i Close it and open it only when i need to upload the image to Fog server?

Server

• FOG Version: 1.3.4
• OS: 14.04 LTS

Need to close this vulnerability which was found while scanning Fog server and that is “Exported volume is publicly mountable” and it gives 6 instances on various ports.

Client

• Service Version:
• OS:

Description

@george1421 Sorry to ask this but how do i disable fog client through webgui just to isolate the issue.

Since yesterday when i updated fog to latest build, I am not able to successfully install windows on any new machines. I am getting error as seen in screensshot. It was working absolutely fine on same hardware before updating the fog to this latest build.

@Sebastian-Roth In compatibility test Network Adapter - fails. It is Lenovo M800 Model with Intel Ethernet Connection I219-LM (Jacksonville). I replaced newest kernel 4.5.0 but still same error. Unable to register host for the following reasons:

I replaced the bzImage file from 1.3.0 beta to 1.2.0 but still giving Unable to register host message… Is there something I am missing?

I am getting this error message on machines which are newer model (6th Gen Processors) while doing Full registration and inventory. After which it gives unable to register host error. I am getting this message for FOG 1.2.0 while it works perfectly fine for FOG 1.3.0 Beta.

@Sebastian-Roth Thank You Sebastian. Really appreciate all developers effort here. FOG is wonderful tool. I simply love it. You guys are extremely responsive as well.

@Tom-Elliott Thank You Tom… When you asked for that file information I cross checked with old version Fog file and I saw that “1” was missing and I edited the file. After which it worked like a magic. I just saw your post and you were spot on. Thank you once again.

@chetansays said: This is for d1.minimum.partitions while d1.fixed_size_partitions is blank

label-id: 0xc9acc7a0
device: /dev/sda
unit: sectors

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

@Tom-Elliott d1.minimum.partitions:

label: dos
label-id: 0xc9acc7a0
device: /dev/sda
unit: sectors

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

@Sebastian-Roth Content of d1.partitions

label: dos
label-id: 0xc9acc7a0
device: /dev/sda
unit: sectors

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

@moses Yes I always select Single Disk and Resizable option. Also my image size is maybe around 30 GB and my Target HDD is 256 GB but still giving error that Target HDD Boot Partition is smaller.

@george1421 But I never faced this issue in Fog 1.2.0. Is there anything which i need to make sure before pulling the image?

Fog Image created from Large size hard (for e.g 500 GB) does not get deployed on small size hard drive. I am using Fog 1.3.0 Beta build no. 6476.