Found and fixed a typo in the IP address of the DB connector on the storage node.

@Sebastian-Roth
Ok, I see. Time is limited! I totally understand this. Well, I’d like to help but I’m have no developing skills at all. I’l try to further investigate the problem (saw some errors in the fog.log)
For the moment this issue can be closed.

@Sebastian-Roth

Sorted!

As soon as i imported the hostMAC table they all appeared in the web portal.

For anybody reading in the future:

To Migrate just your Host list, you will need to export both the “hosts” and “hostMAC” tables from the old database using mysqldump, then import them both into the new database. Just doing the hosts table will not make them show in the web portal.

@george1421 Thanks, that is helpful to know.

Some reports, like “imaging log”, don’t have pre filters and try to show all the entries in the database, normally you have a lot of entries in the database and the server doesn’t have memory to run it.

In the dev-branch, not stable branch, I made some changes in the reports to have some pre-filters, with these pre-filters you can limit more the search parameters and be more exhaustive and use less memory 😉

@luiztpd said in WOl Broadcast not work:

my server fog is with network ip address 192.168.x.x / 24;
the workstations are in a vlan 172.x.x.x / 24 and other 172.x.x.x / 21!

That is probably part of your issue. Unless your vlan router support directed broadcasts the WOL messages are probably not traversing your vlan router. As a test install a workstation on the 192.168.x.x network and then test.

Then I would suggest you test WOL with a third party application (install on the 192.168.x.x subnet) and see if it can wake up a workstation on the 172.x.x.x subnet. Lets try to understand where the problem isn’t before we focus on a solution (maybe).

@Sebastian I need to look into something I found over the weekend. I installed Linux Mint 19.1 on a test Dell computer that was in uefi mode and had raid-on mode configured. LM 19 installed correctly and ran. There was some strangeness with the network adapter so I reloaded LM in bios mode. But then it hit me, why was LM working in uefi mode…?? I need to find out if the linux kernel developers addressed the Intel Raid controller issue in Raid-On mode.

@Sebastian-Roth I added the new lines to my /etc/apache2/sites-enabled/001-fog file, entered my credentials and waited 10 minutes… No change, still getting an HTTP/503 response.

I downloaded the script to the FOG server, ran ./updateIP.sh, and got the following results:

Updating the IP Settings server-wide. A password was not set in /opt/fog/.fogsettings for mysql use. Updating the IP in /tftpboot/default.ipxe Backing up /var/www/html//fog/lib/fog/config.class.php Updating the IP inside /var/www/html//fog/lib/fog/config.class.php Updating the fields inside of /opt/fog/.fogsettings All done.

I tried to log in again, and it’s still spinning around (although, it’s only been 2 minutes since I ran the script and tried to log in).

EDIT: It’s working now! After running the script, I also restarted Apache, PHP and MySQL, then tried again:

systemctl restart php7.0-fpm.service apache2.service mysql.service

@xburnerx00 Sorry for the delay! It’s a topic that I need time to work on and I didn’t have much of continuous time to focus on this.

I totally understand that you’d like FOG to remove printers from a PC again. Did you use “FOG Managed Printers” or “Only Assigned Printers” in the settings. Both should remove printers that are not assigned to the host.

That said I understand that you are in doubt as using the PrinterManagementHelper left you with an undeleteable printer and the fog-client wouldn’t even create your printer in the first place.

I have just spun up a test setup and cannot replicate any of the issues. Don’t get me wrong, I am not saying there aren’t any problems with printer management but I can’t see them in my setup yet.

I have a Windows 10 1803 install, working as normal user (not Admin), assigned printers in the webUI were created properly and also removed when I unassigned the printer for this post.
As well I tested the PrinterManagementHelper, printer was created and I could also delete the printer (Right click -> delete) without any notice or issue.

So I guess there is a lot we have to dig up first before we can address the issues. Let’s start by comparing the setups. Which version of Windows do you have and is the account you are working on an Administrator or normal user account?

I can imagine this being caused

But this task is not as trivial as you might guess. E.g. when you remove a printer from the list of printers for one particular computer we’d need to keep track of this in the background to be able to do the removal on the client PC itself. We

@Sebastian-Roth
No no, you’ve made clear that it is a lost cause trying to sort this out. If I had a clean capture and deploy on this version showing the system partition shrinking it would be different. Your comments made that clear. Thanks for the help.

@mig39 I would only turn off spanning tree on a switch where you have 100% control of the switch ports. If any of the switch ports are user facing I would not disable spanning tree. Your cisco switch should support rapid-stp or fast-stp. That is all that is needed. Then you don’t run the risk of a loopback taking down your network.

Can you upload the pcap of your pxe boot where PXE error T01 is thrown? I’d be interested in seeing why for my knowledge, especially if this is the only model giving this error?

@Hoghsfoot Search the forums for “persistant groups” to understand that FOG has a different concept of the group settings than you think.

Here are the screenshots your requested

Screenshot from 2019-03-21 10-21-20.png

Screenshot from 2019-03-21 10-23-22.png

I’ve changed fog user password to what was written at the bottom in web UI -> Storage -> DefaultMember as you just said, and it worked perfectly ! I just uploaded one more Image and no error - task complete and I am able to deploy it. Thanks a lot guys !! ISSUE SOLVED

@george1421
Increasing PHP-fpm memory did the trick.

Thx for the thinking together.

@nehsa said in Create scheduledtask via POST to API:

“minute”: “30”,
“hour”: “5”,
“dayOfMonth”: “",
“month”: "”,
“dayOfWeek”: “*”,

This all depends on the type of task this is to do:

The json elements that you can set:

{ "name": 'Some Name', // Optional "description": 'Some Description', // Optional "type": "C", // C = Cron, S = Single "taskType": 1, // ID of the task type, 1 = deploy, 2 = capture, 3 = debug do not use this one, 4 = memtest, 5 = test disk, 6 = disk surface test, 7 = recover, 8 = multicast, 10 = inventory, 11 = password reset, 12 = all snapins, 13 = single snapin, 14 = wake up, 15 = debug deploy, 16 = debug capture, 17 = deploy no snapins, 18 = fast wipe, 19 = normal wipe, 20 = full wipe "minute": 30, "hour": 5, "dayOfMonth": '*', "month": '*', "dayOfWeek": '*', "isGroupTask": 0, // 0 = host only, 1 = group task "hostID": 1, // If is grouptask is 1 this will be the group id, otherwise the relevant hostID "shutdown": 0, // 0 = restart, 1 = shutdown "other1": "", "other2": "-1", // Snapins either the id of the individual snapin, or -1 for all. "other3": "fog", // The username who created the task "other4": true, // Wake On Lan? "other5": "", "scheduleTime": "", // Only used for delayed time in which case you will need a valid unix timestamp in the future. "isActive": 1, // 0 or false would mean the task is not active currently. "imageID": 1 // The image ID in the case it's an imaging task. Can be any imageID you want. }

Much thanks, George and others for the help. As well as saving my company thousands of dollars! 🙂

@george1421 You are the man! That was it! I made the changes and the menu came up. It was the - before the Windows 10 1809 - Office 2013 image