Posts made by Scott Adams

Running Ubuntu 14.04, FOG Trunk 7252.

Have set Active directory settings in FOG Configuration. I put plain text password into the field for the new client, and the encrypted FOGCrypt password for the legacy client (I do not have any legacy clients out there though).

After an image, the computer never joins the domain. If I try to rename the computer in FOG, the computer never restarts to change the name.

Not sure what’s going on, but I have noticed that the new client AD password is different on every host that I look at. I know it is encrypted, but the encrypted password is different for every host. The legacy password is always the same. Is this normal? Doesn’t make sense to me why the password would be different for each host.

I am experiencing the same issue. Looking forward to a resolution.

Thanks Tom and everyone! The update has resolved the error with my kernel download. Not sure what got flubbed up to begin with, but resolved.

CPU seems to be looking more normal as well, after deleting all the hosts and re-adding as they check in.

Can be marked as solved.

I was able to push download the newest kernel using pscp (a PuTTY command). I used the site https://fogproject.org/kernels/ to get the latest 4.5.1 kernel.

However, still have the below issue when trying to use the built in kernel update via WebUI:

Any ideas? I’ve checked every permission I know to check and made sure all usernames/passwords are correct (at least in all the locations I know).

Is there possibly a download site I can go to in order to manually download the kernels? I can just push to the FOG server that way while waiting on a resolution to this issue.

Thanks!

I have verified that it is not a credentials issue with FTP. I changed the password in the FOG Settings section of configuration, and got an error about invalid login. I set back to correct password, and received the error message "Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 144, Message: ftp_put(/var/www/html/fog/service/ipxe/bzImage_tst): failed to open stream: No such file or directory:

I am able to open the FTP webpage and log in using my correct fog settings. Any thoughts?

Attached is a screenshot of my config home page. If you look at the bottom, it doesn’t even show what version of bzImage I am using. Could this be related? How do I fix?

Alright. After @Sebastian Roth said to look at how many hosts I had, I noticed a huge problem. We were listing about 1000 more clients than I know I have in my active directory. So, just to start with a clean slate, I deleted ALL hosts, and immediately the WebUI started responding again.

Thanks!

However, I am still having the issue with the kernel update and the error about FTP_Put. Any thoughts?

When I try to pull up the log viewer, I don’t have any options when I click the drop down.

I have restarted my FOG server several times, as well as the mysql service and the Apache2 service as well.

Have recently (within the pas week) been getting terrible response from the WebUI for FOG. Takes 30 sec - 1 minute to log in, swap screens, etc. From an admin standpoint, it’s becoming almost unusable.

Also, with the addition of a new model laptop, I tried to update the kernel to hopefully allow imaging of the Latitude E3350. When I went to update kernel using the slow UI, I get the following message:

"Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 144, Message: ftp_put(/var/www/html/fog/service/ipxe/bzImage_tst): failed to open stream: No such file or directory:

I have made sure my TFTP username/password are set correctly in all locations.

I am using Ubuntu 14.04, running trunk 7180.

Please help!

@Wayne-Workman I am getting the same issue as well. I have ensured that the TFTP username and password are correct, but I get the same error. Cannot update kernel and my kernel version does not show, same as @jes6309

@danilopinotti I have noticed that if this is an existing host in fog already, if the Active Directory settings were already applied, both of the passwords will not be in the host. You have to de-select active directory/update/recheck active directory. Then, both password fields will be populated.

@Varion Try using a different boot file other than default.ipxe. Try using undionly.kkpxe, or if your are using newer UEFI devices, try ipxe.efi.

I have run into this same exact issue but on a much smaller scale. I had the bios settings set right with the right boot order and everything.

What I ended up doing was change the BIOS settings anyway to remove PXE boot as an option, boot the computer up once, reboot, enter BIOS and change settings back. After that, it worked like a champ.

On your large scale issue though, it almost seems like a port issue on the switch, or perhaps an DHCP scope option not pointing to the right boot file/boot server.

Since moving to trunk 6124 from version 1.2.0, our FOG service no longer responds to changing names from within FOG.

Previous way it worked was to change name in FOG, then within a minute, the computer would reboot, change the name, reboot, join domain. All this would happen automatically.

Now, you have to manually reboot several times in order for this process to happen.

Thanks for all your help. I hope so as well.

I can say that I added the kernel argument in my environment just now, and I am now able to image Surface Pro 4s. It would be nice if this was a built-in argument, as I had to manually create the host first, add the argument, then was able to get it to work.

Cool. Thanks. Will do!

By default, we are using kernel 4.4.0 on SVN 6124. When we try to capture an image, we get an error that states “No Network Interfaces Found (verifynetworkconnection).”

We have successfully imaged Surface Pro 3s in our environment.

I have tried several kernels (including the latest 4.4.1) and different boot files (ipxe.efi, snp.efi, snponly.efi, etc.) with no luck.

When I run a FOG compatibility check, it fails on network and tells me to try a newer kernel
I am using the certified Microsoft Surface Ethernet adapter. Any advice? It’s got to be a kernel issue.

@george1421 I have a few different kernel version. By default, we use 4.4.0. I have also downloaded 4.4.1, and a few different 4.3.x.

Good news is, it is all of a sudden working today. No idea what the deal is, but I was able to image my laptop.

Seeings how I am the FOG admin and the network admin, not sure what is different as I have not changed anything, but at least it works now. Thanks!