Thanks Wayne. I checked out the log and also communicated some with Tom. I had to update my Active Directory info in Fog for Legacy Fogcrypt and the new password system. All is well now. Thanks!

I found that was wrong, it was one host that was blocked on start on fog without any task pending on it ??
IP 172.19.81.167.

We have to find what host ( there is 800 computers in school) without having his hostname.

I have to compare export of hosts in Fog with mac adress and the apache log file.

After i have to find in my GLPI inventory where was that netbios name in the school rooms.

The computer failed to start on PXE. I shutdown it too quickly to save the error message.

After shutdown it, i delete again with mysql command blank images and fog runs fine again.

Thanks for your help searching in apache log ! i understand how it works now.

@Tom-Elliott
OK

Thanks a lot for your help. I think I need to expend some time looking for the best solution here. I will update the thread with progress.

@gwhitfield said in FOG service on 0.10.6 not restarting after reboot:

demon ninja gremlins

We are certified demon ninja gremlin dispatchers.

@Stilty update, and all should work hopefully.

Updated to the latest trunk release on the SVN and had to run the SQL commands listed here:
https://forums.fogproject.org/topic/7734/snapin-id-was-not-set-or-unable-to-be-created-svn-revision-5661/27

After that, it started working great.

Thanks for the help, guys!

@Tom-Elliott Fixed as of 5772. Thanks Tom!

@alexwarren That is an Ubuntu 14.04 change that caused FOG to change to use the /html/fog

no it’s not an issue right now. For me the path looks strange with the double slash and I was not able to figure out why it’s always like this after upgrading the trunk.
So then the thread can be closed. Thanks

@george1421 Even though the machine “seems” to be connected to the domain after reimage, I always remove and readd the machine to the domain.

On my current “problem” I had to use the manual complete reset method to get Windows Update working again. And I’m still not sure because it’s “Checking for Updates” on 2 years worth of updates.

@Wayne-Workman: Fog version 1.2.0. Linux CentOS 6.7 server, Windows 7 SP1 Workstation clients.

@MRCUR: I am using WSUS. But, points at george1421. Each Workstation image will only be restored to that Workstation with a new same model hard drive. The impression I always got was that sysprep wasn’t necessary in my case.

You can do it manually for now. You CANNOT use the new inits with 1.2.0, if you download those and place them, no imaging will work at all. Just try the new kernel and keep a copy of your old kernel incase it bombs. Link here for steps:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

Make sure you pay attention to the old file name before moving it - I think 1.2.0 was 32 bit. The kernel bit has to match the init bit.

@Tom-Elliott Thanks Tom. I’m not really sure what the issue was with Centos 6.7. Iptables was disabled, SELinux was disabled. It didn’t throw any specific error messages and nothing in any of the logs caught my eye.

Either way, Wayne’s suggestion to move to CentOS 7 worked and I now have the trunk up and running. Thanks for the help folks!

@Tom-Elliott

Fixed in r5767. Thanks

cross linking post same issue, by same OP: https://forums.fogproject.org/topic/7926/fog-won-t-finish-capturing-a-windows-10-image

Upgraded from v1.12 and not all storage nodes were up or had the correct id/password combination. Removing old storage and fixing credentials fixed this. In the previous version snapins did not validate the fog user.

That’s good news. That video pretty much answered all my questions. Thanks a bunch.

@plegrand
No worries!

@Joe-Schmitt

Makes sense, and I had suspected as much.

Thanks!

PS snapin if anyone needs it.

Start-Transcript -path c:\SnapinLogs\CleanupUpdaterLog.log $strFileName="c:\program" If (Test-Path $strFileName){ Remove-Item $strFileName } Stop-Transcript

This is because 1.2.0 had no support for windows 10 as it didn’t exist during 1.2.0’s release. The only way, that I’m aware of, to get Windows 10 to image is to use Multipart Non-resizable. That said, Trunk versions of fog will run without much issue.