@tom-elliott I’m having this issue as well. Login screen appears pretty quickly, but logging in takes at least 3-5 minutes and all UI navigation takes several seconds to up to a minute to load.
Posts made by moses
-
RE: Slow webinterface after update to 1.5.0
-
Per-group timezone settings via FOG client
It would be nice if we could set the client’s time zone on a per-group or even per-client basis.
-
RE: Active Directory OU aliases
@george1421 I’d be really interested in your setup, because that’s exactly what I would ultimatly want. Our setup would be much simpler, if it’s possible to do it this way, but we have several physical locations and one OU per location.
How might I go about getting FOG to change the OU based on location? I am using the plugin. Might you be able to share a redacted version of the scripts you’re using?
-
Active Directory OU aliases
We have multiple OU destinations for computers joined to our domain via FOG, and right now I’m using a text file as a cheat sheet for those OU paths, which I copy and paste into the host settings.
What would be nice is if we could define aliases to use for each OU, rather than having to type/paste the full OU path each time we set up a new host, or not have to put them in the same OU every time.
Perhaps aliases could be defined in FOG settings, and then the user could select from a dropdown list in the Active Directory settings for the host? Correct me if I’m wrong, but this would be as simple as a constant being defined for the OU path string when the user creates an alias.
-
RE: How can one manually & locally clone image to device using Clonezilla?
@george1421 I completely forgot I have a USB ethernet adapter. I’ll give that a try.
-
How can one manually & locally clone image to device using Clonezilla?
I’ve got a notebook I need to image from FOG, but alas, the ethernet adapter is dead.
Is there a way to manually write a standard single disk/resizable Windows 7 image that I have on my FOG server if I copied it to a portable HDD? I’ve used Clonezilla in the past, but I’m sure with resizable images, there might be some extra steps involved.
Here’s the image as it is on my FOG server:
-
RE: Deploy fails - detected stalls on CPUs/tasks
@george1421 Well,
acpi=off
in the kernel options did the trick. Must be one of those finicky models. Thanks! -
RE: Deploy fails - detected stalls on CPUs/tasks
@george1421 It’s BIOS, yes, but I’ve never had to add that argument for any other computer using BIOS. Regardless, I’ll give it a whirl and report back the results.
-
Deploy fails - detected stalls on CPUs/tasks
Server
- FOG Version: 1.3.5
- OS: Centos 7 x64
Client
- Service Version: N/A
- OS: Windows 7
Description
I did a quick registration on a HP Z400 workstation, and that worked fine, but when I attempted to deploy an image I got the following:
So I then stopped the task, deleted the host, and did a full registration instead. The registration worked okay, and the deploy task got a little further this time, but then it halted here:
Any idea what’s going on? I’m using
undionly.kpxe
, if that’s relevant. -
Windows 7 OEM Activation Script - FOG Edition
Greetings,
I’ve been using FOG for a little while now and where I work, we buy PCs that typically come with either an OEM Windows 7 license or Windows 8 with downgrade rights to 7. FOG handles retail or volume keys fine using the FOG client, but this won’t work for these OEM licenses or downgrade right installs.
So I made myself a little SetupComplete script about a year ago that lets us quickly clean image these PCs and activate Windows the same way the OEM does when they arrive on our doorstep sysprep’d from the factory.
You can read about how to do this yourself here, but I wrote a version that might suit FOG Project fans.
What it does:
- You select the manufacturer of the PC (or use the new “automatic mode”)
- The script identifies the edition (Home Premium, Professional, etc) and installs the corresponding OEM cert and key
- Verifies that activation was successful
- Starts up the FOG client service
It’s written in Batch and it’s messy, but it works. Feel free to fork it to make improvements, or open an issue on Github if you discover a bug.
Cheers!
For now, you can view the FOG Edition of the script on Github:
https://github.com/mgiljum/Windows7-OEM-Activator/tree/FOG-EditionOr you can download it directly here (just be sure check the
README.md
https://github.com/mgiljum/Windows7-OEM-Activator/archive/FOG-Edition.zipNote: the “Non-FOG” edition of the script (can be found on Github) does the same thing, it just doesn’t start/stop the FOG service or come packaged nicely with a SetupComplete.cmd template.
-
Anyone using Webmin + FOG? Compatible?
Has anyone attempted installing Webmin along with FOG on a CentOS or Debian box? I love it for management but didn’t want to screw up FOG. Any experience with compatibility?
I’m using stable FOG 1.3.0
-
Timestamps for image transfer logs
Under FOG Configuration > Log Viewer > [Nodename] Image Transfer Log, I get the following:
Transferring file `d1p2.img' Transferring file `d1p2.img' Transferring file `d1p2.img' Transferring file `d1p1.img' Transferring file `d1p2.img' Transferring file `d1p2.img' Transferring file `d1p2.img' Transferring file `d1p1.img' Transferring file `d1.partitions' Transferring file `d1.mbr' Transferring file `d1p1.img' Transferring file `d1.partitions' Transferring file `d1.original.swapuuids' Transferring file `d1.original.fstypes' Transferring file `d1.minimum.partitions' Transferring file `d1.mbr' Transferring file `d1.fixed_size_partitions' Transferring file `d1p2.img' Transferring file `d1p2.img'
Is there any way of adding timestamps to that, for when each transfer started? Without it, there’s not a whole lot of information to be garnered here.
-
RE: "Could not find a Storage Node in this group, is there one enabled?"
Finally got it to work by moving the storage node to a different one, turning it off as a master, then creating a location for that node specifically in the Locations plugin.
Still, not sure why my initial setup stopped working. This will do for now, but hopefully I can get it figured out. If anyone can provide some direction, please let me know.
-
"Could not find a Storage Node in this group, is there one enabled?"
Server
- FOG Version: 1.3.0-RC26
- OS: Centos7
Client
- Service Version: N/A
- OS: Windows 7
Description
When attempting to deploy an image onto an HP Elitedesk 705 G2 Mini, I get the following error:
*Attempting to check in......Failed *Could not find a Storage node in this group, is there one enabled? *Attempting to check in ....Failed
This repeats endlessly until I shut the PC down.
In FOG, the host is in a group with a storage node in it. Not sure what else needs to be done to get it to deploy correctly.
Edit: I can get around this problem by deleting all the entries in the Location plugin, but that’s no good because I need to image a PC where this storage node is local and the DB server is remote, and would take hours.
Edit 2: I deleted the storage node, and the storage group and reinstalled FOG and recreated the storage node, same error.
-
RE: Image doesn't replicate after updating to RC19
@Tom-Elliott You’re the man, Tom!
-
RE: Image doesn't replicate after updating to RC19
@Tom-Elliott Ah, yes, didn’t look at the value type, thought it was an integer. That worked.
As I said, I’ll personally just ignore this for now, since this only seems to be a problem with this particular image. You can mark it as solved if you want, or track it if the other posts Wayne referenced are relevant/needs further investigation. I can provide any logs/info you might need if you want to look into it further.
If it matters, I updated this morning to RC20 and the issue persists.
-
RE: Image doesn't replicate after updating to RC19
@Tom-Elliott Unfortunately, I can’t change it the GUI still. It doesn’t change from a 0.
Worse still, I can’t change it manually in the DB:
I’m using:
UPDATE imageGroupAssoc SET igaPrimary = 1 WHERE igaID = 118;
It now results in:
Query OK, 0 rows affected (0.00 sec) Rows matched: 1 Changed: 0 Warnings: 0
The table is here:
+-------+------------+-------------------+------------+ | igaID | igaImageID | igaStorageGroupID | igaPrimary | +-------+------------+-------------------+------------+ | 23 | 4 | 1 | 0 | | 57 | 10 | 2 | 0 | | 58 | 10 | 1 | 0 | | 68 | 10 | 7 | 1 | | 71 | 10 | 8 | 0 | | 70 | 4 | 7 | 1 | | 75 | 10 | 9 | 0 | | 77 | 10 | 10 | 0 | | 79 | 4 | 8 | 0 | | 80 | 4 | 9 | 0 | | 81 | 4 | 10 | 0 | | 103 | 17 | 10 | 0 | | 118 | 17 | 7 | 0 | +-------+------------+-------------------+------------+ 13 rows in set (0.01 sec)
Is my query correct? This issue only appears to happen with this image, so if I can set it correctly manually I’ll just ignore it from here on.
-
RE: Image doesn't replicate after updating to RC19
@Tom-Elliott See the bottom of my post below; changing it manually worked and replication starts, however can’t change it in the webgui. If you need any specific logs on that let me know.
-
RE: Image doesn't replicate after updating to RC19
@moses Nothing of use is showing in the PHP logs, but mysql shows that value is left at null (last entry):
+-------+------------+-------------------+------------+ | igaID | igaImageID | igaStorageGroupID | igaPrimary | +-------+------------+-------------------+------------+ | 23 | 4 | 1 | 0 | | 57 | 10 | 2 | 0 | | 58 | 10 | 1 | 0 | | 68 | 10 | 7 | 1 | | 71 | 10 | 8 | 0 | | 70 | 4 | 7 | 1 | | 75 | 10 | 9 | 0 | | 77 | 10 | 10 | 0 | | 79 | 4 | 8 | 0 | | 80 | 4 | 9 | 0 | | 81 | 4 | 10 | 0 | | 103 | 17 | 10 | 0 | | 114 | 17 | 7 | NULL | +-------+------------+-------------------+------------+
Changing it manually to a 1 fixes the issue and replication starts, but still can’t update it using the UI.