@george1421
I can post any logs, if you’d like. Multicast does complete. The image just does not function. I was out sick the last couple days. I’m back at it today. I’m hoping to get my new image done here this week. We’ll see.

@george1421

I believe I have already done this.

@george1421

That is correct.

@george1421
I wanted to report in on my findings… I tested things again and I can indeed push images via Unicast with my current image. I am currently pushing a lab of computers now. Unfortunately this isn’t very efficient.

So I have set up a Windows Server 2016 with MDT and ADK installed on it. I am in the process of creating a golden image with that… I’m hoping by mid-week I will have a new image to use.

Let me know if you’d like to see any log files or if you want to remote in.

Thanks!

@george1421
Well I’m taking off for the weekend. This can wait until next week. The results from re-imaging was not successful. It still fails via multicast but does succeed via unicast.

I’ll touch base with FOG on Monday.

Thanks!

@george1421
I am re-running my AHCI image on some of the problem machines to verify that it does indeed fail on multicast. It should be done in about 10 minutes or so. I’ll post back when I find anything.

@george1421
Thanks for explaining MDT. I will have to look into it. I’d love to only have one golden image for everything.

So I think I figured one of my issues out… The SATA Operation in BIOS/UEFI was set to AHCI on some and ATA on others (two separate labs). The ATA image will not work on the AHCI image. That makes since now.

To answer your questions - The model computers are identical. They are SATA SSD’s. The drivers are correctly installed on the master image.

Now, I have since taken an image on the AHCI clone and it still does not multitask to the problem lab.

@george1421

I do have a single WIN10 image created in Audit Mode and re-armed prior to pulling an image.
I can deploy this image to HDD drives OK with Multicast.
I cannot deploy this image to SSD drives with Multicast.
I can deploy this image to SSD drives with Unicast.

I have since tried to create a new image specific to the SSD drive machines. This has also blue screened during Multicast only.

Please forgive me as Windows 10 is a new environment for me. I primarily have worked in Win 7 and Unix/Linux. I am not familiar with Bitlocker but I can say nothing is encrypted on our drives.

I am also unfamiliar with MDT. After Googling that I see what it is. Is that easier to use than fooling with Sysprep? Does it provide the same thing?

Thanks!

@george1421 Any ideas here?

Thanks!!

@joe-schmitt
I see. I did discover a BIOS/UEFI setting on this lab model that does not allow the computer to completely go to sleep. This may at least let me invoke shutdown or WOL. We’ll see. Otherwise, I can always use CRON to set the shutdown settings after things have been updated.

Thanks again!

@Joe-Schmitt

Just one quick observation… If a host is asleep when it receives the shutdown command, set to perform immediately, is it supposed to shutdown? Mine are not. What’s the best solution to shutting down hosts that are asleep? I usually end up just doing this manually but their has to be a simpler way.

Thanks!

That error code appears to be caused by a problem with the MBR…

https://answers.microsoft.com/en-us/windows/forum/windows_10-performance-winpc/windows-10-error-code-0xc000000f/765e013a-f3d0-472b-a92f-2f0ec14b0e6c

This image was sysprepped.

Thanks!

I just made the switch over to WIN10 in our district. I just got finished making my sysprepped images for WIN10.

I followed: https://forums.fogproject.org/topic/9877/windows-10-pro-oem-sysprep-imaging

I was able to successfully push my image to a lab full of computers. Everything looked to be going so well. I tried pushing my image to another lab full of identical computers (minus SSD drives) and received the following message on boot up…

I tried pressing Enter or F8 and it fails with this same message…

I tried re-doing my image on one of the lab computers with the SSD drive and that failed with the same message. I can push this just fine via Unicast but it will not Multicast.

Any suggestions here?

Let me know which log files to upload and I will gladly post them. Thanks!

@Joe-Schmitt I apologize. No problems here. I jumped the gun. I made the change on the server last night and updated a lab of hosts. They didn’t shut off, after checking back in to the server, so I assumed it was an issue. I could see on the log where the server made the call to power off the machine but nothing happened. So I powered them off manually. I assumed that their was an issue. I just retested things and they seem to be working just fine. It appears that I was just caught in the delay of things updating, yesterday.

Thanks for making me look at this one more time.

FOG Server - 1.5.4
FOG OS - Debian 9.4
FOG Client Ver. - 0.11.16
OS - Windows 10

I noticed that our Windows 10 clones do not respond to FOG’s request to shutdown via the Power Management feature in the FOG Client. I verified that both settings were set to allow FOG to manage settings for Power Management (globally and per host). I also checked the machines FOG log and it shows it pull the request to shutdown the computer but nothing ever happens.

Any suggestions are appreciated!

@george1421
As always, I appreciate the help! I am happy to help out where I can.

@george1421
Yes php-fpm is off currently. I am going to leave it that way for a bit. I may play with it more later this Summer but for now I’m leaving it turned off.

What would happen with mine, when php-fpm was turned on, was it would appear to be working OK and then bomb out when I ran a multitask session. Most of the time, if I ran a single task here and there, things would be OK. As soon as I threw something that was memory intensive, things would crash.

Glad we’re up and going again. I imaged two labs and didn’t have any problems with FOG.

@george1421
It is Debian 9.4.

And so far everything is working just fine since the change. I’ll let you know as time goes. But so far so good!

Thanks again!

@george1421

I have several tasks I will be running this afternoon. I will report back as to whether this fixed things. Previously, the issue would come back and haunt me after more than one multitask session.

Thank you for the help!!!

As soon as I commented out the setting in SItes-Available, things worked.