@TomBagley said in Fog Boot Menu only works once:

@Wayne-Workman said in Fog Boot Menu only works once:

@TomBagley said in Fog Boot Menu only works once:

@Quazz said in Fog Boot Menu only works once:

@TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

My networking manager has explained that the Fog Server and clients are on a Vlan completely separate from the rest of the network. Could this still be interfering?

Thanks Quazz,
Tom

Depends on if the totally seperated vlan is being served DHCP or not.

That’s done it - solved! Thank you ever so much! Time to slap my network manager for not blocking the DHCP

Have a nice evening guys.

Tom

Hi Wayne,

The NFS Server Service was stopped for whatever reason.

Just in case anyone stumbles across this.

I checked it with: systemctl status nfs-server
Started it with: systemctl start nfs-server
Then set it to always auto-start after boot with: systemctl enable nfs-server

Picked up off another thread which I should have read first!

Thanks for your help much appreciated.

Regards,
Tom

Hi, apologies the bios on the laptop needed flashing to allow the adapter to function. We now have Inspiron’s booting to the fog menu - what a pretty sight!

Thank you for your guidance, brilliant as always.

Tom

Hi,

I am currently running into the issue of USB Nics passing duplicate mac addresses to laptops.

I saw a potential solution discussed here: https://forums.fogproject.org/topic/5743/sharing-nics-between-laptops/8 using the WiFi macs.

Is this still the best practice at present or has there been any further developments? If we are registering them with their WiFi Macs how would Fog know which image to deploy when connected back up with the USB nic?

Running Fog 7492 and it is brilliant.

Thanks,
Tom

@Tom-Elliott It did Tom, thank you.

@Tom-Elliott Hi Tom do I need to capture a fresh image after running that? Re-imaged and got the same message.

@Quazz Hi Quazz, seems to I’ve just reset the surface and it’s gone through the process and come back to OOBE without a problem.

@UniSuperBox Hmm that’s interesting. It boots absolutely fine, if I hadn’t caught the error message I’m not sure I would have known.

Server

• FOG Version: 1.4.4 SVN 6077
• OS: CentOS7

Client

• Service Version:
• OS: Windows 10

Description

Hi,

Just testing out deployments to a surface pro 4. I have captured a basic image from the Surface (just created a local user on the machine to get to desktop, no sysprep). When I deployed back to the surface all seemed OK until the end where I got the 'Failed to set disk guid (sgdisk -) (restoreUUIDInformation) error.

My d1.original.uuids file for the image contains:

/dev/nvme0n1 b1f3ace2-8663-4e88-98b9-018c60d0b6a3
/dev/nvme0n1p1 1:FE2F-E040 1:addec0c6-0546-46f6-8789-1b9002a30019
 2:72ce68c9-8ff5-4eaf-8197-ed86e5e8752e
/dev/nvme0n1p3 3:4A44EC6844EC5869 3:365e62e4-e5e5-4408-bc88-26e9f291bd3f
/dev/nvme0n1p4 4:0C42EEA242EE902E 4:453f2067-0e0b-4fd2-b61e-ff5026dce0a0

Could you assist?

Thanks guys,
Tom

[0_1496679782646_fog.log](Uploading 100%) ##### Server

• FOG Version: 1.3.0-RC-8
• OS: CentOS 5

Client

• Service Version: 1703 * OS: Win10

Description

Hi,

Today one of my users alerted me to the fog needs to perform maintanence popup on his machine and advised that it had rebooted. It then proceeded to continually reboot his PC several times and in the end I’ve had to disable the service to allow him to work.

