@Tom-Elliott

I’m using Google Chrome.

Version 59.0.3071.115 (Official Build) (64-bit)

I’ll post a screen shot in a few minutes when I do another imaging task.

It would be awesome if the page that you land on when you click on Hosts, has a search box in it in place of where it says no results found. An alternate would be to have the landed page be Search All Hosts.

If their is a way for me to set mine up to go to Search All Hosts, when I click on Hosts, I’d love to try that.

Thanks!

Cheers,

Joe Gill
Townsend K-12 Schools

@Tom-Elliott

I noticed that any time you click update on any of the interfaces (IE setting up an imaging job (basic tasks), printers, ect) it does not refresh your screen as it did in previous versions of FOG.

For example, I created an imaging task for one machine using basic imaging. Clicked on capture, clicked on update, and the screen stayed the same. It never appeared that it had done any updating at all. I had to navigate to tasks to see that it had started.

In FOG 1.5.0 RC 2, the printer list disappears after you add a printer to a host. It would be awesome to have the printers that are attached to the host be displayed after the update key is pressed.

This would also be nice to be seen when you change the FOG to Printer relationship on the host.

I’m enjoying the new look!!

Thanks!

Cheers,

Joe

Server

• FOG Version: 1.5.0 RC 2
• OS: Debian 8.8

Client

• Service Version: 0.11.12
• OS: Windows 7

Description

When deleting multiple hosts, only first host in list gets deleted. The list shows all of the hosts selected. When you hit delete, it only deletes the first one in the list.

Impressive! Very nice overhaul of the web interface!

@Developers Thank you!!

@Wayne-Workman

So after much frustration, here is what I came up with!!

Set FOG to Only Assigned Printers…
Delete all current printers…
Set FOG to FOG Managed Printers…
Re-Add Printers…
Reboot PC.
Voila! The new driver is added and you’re good to go!!!

So FOG CAN do it.

For the amount of headache I just spent on trying to figure out GPO to enable scripting. Testing script and getting everything to work… The above is much simpler…

For what it’s worth… I did find a link to your script. You had given it to me once before also. LOL!

https://forums.fogproject.org/topic/8406/fog-client-printer-not-displaying

Thanks!

I’ll try that and report back! That may be easiest. I know their are a few utilities out there that can manage printers but I like the all in one. I also like being able to use FOG for everything.

If I find your old post I’ll post a link to it here. Otherwise, I’ll post what I find out.

Thanks!

Server

• FOG Version: 1.4.4
• OS: Debian 8.8

Client

• Service Version: 0.11.12
• OS: Win 7 SP 1

Description

@Joe-Schmitt
@Wayne-Workman

Our district recently replaced all of the printers (new manufacturer). I updated the driver file and printer model on the server for every printer and left alias’s and IP’s the same. All of our hosts are set to Managed Printers in FOG.

I checked one of the host machines and it is updating properly from FOG. The FOG client, however, doesn’t recognize that their has been any change in the printer file and is not updating our clients. Is their a way to force all printers to update?

Thanks!!

Cheers,

Joe Gill
Townsend K-12 Schools

Server

• FOG Version: 1.4.4
• OS: Debian 8.8

Description

This isn’t a huge deal but I noticed this today… It looks like FOG is dropping the second digit for the day on the imaging graph on the Home screen. You’ll notice where it says “Jun 2” on the far right hand side of the graph… It should be Jun 29. Like I said, not a big issue. I don’t think this is a screen resolution issue, but I have not checked.

Cheers,

Joe GIll
Townsend K-12 Schools

@Tom-Elliott

Yes sir! Things are working well! I’ve multicasted several machines this afternoon without a hitch. Yay! Thanks!!

We discovered the issue… DNS was not set properly on the FOG server… Don’t ask why this made a difference but when I reset things and restarted the server WOL works again. Ugh!

Settings on our switch ports were identical. So that was likely not the issue.

@Tom-Elliott

You were correct! I apologize! I forgot we moved my test lab to a different switch. I can use WOL just fine now in one of my other labs on a different switch. Having the network admin adjust the port settings on that switch. I’m certain that’s the issue!

Everything else with our upgrade is working! Yay! Now I’m on Debian on upgraded hardware.

Thanks!!

@Tom-Elliott

Sounds like it must be a setting on my VM. I’ll check it out and post a fix when I figure it out. The only things that have changed are the OS and the OS the VM is running in and the new enclosure. It must be one of those things.

Thanks!

@Tom-Elliott
@Developers

I just tried sending a Host a Wipe task w/ WOL. The host appeared in my task list like it should. WOL did not work. I manually powered on the host and it PXE booted into the task and started the task. So it appears everything functions except WOL.

@Tom-Elliott

Well I updated to 1.4.4. I ran back through everything to make sure I had all my usernames and passwords changed on the server. I found a few that were not correct. That seems to have resolved the non-PXE boot issues…

The WOL issue is still there though. Now I task it and it doesn’t show up in tasks. But nothing happens on the hosts I’m tasking.

@Tom-Elliott

One thing that did change on this install is that I eliminated a password on our mysql database and I eliminated the FOG user on the server and FOG itself. I have gone through and done the best I could to change those things throughout FOG.

@Tom-Elliott

I will update to 1.4.4.

FOG server is on the same subnet as the hosts. I haven’t changed any of my addressing from old FOG server.

@Tom-Elliott

I created a WOL task and the hosts are non-responsive.

I PXE booted one of those hosts just now and got this message…

Changing permissions made no difference. The machines still will not task.

Any suggestions would be helpful!

Thanks!!

Cheers,

Joe Gill