@austinjt01 Ok that is a great starting point. I’ll again refer you to my tutorial: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed Look at the fog.custominstall script. Start with that script and then in this section add your code: echo "Done" debugPause . ${postdownpath}fog.copydrivers # . ${postdownpath}fog.updateunattend umount /ntfs Remove the call to the fog.copydrivers and fog.updateunattended and insert your code. At this point in the code /ntfs has been mounted onto the windows (C: drive) partition, wherever it may be. The script takes into account nvme vs sata as well as partitions being in different order or locations.

@gwhitfield said in FOG service on 0.10.6 not restarting after reboot: demon ninja gremlins We are certified demon ninja gremlin dispatchers.

Perhaps I should expand. This is what I did up to v1607. My sysprep answer file sets autologon of Administrator for 99 times. It enables the Administrator account and has the password included (hashed by sysprep). It also includes a FirstLogonCommands to run a cleanup script. That cleanup script performs the first part to remove security, rewrites the RunOnce registry value, then restarts the computer. Because the RunOnce registry value was recreated, the auto logon of Administrator launches that script again to perform further functions. After 3 more restarts the script turns off autologon, does not rewrite the RunOnce, re-enables security, then shuts the system down. With v1709 I changed how I harvest driver files and have been able to install all drivers without the need to dumb down the security. I now install all general drivers from setupcomplete.cmd .

@Tom-Elliott The group settings change in the update fixed the problem! Thanks!

@aksl Are keen to get your hands dirty and dive into “compiling and debugging iPXE”?? If yes is your answer, there is a way I could lead you.

@Sebastian-Roth that’s good news! I can test it out once it’s wrapped in. I tried what John did, but didn’t have any luck. Also tried following the wiki post on HTTPs/custom certificates that you shared in the other thread, but was still getting the overlength error. I decided to just use the certificate that FOG creates on install instead of my custom one for now.

@SaxxAppeal Hi. I would love to get the Fog server Vm. Can you share a link to download the .Vdi? Thanks to all at this forum.

@Tom-Elliott Thank you! I can confirm this fixed the issue. Snap-ins are deploying successfully and the tasks are clearing.

THANK YOU GILOU!!!

@george1421 Wouldn’t Know How To check if it’s in the repo, but I can give it a shot almost home.

FOG and Windows 8/8.1 can work with the UEFI default of 4 partitions (Partition 1 usually being the Protective MBR, Partition 2 being the Recovery, Partition 3 being whatever it is microsoft decided it to be, and Partition 4 being the main data partition) This is what is typical of a default Windows 8/8.1 install with UEFI enabled. Yes, the file system is also structured in GPT which also should work fine. Under the Default Windows 8/8.1 setup, with UEFI enabled, the only requirement before an imaging task occurs is to disable Secure boot, and re-enable it once the imaging task is complete. Maybe you could try the latest and greatest in SVN to see if it may help you with the default partitioning scheme done by the Lenovo installation disks? I’ve try to make as dynamic as possible and rely purely on the disk layout scheme over specifically telling the HDD where and what partitions to place.

Hello, I’ve upgraded to SVN 2906 and this problem is resolved. I now see a sensible page if I call up the login history. Thanks Alasdair

@jeremyvdv I’m sorry I don’t have a good answer for you. With the fog server max clients at 0 and other nodes greater than 0, the code should use the available storage nodes and not the FOG server for image delivery.

@SeqSupportEdkey please see @brianjones2007 's request. Brian, you might want to head over to iPXE and look for a guy named Micheal Brown… Or you could further elaborate your problem here and we will do our best to assist. It may be something that we know the solution to… sometimes it works that way.

You’re very welcome.

Just wanted to update. I have been busy here at work so I have not been able to do anymore testing on the init files. So sorry for the delay.

@Junkhacker Checking it out! We had to move our workspace around the office… Edit: We got sick interns, colleges on vacations having a hard time scraping time together.

@Towndrunk said in Multicast won't start: Is there any benefit to updating all the time if there is also the potential to have things not work? The benefit - getting a bug you report fixed. Getting bug fixes others report. Updating is totally up to you. Nobody is forcing your hand, and Release candidates are just that. Release candidates. If you want to sit on it, you can. If you want to update, you can. However - if you have issues and ask for help here, and the devs/mods/testers know your issue is fixed in a later RC, we will ask you to update and won’t offer much help with getting your older RC to work, when all you would need to do is update. Of course we’d help with the updating itself if you had problems. But it’s all still up to you.

@Sebastian-Roth @Tom-Elliott After an update to the current subverion it’s working again. Thanks.

@george1421 I’m 99% sure it was the suggestion of something I found on the forums a long time ago, but simply forgot. Like I said, once everything calms down, I’m planning on rebuilding my FOG machine anyways, and blast away old images, especially since I can drop driver packs in now