Posts made by maxcarpone

@george1421 Ok, I was curious to see the newest version but no problem, we will switch back to dev-branch.

Thanks.

Hi guys!

We are trying FOG 1.6 and we are facing our first problem which is we can’t register our host. It tells us : “Unsafe Hostname entered, please try again : ZHdzCg==”

What can we do to register our host properly?

I must add we can register our host with the desired name using the web interface.

Thanks for your help.

Max

PS : FOG Version : 1.6.0-alpha.1159

Hi,

Everything’s fine after updating our FOG. Thank you guys.

Morning,

Have you tried to update kernels of your FOG Server guys? To do so, you click on “Fog Configuration” then “DefaultMember FOG Version” to display both running kernels (mines are 5.15.19 for example).

Then you click on Kernel Update in left panel. You pick those 5.xx.xx kernels Intel 64 Bits and Intel 32 Bits and download them to start the installation process.

You probably need a 5.xx kernel and don’t have it installed.

Let us know if it works

Good afternoon,

Sorry, I didn’t see your topic before but after looking at it, it looks like you’re right, we’re facing the same problem.
I also found this issue here : https://github.com/FOGProject/fogproject/issues/467 which is the same as well.

Let’s wait for a fix now. Cheerio

Hello,

I updated my FOG 1.5.9.113 with the last dev-branch version and since then, my snapin is queued. I try recreating it but it doesn’t work either.

On client side, the fog.log says “response no snapins”.

Any idea how to solve this?

Thanks.

Yes, this is true, I could do that but it won’t change anything the way the “Image Managament” page looks. I was thinking about the ability to browse through folders and display the content rather than displaying all the images. (I know there is the searching field but it’s not exactly the same)
We could imagine a tree on the left side of the panel and browse through categories like an explorer if you prefer.

Well, that was just an idea and the way it works at the moment suits my needs but I thought it could bring a little something.

Cheers.

Hey guys,

We don’t say it very often or perhaps we do but I’d like to thank you very much once again for FOG because it’s so useful! We love it

Yesterday, I was cleaning our server because we had a lot of old images and I suddenly realized there was a missing feature which could help us to tidy images up.
We could create categories and sub categories to classify images. For example, I could create a “Windows 10” folder and inside it another folder named “1903” and another “20H2”
Then, when I would like to clean old images, I could remove the whole 1903 folder.

Thanks for thinking about it!

Best regards from France

Max

I’ve just found out that the management password of my storage node has been truncated by 1 character. After typing it again, everything is back to normal.
That version has definitely changed my password

Well I’m not sure my problem is related to the one described above, sorry for that.

Hi guys,

Same problem with my server, I’ve just updated from 1.5.7.2 to 1.5.7.4 and snapins are not deployed anymore. It failed with return code “-1”.

Hey guys!

It looks like it works so far. I tested with 2 fresh installations of W10 1803, one in MBR and the other one in UEFI and each capture has its own d1.fixed_size_partitions populated.

Content of these files :

• MBR => :1
  which is the partition labeled : Réservé au système

• UEFI => :2:3:1
  Which are Recover, System, MSR

I will do more experiments soon but I like what I saw ^^

Thanks for the good work

@Sebastian-Roth Ok, I’ll be happy to try those new inits

I did not really understand what was going on here… Have you made some progress?

@Quazz Here it is.

@Quazz Here is a screenshot of my image settings

I asked my colleagues to see if they had the same problem and some have that problem with empty file and some don’t.
For example, in another college, their W10 images have :1:3 in d1.fixed_size_partitions but not their W7 images!

I don’t understand because we installed things the same way and we built our FOG server the same way too!

@Sebastian-Roth I won’t be surprised because all the files d1.fixed_size_partitions I have are empty and I’m using FOG since 1.2 (before moving to trunk version).

@Sebastian-Roth Well, d1.fixed_size_partitions is still empty with the new init provided

@Sebastian-Roth Hey, I created a new image so there is no possible mistake.

I’m ok for testing more things, I just need more explanations.
If I understand well, I must log on the server and go to /var/www/html/fog/service/ipxe and download 67init.xz then go to the “TFTP server” settings and change the pxe boot image? Or do I need to execute something on the client side in debug mode?

Ok, I get it, I need to edit host parameters.

Done

I hope this can help.

I’ve just upgraded to 1.55 and set up a new image with my usual settings. Then, I launched a capture task which was much quicker during the “erase mbr” process (good point!).
But, when I checked the content of file d1.fixed_size_partitions, I’ve been disappointed because it’s still empty

I also tried to add “1” in that file and it works as expected, the system reserved partition not being extended.

So, despite being upgraded, my server still has the same behavior.

The French name of system reserved partition in W10 is : “Réservé au système”
Using diskpart, I get : “Réservé au” in Name column and “Système” in Info column.

How I can help to sort this out? What do you need, let me know.

Cheers

Max