@Fernando-Gietz Thanks, now its working!

[EDIT: sorry didn’t see this marked as “solved”]

@jconway1006, not sure if you were able to get your web service back up.

After testing on CentOS, I found that 1.5.7 would not work, and I had to move to dev-branch (1.5.7.2)… not sure why, but it worked. Maybe a clean install on the VM server is best.

I’ve also noticed with VMware it frequently takes more than one try to get the iPXE connection. To get around it

boot to EFI bios and try PXE network boot

at each failed attempt, choose the shutdown option in blue screen

rinse and repeat

Found the issue! After some research and discussion with Cisco, we had to add “PIM” to the vlan on our core, even though both the server and client are both on the same vlan!

Used the command - ip pim sparse-dense-mode on vlan 1 interface and it started working like a charm! I really appreciate everyone’s assistance here. This will help our institution so very much.

I was using notepad ++. I guess creating the files from scratch uses the windows CR EOL format. I switched them all to LF and will never have this insanity happen again!

thx!

@Athena What exactly do you need help with?

I still pushed the fix but I’d hope that people help us testing things more!!

@njones You expect group settings to be what I’d call “persistent” but that is not the case in FOG. Groups are more or less just a tool to push settings out to severl host objects but does not store the group information within the group object. Please search the forums for “persistent groups” and read a couple of topics on this.

Hi @Sebastian-Roth and @EduardoTSeoane,

Thank you for your answers.

@Sebastian-Roth said in Multicast with multi-NIC FOG server:

@benjamind May I still ask you to post the full output of the command ip a s. I don’t like to do all the guesswork.

Sorry, but i have removed the virtual NIC to put the server directly in the subnet of the machines.

@Sebastian-Roth I had the same errot as @zclift15 but it seems to have fixed itself perhaps it just took a minute for the change of primary disk to trickle down

@george1421

George/Tom…you are genius’s

I am overcomplicating things. To not define address’s was the answer. Multicast works on my network as i said earlier because i can VLC RTP stream just fine. I have routers setup to do PIM SM. Specifying a multicast rdv was my downfall.

All of you are amazing. Please keep up the great work!

@chunter2 said:

05/09/2019 7:45 PM PrinterManager Adding printers 05/09/2019 7:45 PM Printer Adding: Computer Lab x64 05/09/2019 7:45 PM PrinterManager Could not read printer INF file: bad path 05/09/2019 7:45 PM Printer Adding: Workroom Copier_64bit 05/09/2019 7:45 PM PrinterManager PrintUI return code = 0 05/09/2019 7:45 PM PrinterManager Restarting spooler

And then this the second and subsequent times through.

05/09/2019 7:47 PM PrinterManager Adding printers 05/09/2019 7:47 PM PrinterManager Computer Lab x64 has already been configured 05/09/2019 7:47 PM PrinterManager Workroom Copier_64bit already exists

I might have misunderstood that part wrong when you mentioned this first. It’s not easy to keep up with dozens of requests in the forums and see it all clearly when things are a bit hidden between the lines or messages. I hope to get some more time to dig through that part of the code and see if I can find out why it was programed the way it is (or find a loop hole in it).

I do understand this is an opensource project so no need to feel bad for not having the time. I can wait. I hope I’m coming across as a help and not demanding.

Thanks for mentioning! Good to hear that we are on the same line here.

Or use sysprep to power off the computer
Or run this command to properly power off the computer for cloning shutdown.exe -s -t 0

You found the issue with Windows 8+ where shutdown isn’t really shutdown but an enhanced sleep mode. Disabling fast boot actually puts the computer in a powered off state too.

@Sebastian-Roth That’s fine. Things have been pretty swamped over here so I had to put the issue on the back burner. The issue doesn’t always show up, so troubleshooting has been time consuming.

@snap7B Any news on your test using the netdom command? Unfortunately I don’t have such an AD setup and won’t find the time to set one up any time soon. But I could try adding more debug output and provide that as a new DLL to you so we can figure out what goes wrong.

We had a similar message in a different thread. The OP at that time had a 486 industrial machine that was stalling issues even after I rebuilt a 486 kernel. Anyway, to the point we had to add acpi=off as a kernel parameter for that 486 to boot correctly. Once that was done it imaged correctly.

So lets try a host specific kernel parameter of acpi=off for this host.

@markbam Thanks for testing und letting us know! I will add this to the official code und it will be in the new fog-client releases from then on. But I won’t update the official 0.11.16 version. Feel free to use that DLL provided.

@VictorV I’m not 100% sure if this works, but you could try to make the partitions the relative percentage of size as to what you want and then capture as Resizable type image.

If I’m not mistaken, it will try to resize those partitions according to their relative size.

So if for example you have 😄 as 20GB of a 100GB disk and 😧 as 80GB of a 100GB disk, then it should come out as roughly 100GB for 😄 on a 500GB disk and 400GB for 😧

Alternatively and perhaps more flexibly, you could make a non-Resizable image with just the 😄 partition and then include a SetupComplete script that automatically creates the new partition for you using diskpart.

Or, if you are more comfortable/knowledgeable in Linux, you could also try to do the same as the above, but using FOG postdownloadscripts (scripts that run after deploying the image, but before reboot)

@FogNewUser Ok this one almost tells me what I need to know, from the picture perspective it would be handy to see more to the left edge to get the complete interface name.

But what I see you have built in network adapters (knowing its a P710) helps with the guessing and maybe 3 riser card network adapters. At this point I don’t see any interfaces with IP addresses, so it looks like you have a bunch of unconfigured interfaces.

From the screen shot it looks like you have a debian based OS (could be ubuntu which is debian based). So you will need to use the network manager if you have the gui loaded to define an IP address for your fog server. IF you have fog installed AND it was working you can refer to the file /opt/fog/.fogsettings to what the IP address of the fog server was when FOG was installed. You need to move it back to that IP address or you will have to make several changes to the fog configuration since the IP address is hardcoded in a few spots.

@Sebastian-Roth Didn’t has time, sorry. The whole PLUGIN thing was actually new to me, so now after quick navigation in settings, I’ve explored PLUGINSYS checkbox. 😃 Thank you, now I’ll sped some time to investigate all of the “mainline” plugins. Thank you for advising me to use this plugin.

PS
Aaan,d I could’t find any functionality that I’ve implemented, also the whole thing seems not working, because I couldn’t restrict Support role from accessing “Access Controls”, where they can revert everything back.
I also reported to this topic about last problem: /topic/10918/access-control-plugin/10

@zclift15 As well read through this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit