@GregorS I have 3 Dell Models that are also doing this, but I will try the change to DHCP Boot file.
I will post back when I have an update.
Thanks!
@GregorS I have 3 Dell Models that are also doing this, but I will try the change to DHCP Boot file.
I will post back when I have an update.
Thanks!
@GregorS I have the same issue, was there ever a resolution to this? Except we are running RockyLinux 9.7.
Thanks,
Yes, was able to confirm it is working. Thank you for your help!
@Tom-Elliott I just updated to dev-branch version: 1.5.10.1719
Still getting stuck on:
Export Item(s)
Attempting to perform actions.
Just stuck on the screen, and won’t export to csv,
Thanks for taking a look at this.
@Richarizard504 Updated to 1.5.10.1716
Now am getting “Forbidden (invalid CSRF token)”
When trying to run group exports to PDF or CSV.
Any update would be appreciated.
Thanks!
When we are enrolling new devices into our environment our process is usuallty to roll through Quick Inventory and have them add themselves to a group where we can change the setting all at once. We then export the group, so that we can put the information from the export into another sheet for inventory purposes.
This has been working fine in the past, But we recently had to upgrade Fog to support network booting with newer docking station that we aquired.
I tried the most recent stable version, but ran into issues with the loading bar for both the GUI in FOG and the machine on-screen.
Seems like it was being stuck at 1% on some clients, but then eventually was able to complete.
I figured this was a bug so I upgraded to the most recent Beta version 1.5.10.1694, and now the loading bar issues seems to be gone, but we cannot export groups to excel or pdf files.
Any help would be appreciated.
Running on RockyLinux, and just upgraded Rocky fully before I put this post out there.
Thanks All!
@Sebastian-Roth I do not have more than 1 fog server. There is only one, and yes that file does exits.
Looks like this
<?php
/**
@Tom-Elliott Okay, that is what I thought, but I looked on the server itself in the /opt/snapins folder and the snap-in is in the folder like it should be. Which is why I was thinking a permissions issue.
I am not sure what else it could be. I think I am just going to rebuild the server and migrate our data over to the new server. Our old server was running on CentOS anyways. I tried as much troubleshooting as I could.
6/1/2023 11:05:15 AM Middleware::Communication ERROR: Could not download file
6/1/2023 11:05:15 AM Middleware::Communication ERROR: The remote server returned an error: (404) Not Found.
Running into some issues with Fog Snap-Ins. Wondering if anyone can help
Through troubleshooting, it seems like Fog can run the snap-in on the client machine, but the snap-in cannot access the powershell script that needs to be run. Seems like a permissions issue, but would like some help.
Thanks All,