OK so what would I need to do to resolve this. I am in another state trying to get the node working so I dont have to touch every machine but cant due to this.

So I’m lost I need it to regenerate or I need to replace with the backed up one

I’m assuming this is the cert? /fog/management/other/ssl/srvpublic.crt

@Wayne-Workman Also where is the cert located in the OS?

@Wayne-Workman So if I rolled back and made a backup of the file then followed Tom’s instructions. Replaced the file after the upgrade should that resolve it?

A little cleaner error:

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 2/29/2016 4:45 PM Client-Info Version: 0.9.11
 2/29/2016 4:45 PM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 2/29/2016 4:45 PM Data::RSA FOG Server CA cert found
 2/29/2016 4:45 PM Data::RSA ERROR: Certificate validation failed
 2/29/2016 4:45 PM 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)
 2/29/2016 4:45 PM Middleware::Authentication ERROR: Could not authenticate
 2/29/2016 4:45 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
 2/29/2016 4:45 PM Service Sleeping for 120 seconds
 2/29/2016 4:46 PM Service Stop requested
 2/29/2016 4:46 PM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 2/29/2016 4:46 PM Bus Emmiting message on channel: Status
 2/29/2016 4:46 PM Bus Became bus server
 2/29/2016 4:46 PM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 2/29/2016 4:46 PM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 2/29/2016 4:46 PM Client-Info Version: 0.9.11
 2/29/2016 4:46 PM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 2/29/2016 4:46 PM Data::RSA FOG Server CA cert found
 2/29/2016 4:46 PM Data::RSA ERROR: Certificate validation failed
 2/29/2016 4:46 PM 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)
 2/29/2016 4:46 PM Middleware::Authentication ERROR: Could not authenticate
 2/29/2016 4:46 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
 2/29/2016 4:46 PM Service Sleeping for 120 seconds```

Now getting this from all clients:

 2/29/2016 6:19 PM Middleware::Communication Response: Invalid host certificate
 2/29/2016 6:19 PM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 2/29/2016 6:19 PM Data::RSA FOG Server CA cert found
 2/29/2016 6:19 PM Middleware::Authentication Cert OK
 2/29/2016 6:19 PM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 2/29/2016 6:20 PM Middleware::Communication Response: Success
 2/29/2016 6:20 PM Middleware::Authentication Authenticated
 2/29/2016 6:20 PM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=B6:AE:2B:EB:6E:CD|00:0A:CD:2A:4D:A6|B4:AE:2B:EB:6F:CC|B4:AE:2B:EB:6F:CD||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1
 2/29/2016 6:20 PM Middleware::Communication Response: Invalid host certificate
 2/29/2016 6:20 PM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 2/29/2016 6:20 PM Data::RSA FOG Server CA cert found
 2/29/2016 6:20 PM Middleware::Authentication Cert OK
 2/29/2016 6:20 PM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 2/29/2016 6:20 PM Middleware::Communication Response: Success
 2/29/2016 6:20 PM Middleware::Authentication Authenticated
 2/29/2016 6:20 PM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=B6:AE:2B:EB:6E:CD|00:0A:CD:2A:4D:A6|B4:AE:2B:EB:6F:CC|B4:AE:2B:EB:6F:CD||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1
 2/29/2016 6:20 PM Middleware::Communication Response: Invalid host certificate
 2/29/2016 6:20 PM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 2/29/2016 6:20 PM Data::RSA FOG Server CA cert found
 2/29/2016 6:20 PM Middleware::Authentication Cert OK
 2/29/2016 6:20 PM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 2/29/2016 6:20 PM Middleware::Communication Response: Success
 2/29/2016 6:20 PM Middleware::Authentication Authenticated
 2/29/2016 6:20 PM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=B6:AE:2B:EB:6E:CD|00:0A:CD:2A:4D:A6|B4:AE:2B:EB:6F:CC|B4:AE:2B:EB:6F:CD||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1```

@Tom-Elliott Worked like a champ, thank you as always

@Tom-Elliott Trying now.

Getting the following which led me to do this in the first place:

Was getting cert errors on some clients.

Also rolled back and tried it again and it did the same thing.

trunk 4909

Was able to update node without issue. When I update master to 4909 it wont allow Apache2 to restart. Reboot doesn’t help. Any ideas?

@Wayne-Workman I think I am not explaining it right, from the surface upload I am getting everything I need. I was able to restore it back to factory orig with eh captured image.

My custom image doesn’t have a EFI partition due to it being loaded form ISO. So in normal Windows install there is the System partition that has stuff in there to allow for the machine to boot. I will be pushing the EFI files to there to see if I can make a hybrid solution.

@Wayne-Workman I am using that now, it isn’t the image it is the device, so when it boot to the drive it needs the EFI partition in order for the device to continue. I am attempting to insert the files into the system partition on the existing image to see if it will pick those up.

OK imaging did image to the device, however, it does need the EFI parttion or it will not boot into the Surface so far as I can tell.

I have tried changing the host EFI Exit type to all different options no change. I will try and see if I can somehow put the partition on there , but I am thinking there will be two different images since the one I made with sysprep and this use two different types of boot partitions.

But to nail the point down the UEFI is on the device not the HDD.

yeah I would say so.

@Wayne-Workman Yeah those are guides for 2s and 3s. I am on the support line with “Bob” at M$. They are checking to be sure. I am sure it will be fine but if I brick a 1700 device my boss my call me bad names. I have gotten the answer direct form them that the UEFI is embedded int eh device not the HDD. So I am good to try now.

@Wayne-Workman I would agree but I want definitive proof before I move forward.

@Wayne-Workman yeah I have done just that with some other software so I would have physical access to it on a USB drive. I’m just trying to find out for sure weather or not I can just boot to a USB flash drive if I was to wipe out that EFI partition on accident

@Wayne-Workman I have no successfully imaged yet, I am afraid that if I image it with my image it will not have the EFI partition nor the recovery partition. If that is needed by the device it might brick it and I will not be able to get back into it.

So this is what I am seeing as partitions:

I am not sure if there is a UEFI section on the board of the device or if it just reads everything off of the disk. If the latter is the case when I put my image on there it wont know what to do. So I am attempting to ad those partitions into my image before I move forward.

I am hoping that if something bad happens I could always just boot from a USB flash drive to reinstall but I am still researching.

This is the Partitioning of my image:

I just added the RAW partition. I have some software here I am going to try and replace it with the partition I pulled off with a quick image form that software. Unless someone has already hit this part and knows a way around it or how to do it correctly.