Posts made by K.Hays

@george1421 That sounds like no good. What’s available for me to try next?

@george1421 I did use both pxe files

@george1421 more in depth, what happens is: No matter what i click it gets to the point where it says “Init.xs… ok” Then it jumps back to the main fog screen, but plain black background and white text. There is also no highlight showing me what i hover over, and after a while of sitting at that screen it says

http://x.x.x.x/fog/service/ipxe/refind.conf... ok
http://x.x.x.x/fog/service/ipxe/refind.efi... ok
Could not boot: Error ox7f048283 (http://ipxe.org/7f048283)
Could not boot: Error ox7f048283 (http://ipxe.org/7f048283)
Chainloading failed. hit 's' for the iPXE shell: reboot in 10 seconds

@george1421 So i was able to get to the fog menu with the assistance of the flash drive, but from there anything i try to do with it fails. Also the firmware is up to date.

@george1421 said in UEFI-PXE-Boot (Asus t100 Tablet):

\EFI\BOOT

Yep, that worked to get to the menu with the ipxe.efi file. So then what next?

@JJ-Fullmer Also i had not tried your guide yet, i was wondering if there was an option other than that (since it had gotten further) but it seems like that is not the case

@Tom-Elliott So far we’ve tried ipxe.efi, snponly.efi, intel.efi, realtek.efi. That’s just today so far.

So its been almost a year now, but as summer maintenance is coming back up, these tablets are in question again. I was going to try what @JJ-Fullmer suggested, but i thought since it’s been a while ill try it normally once more. What i found was that it got to the point where it says “succeed to download NBP file” and then it proceeds to boot to windows. So it did connect to the fog server now.I would love to be able to do these without having to purchase several hubs/adapters/usb drives for the ability to have a good group going at once. If that’s what it comes to though, so be it. Also if it would be best to open a new topic, just let me know. Thank you!

Since it’s been a while here are the specs on the server
Fog Version: 1.4.0 - RC - 13
Ubuntu 16.04

@Wayne-Workman I was able to figure this out, i should have mentioned this sooner but it can be marked as solved. At the time we were having trouble with the client.

@JJ-Fullmer Thank you for the reply! Even after it’s been so long haha. I’ve been meaning to come back to this but it isn’t necessary for me until a break when it’s time to maintenance these computers. I will definitely try this when the opportunity arises. I did try to PXE boot one the other day and noticed that it got further than it had during the time this post was made. It still did not work and I didn’t pursue it any further, but with your guide it seems hopeful! Thank you again!

Server

• FOG Version: 1.3.0-RC-10
• OS: Ubuntu 14.04

Client

• Service Version: 0.9.12 (although it varies)
• OS: Windows 7

Description

The problem im having here is the client is not auto updating on any of the client computers. I do have the settings enabled on the fog server. Below is what is what i found that i think is causing the problem.

 9/23/2016 11:35 AM Client-Info Version: 0.9.12
 9/23/2016 11:35 AM ClientUpdater Running...
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=B8:AC:6F:2C:06:D0||00:00:00:00:00:00:00:E0&newService=1
 9/23/2016 11:35 AM Middleware::Communication Response: Success
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/service/getversion.php?client&newService=1
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/client/FOGService.msi
 9/23/2016 11:35 AM Data::RSA FOG Project cert found
 9/23/2016 11:35 AM Data::RSA ERROR: Certificate validation failed
 9/23/2016 11:35 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
 9/23/2016 11:35 AM ClientUpdater ERROR: Update file is not authentic
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 9/23/2016 11:35 AM Client-Info Version: 0.9.12
 9/23/2016 11:35 AM TaskReboot Running...
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/service/servicemodule-active.php?moduleid=taskreboot&mac=B8:AC:6F:2C:06:D0||00:00:00:00:00:00:00:E0&newService=1
 9/23/2016 11:35 AM Middleware::Communication Response: Success
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/service/jobs.php?mac=B8:AC:6F:2C:06:D0||00:00:00:00:00:00:00:E0&newService=1
 9/23/2016 11:35 AM Middleware::Communication Response: No jobs
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 9/23/2016 11:35 AM Client-Info Version: 0.9.12
 9/23/2016 11:35 AM HostnameChanger Running...
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=B8:AC:6F:2C:06:D0||00:00:00:00:00:00:00:E0&newService=1
 9/23/2016 11:35 AM Middleware::Communication Response: Success
 9/23/2016 11:35 AM Middleware::Communication URL: http://10.20.0.9/fog/service/hostname.php?moduleid=hostnamechanger&mac=B8:AC:6F:2C:06:D0||00:00:00:00:00:00:00:E0&newService=1
 9/23/2016 11:35 AM Middleware::Communication Unknown Response: Not Allowed Here```

@Wayne-Workman Ok ill be sure to look for that in the future. Thanks to everyone who helped! Ill be sure too update frequently now haha

@Wayne-Workman That worked! Any idea to what caused this whole thing? Im going to have to update my other servers, and obviously this one in the future and would like to avoid this whole ordeal again haha

@Wayne-Workman that worked, as in it let me in mysql

@Wayne-Workman Access denied for user ‘fog’@‘localhost’ (using password: YES)
d430@

@Wayne-Workman it said unknown host

@Sebastian-Roth That got me further! But when i got to the Updating database schema there is no update option on the web page.

@Sebastian-Roth Im currently on Version 7084, and was trying to upgrade to 1.3.0-RC-8.

@Sebastian-Roth

The script you are attempting to invoke has been converted to an Upstart
job, but lsb-header is not supported for Upstart jobs.
insserv: warning: script 'friendly-recovery' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `friendly-recovery'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `friendly-recovery'
The script you are attempting to invoke has been converted to an Upstart
job, but lsb-header is not supported for Upstart jobs.
insserv: warning: script 'cron' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `cron'
 * Starting FOG Computer Imaging Solution: FOGMulticastManager
   ...fail!
 * Starting FOG Computer Imaging Solution: FOGImageReplicator
   ...fail!
 * Starting FOG Computer Imaging Solution: FOGSnapinReplicator
   ...fail!
 * Starting FOG Computer Imaging Solution: FOGScheduler
   ...fail!
 * Starting FOG Computer Imaging Solution: FOGPingHosts
   ...fail!
 * Stopping NFS kernel daemon
   ...done.
 * Unexporting directories for NFS kernel daemon...
   ...done.
 * Exporting directories for NFS kernel daemon...
   ...done.
 * Starting NFS kernel daemon
   ...done.

This is the other error log. There is two, one for the new version which i posted below, and one for the old version which is posted here.