@rstockham23 Sorry but the important information is not on the picture. Usually there is a message in the blue partclone screen which should give is more hints on what’s wrong. When scheduling the task you can set the checkbox for debug and after the error happens you’ll get to a command shell. There you can check the mentioned log file: cat /var/log/partclone.log

@sebastian-roth Here is a new thread: https://forums.fogproject.org/topic/11393/chromium-image-issues-after-updating-server

@rstockham23 I meant reboot once the entire domain process is complete, and then check how long the service takes to startup. (This can be done by monitoring the fog.log by using get-content -wait C:\fog.log from powershell). If there’s an authentication issue again, please post the entire fog.log after you test the reboot.

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!

@Tom-Elliott

This resolved our issues. Thank you for the great support. I now have a working FOG server again; now on trunk. I hope this makes our upgrades to Windows 10 Edu easier over summer break.

Thanks, again!

Again, anything on this?