@Tom-Elliott
Alright, that was the point where I was confused too. Now I understood.
Posts made by sega
-
RE: Deployment stuck at x percentage
-
RE: Deployment stuck at x percentage
I mean is there a setting in FOG where I can change it or does FOG just uses the version that is available?
-
RE: Deployment stuck at x percentage
We just saw our switches can’t process v3… Is it possible to change a setting that FOG uses the v2 of igmp?
-
RE: Deployment stuck at x percentage
Yea, it’s not possible having the FOG and the target pcs on the same subnet. Our switches have the option active igmp. And I see a warning on the switches that they get a v3 query but the device is just configured for igmp v2. But that I have to look with our service provider.
-
RE: Deployment stuck at x percentage
That’s a good idea to reduce the limit. But our priority will be to get multicast to work. I’m pretty sure somewhere in our network structure is the error why it’s not working yet.
Since we have to do that multiply times in a week, reducing the time would be great.And here are the logs: https://pastebin.com/JQadkbZ0
-
RE: Deployment stuck at x percentage
The current status: FOG and client pc in different VLANs. We have managed switches where the streams should be forwarded (we don’t managed them ourselves). We started a multicast session for 6 pcs. They are all going into the Partclone windows, but don’t start the deployment process.
In the active task tab I have once (under “Active Tasks”) 6 task (for each pc one) and under “Active Multicast Tasks” I have one for the whole group. State is in “In-Progess” and status is “0”.
edit: I somehow can’t post the logs because they are marked as spam
-
RE: Deployment stuck at x percentage
@george1421
We have the following structure:- FOG Server on office VLAN
- 3 rooms with separate VLANs each (because they have different rights in the network, but all can access the FOG server)
- FOG server is running on the VM but on ssd, if I’m correct
- All are linked with aruba managed switches
Somewhere I read that it’s possible to have it with different VLANs if the udp stream is forwarded.
The weird thing is: we didn’t had the problems in the past… so yea something in the network could be the problem. -
RE: Deployment stuck at x percentage
@george1421 The 10 pcs getting all the same image, but through the normal deployment. It would be still better to use multicast deploying in that case?
Edit: I tried the multicast for one group now, they starting the Partclone part but don’t start the deplayoment. As I seen the FOG server and the client pcs has to be in the same VLAN for multicast? That’s not our case, they have different ones.
-
RE: Deployment stuck at x percentage
@george1421 On that place we have 10 pcs, but all are connected at a one gigabyte port. So when all are deplyoing at the same time, the rate is decreased. If just one is deploying the rate is at that 5.7 GB/min.
But you saying that the problem isn’t something on the FOG more like outside, like the network connection? -
RE: Deployment stuck at x percentage
We tried to reset 8 pcs yesterday. 3 of them stuck at 22, 24 and 25% like shown in the image. These are also always different pcs.
https://drive.google.com/file/d/1tca2-DMd16ZeNwSitgC0hb0-xhaw-Ma2/view?usp=drive_link -
RE: Deployment stuck at x percentage
@george1421 It’s always different, sometimes at 34%, then 56%, then another number. But the next time it happens I will take a picture of it.
The fog version is 1.5.10 -
Deployment stuck at x percentage
Hi,
we noticed in the last time, that we have issues with the deployment process. Sometimes the deployment is getting stuck at a random % number.
The problem happens with different pcs and different images. Is there somewhere a log file which could give me a hint, what the problem could be? -
RE: Changing Heart rate of monitor after deployment/with snapin
@sega Whoops, yea I meant that.
-
Changing Heart rate of monitor after deployment/with snapin
Hi,
I would like to change the heart rate of the monitors after the deployment to automate as much as I can.
We have two different systems (PCs and monitors), so is that possible with the snapins for example? -
RE: Invalid signature detected on new PCs
After many try&error runs, I managed to sign the files and to boot into the FOG menu with secure boot enabled. And I can deploy an image, register the host and do all the other things except boot from hard disk. Whenever I choose this option in the FOG menu he just goes back into the menu.
When I boot directly from the hard disk it works and also if I disable the secure boot option the FOG menu can boot from hard disk.What could be the problem here? Oh and while I was troubeshooting I updated Ubuntu from 20.04 to 22.04 and FOG to 1.5.10
-
RE: Invalid signature detected on new PCs
@Tom-Elliott Hmm ok, thats really weird. I did the set up for these machines and if they won’t installed with the FOG client,I can’t imagine how… Can you tell me where normally the certificates are?
I found some certificates in following folder but I don’t think that’s the right ones… “opt -> fog -> snapins -> ssl -> CA” but I guess that something complete different -
RE: Invalid signature detected on new PCs
@Tom-Elliott I thought that too but these are the settings from the old PCs. The only thing that is weird here, is that Secure boot is enabled but there is also a “Not active”?
-
RE: Invalid signature detected on new PCs
@Tom-Elliott I know when we set up the last Pcs we didn’t install any certificates, just changed some settings in the mainboard and thats it (plus updating the BIOS).
Can you tell me where the certificates could be? Then I could look if there are some on the FOG server. -
RE: Invalid signature detected on new PCs
@Tom-Elliott Thanks for you quick reply.
As far as I know (didn’t installed it) there weren’t any certificates installed.
And, as I read my first post, that could cause a confusion, the old systems still work. So we have both systems currently here and just the old PCs working with the settings.