Posts made by John L Clark

@george1421 probably a few 1000. Not sure of the exact number. We only started seeing this a few months ago.

@sebastian-roth
This is what I see. Thanks

As of late Fog is running extremely slow. We have had no changes to fog but pulling up the GUI takes forever. Then searching for anything is very very slow. This is a screenshot of the server information. Any help would be appreciated. Thanks

@sebastian-roth

This is how I install it manually. I browse to it and right click and click connect. I will uninstall it on my computer and try it your way. Thanks

@sebastian-roth I am sorry it is 21H1

@sebastian-roth Windows 10 and Fog client is 0.12.0

@sebastian-roth It was working last school year. Not sure when it stopped. We have found that if you install the printer manually and then remove it, it will install properly with Fog.

Fog log says that the printer we are installing on all machines is already installed but when you pull up the printers it is not listed. This is a network printer and not a TCP/IP printer. It is a shared printer off of our badge printing server.

@sebastian-roth

@sebastian-roth I went through the entire database clean-up that you sent and I am still unable to run a full report of all inventory. Is there any way I can just get an Export of all hosts?

@sebastian-roth Here is a clip of the PHP log. Not sure what it means.

@sebastian-roth try this https://drive.google.com/file/d/1I_LFCwT0INMzg8vHbbi60KSqvYHtNDKN/view?usp=sharing

@sebastian-roth error.log I have attached the error log . Thank you

I also get the same thing when I try to export all hosts.

@sebastian-roth

@sebastian-roth We are on 1.5.9 I am able to select AD_creditiels and then each model and get the report for that but we are needing all inventory.

Fog-srv is currently unable to handle this request.

HTTP Erro 500

I just need to export all inventory to a .xls or pdf.

When I click on host list or Inventory I get the a page that says this page is not working.

@george1421 Worked Great thank you sir. It was the Storage node password was incorrect.