Unable to check in
-
I updated to 1.5.10.1688 and attempted to capture an image. Win 10 resizable whole disk. It captured the main partition then failed at some point. I couldn’t see the error on the screen. The drive is now too borked to boot into Windows. So I tried to deploy an image I took before the update to the PC but was unable to check in
An idea on how to fix?
-
@Fog_Newb Can you provide your http/php error logs?
See my signature for locations (or very similarly close to)
-
-
Some additional info. I believe I was able to successfully capture an image of this PC right after updating to 1.5.10.1688. on Aug 26th. I am restoring a back up FOG from that time to a new VM to see.
UPDATE: So I restored the FOG server back up from a couple of days ago to a new VM and yes, I was able to back up the PC once after updating to 1688.
-
@Fog_Newb I don’t know how to replicate the problem you had unfortunately, but I believe I made a fix for the issue you were having. The function is expecting the parameter to be a string, and we were sending a null. I’m now going to have it send in an empty string instead which should prevent that problem moving forward.
Thank you.
I still wish I could get you to look at 1.6 but I understand the hesitation
-
@Tom-Elliott Hi Tom, Thanks… I updated to 1.5.10.1692 and was able to deploy a 2 day old image to the PC. I updated some things on the PC, mostly with Steam and display settings then went to capture an image from it again and ran into the same problem mention in the OP. Only this time, I was able to take a pic.
I ran chkdsk prior to capturing and it came up clean