His PC name does match what the fog database holds and apologies I don’t understand the fog log enough to comprehend why it’s creating the reboot task although there seems to be an authentication error.

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 05/06/2017 16:36 Client-Info Version: 0.11.5
 05/06/2017 16:36 Client-Info OS:      Windows
 05/06/2017 16:36 Middleware::Authentication Waiting for authentication timeout to pass
 05/06/2017 16:38 Middleware::Communication Download: http://10.10.60.10/fog/management/other/ssl/srvpublic.crt
 05/06/2017 16:38 Data::RSA FOG Server CA cert found
 05/06/2017 16:38 Middleware::Authentication Cert OK
 05/06/2017 16:38 Middleware::Communication POST URL: http://10.10.60.10/fog/management/index.php?sub=requestClientInfo&authorize&newService
 05/06/2017 16:38 Middleware::Response Success
 05/06/2017 16:38 Middleware::Authentication Authenticated


 05/06/2017 16:38 Bus Registering ParseBus in channel Power
 05/06/2017 16:38 Middleware::Communication URL: http://10.10.60.10/fog/management/index.php?sub=requestClientInfo&mac=B0:83:FE:90:FE:90||00:00:00:00:00:00:00:E0&newService&json
 05/06/2017 16:38 Middleware::Response Success
 05/06/2017 16:38 Middleware::Communication URL: http://10.10.60.10/fog/service/getversion.php?clientver&newService&json
 05/06/2017 16:38 Middleware::Communication URL: http://10.10.60.10/fog/service/getversion.php?newService&json

 05/06/2017 16:38 Service Creating user agent cache
 05/06/2017 16:38 Middleware::Response Invalid time
 05/06/2017 16:38 Middleware::Response No Printers
 05/06/2017 16:38 Middleware::Response Module is disabled globally on the FOG server
 05/06/2017 16:38 Service Initializing modules

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 05/06/2017 16:38 Client-Info Client Version: 0.11.5
 05/06/2017 16:38 Client-Info Client OS:      Windows
 05/06/2017 16:38 Client-Info Server Version: 1.3.0-RC-8
 05/06/2017 16:38 Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 05/06/2017 16:38 Client-Info Client Version: 0.11.5
 05/06/2017 16:38 Client-Info Client OS:      Windows
 05/06/2017 16:38 Client-Info Server Version: 1.3.0-RC-8
 05/06/2017 16:38 Middleware::Response Success
 05/06/2017 16:38 TaskReboot Restarting computer for task
 05/06/2017 16:38 Power Creating shutdown request
 05/06/2017 16:38 Power Parameters: /r /c "TaskReboot" /t 0
 05/06/2017 16:38 Bus {
  "self": true,
  "channel": "Power",
  "data": "{\r\n  \"action\": \"shuttingdown\"\r\n}"
}
 05/06/2017 16:38 Bus Emmiting message on channel: Power
------------------------------------------------------------------------------

 05/06/2017 16:39 Main Overriding exception handling
 05/06/2017 16:39 Main Bootstrapping Zazzles
 05/06/2017 16:39 Controller Initialize
 05/06/2017 16:39 Zazzles Creating main thread
 05/06/2017 16:39 Zazzles Service construction complete
 05/06/2017 16:39 Controller Start

 05/06/2017 16:39 Service Starting service
 05/06/2017 16:39 Bus Became bus server
 05/06/2017 16:39 Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 05/06/2017 16:39 Bus Emmiting message on channel: Status
 05/06/2017 16:39 Service Invoking early JIT compilation on needed binaries 

I know I’m far from on the latest version of fog so if you suggest I update I certainly will. Just looking for assistance reading the fog log.

Thanks as always,
Tom

@Wayne-Workman I changed the IP address to conform to our new networking structure and ran the tool which worked a charm. My Fog server has now sprung into life and is functioning as it was before the move so it must have been a network setting at our end that was causing the malfunction to begin with!

Thanks for the help as always really appreciate it.

Tom

@Wayne-Workman Thanks Wayne I will try that and let you know.

Hi,

I’m able to PXE boot if I roll back my Fog Server to a checkpoint when I first completed the build which does suggest I’ve changed something inadvertently.

I’ve only updated one image since this checkpoint so if it sounds sensible I’ll look to export the newest image, roll the server back and then import the newer image.

Tom

Hi,
Thanks for the responses. I have left the IP address the same although there is a wish to rebuild and change it to fit inline with our new network structure so that script is going to be extremely useful to me.

Having said that there’s a possibility it was changed from it’s usual IP and then back to it so do you feel it’s still worth running the updateIP tool?

Tom