@nkduy1508 You can either use Greasemonkey or other plugins to hide the IDs.

Or you can manually edit the PHP code (/var/www/fog/lib/pages/imagemanagementpage.class.php on your local filesystem) to remove the ID. Though the later will be gone when you update your FOG install.

@mikmatcr If this only ever happens on multicast deploys we should start looking at those logs I reckon. Please upload all the log files you find in /var/log/fog/ that have multicast in their filename.

Though I am not much optimistic we’ll find the issue in multicasting. I say this because in the pictures we see errors at various points in the deployment process. That points to hardware issues on those machines I would guess. Maybe dying hard drives or memory or whatever.

@Jordane said in ERROR: Could not get security token:

Indeed, in the local security strategy of our clients, the FIPS encryption is activated.
But also the option, Configure the types of encryption allowed for Kerberos “AES256 and future”.
These are the options that would block me?

Probably yes. And I really do understand your organization is forcing FIPS compliance.

AES is not compatible with FOG services?

Well, AES is actually a subset of the Rijndael implementation used in the fog-client. So it’s pretty close. I guess we can switch to using AES as I said before but not in a quick move! Needs code changes and testing.

I was going to open an issue report on github to keep track of this but turns out this has been around since a long time already as well as another forum topic (sounds like the fix isn’t that easy…)

Is it possible to disable encryption from fog and the TOKEN function?

No, not right now. One of my future plans was to remove the self made encryption from the fog-client/forproject code but switch to using HTTPS (enforced). This way we’d rely on state of the art crypto done by webservers and system crypto libraries. But that is even further away than switching to AES.

Ideally, it should communicate with clients without encryption.

I don’t get this. Why would you enforce FIPS compliance but then let the communication go unencrypted?!?!? Just doesn’t make sense to me.

@Sebastian-Roth Thanks…

@lostitguy From what you describe it’s iPXE pulling the wrong MAC address. To get this fixed you’d need to contact those people: https://ipxe.org/contact

The quick workaround you can take is booting this particular machines via USB: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

@danieln said in Cannot delete image off of all nodes. Type 2 FTP Error...:

If I wanted to do this, would I just delete the entire directory? Or would I just delete the d1p1.img file? I feel like the entire directory, right?

Yes, delete the whole directory.

Speaking of, is doing an update just running the following commands?:
cd /fogproject
git checkout dev-branch
git pull
sudo ./installfog.sh

As I said, there is a new official release in the pipeline and you could install that if you feel like it. Instead of dev-branch use master instead in the above command sequence.

Is there anything else to it? Aside from backing up the FOG database?

If you have FOG running in a virtualized environment I would also take a snapshot just to be sure. As always, backing up the DB is advised.

@danieln Great to see you figured this one out yourself. Would have been quite a challenge for us to help find that issue.

@Tom-Elliott said in can’t install sumatrapdf:

@kalafina I suppose this is fixe then?

So Snapinarguments becomes: -all-users -s ?

Yes!

@snmdla said in Snapin group:

@Tom-Elliott
yes, it appears to have no effect, as no plugin task is created as far as I have seen.
Please correct me if I’m wrong.

ah, I think I now understood. The dialogue will associate all group members with the snapin, which will only be fired when, for the individual client “All Snapins” task will be run.

So, to correct my usability suggestion, it would have helped to read “all group members updated” instead of “group updated”.

@Sebastian-Roth Thanks I change the mounting point then it works.

@Tom-Elliott

I hadn’t thought to check in that direction. But you are correct.
BASE64 encoding what is in the database matches what is displayed in the web UI.

Thank you for the help.

@george1421 Thank you very much!

Hey guys,

Thanks for replying. I have found a solution and that was to clear out the Storage Node Disk Usage. It was full.

Thanks again.

Update:

Trying the installation again worked.

¯_(ツ)_/¯

@MikeWall We have a plugin for Product keys already…

https://github.com/FOGProject/fogproject/tree/working-1.6/packages/web/lib/plugins/windowskey

https://github.com/FOGProject/fogproject/tree/master/packages/web/lib/plugins/windowskey

Problem solved !

Thanks a lot !!

sorry for the delay

i solved it.
It was a Pre-Install System from a Distributor with a lot of bloatware, what i first not know.
I installed a Clean Windows 11 System and then i could capture the Image.

@switch_apoc Well, this forum topic is pretty straight forward. Just start reading upwards beginning from this post: https://forums.fogproject.org/post/135069

Hello Sebastian,

this is my original d1.minimum.partitions file:

label: dos label-id: 0x4ff028f0 device: /dev/sda unit: sectors sector-size: 512 /dev/sda1 : start= 2048, size= 2196723, type=7, bootable /dev/sda2 : start= 2198771, size= 75451766, type=7

this is my original d1.partitions file:

label: dos label-id: 0x4ff028f0 device: /dev/sda unit: sectors sector-size: 512 /dev/sda1 : start= 2048, size= 2196723, type=7, bootable /dev/sda2 : start= 2198771, size= 264139264, type=7

What i did is to change the size of sda2 (my windows partition).
The original start was 2198771 sectors x 512 Bytes = 1125770752 Bytes div 4096 equals = 274846,375 - not good !
To align the partition correctly i used 2199552 sectors =
1126170624 Bytes / 4096 = 274944 - that’s good !

You just need to choose a sector start that is divisible by 4096.
I took my size from a aligned partition where AS SSD showed me that
1099776K would be ok. 1099776 x 1024 Bytes = 2199552 x 512 Bytes

Easy maths - but it is annoying , here 512Bytes shown here, 1024 Bytes shown in AS SSD and 4K Bytes needed to calculate the correct sector size.