@dj FOS (name for the FOG system that loads at that point) doesn’t need /sbin/mount.nfs I just checked and tested and it all works fine in my environment. Can you run mount -v | grep images on a system where you were able to mount the nfs share and take a screenshot/paste it here? What Ubuntu version is the FOG server running btw? Did you test the mount in FOS on a system that mount does work in a full linux distro?

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

@george1421 Pffft…i’m there with ya brother. ;)

I was able to remote in and find out what was going sideways with the OP’s system. I’ll fill out the details in a bit, but there is the keys. mods-enabled/php5.conf set handler 9.4 sites-enabled/001-fog.config It appears to be an issue with at least debian 9.4 at the moment where php-fpm wasn’t being enabled causing the sluggish UI and high apache usage.

Based on the information given I’m guessing that you’re missing a driver for the storage controller. Which simply means you need to get the driver and put it on loadable media and load it with the load driver button in the windows install wizard. What are you installing windows on? As in what computer and model (or what the make and model of the storage controller if you know) or if it is a vm, what brand of vm (vmware, xen, hyperv, virtualbox, etc) and what kind of storage controller do you have configured for the vm. For example: If you use Vmware and set the storage controller to SCSI with vmware paravirtual that controller’s driver is not included in windows installers and has to be loaded and would give an error like what you’re talking about. In this case I would add a second dvd drive (you can just use one and swap a driver disk for loading the driver and then swap the installer back, but I find it simpler to just have two drives on a vm) and mount the vmware tools installer iso. If you’re lucky the inf file will be available on the disc, I believe the filename is pvscsi.inf or something of that sort. (I’ve actually exported just the driver infs from a vmware tools installation to make this easier since the infs aren’t always on the install disc. To do this, Install vmware tools on a windows vm with all features of vmware tools selected then use pnputil /export-driver * C:\vmwareDrivers Then copy that folder to a remote server, sort through it to get just the vmware drivers, and turn it into an iso and put that iso in your vmware iso store) Some other cases where this can happen are trying to install windows 10 on older computers where there’s a legacy RAID controller. There can also be legacy chipsets/cpus (if you’re trying to install on something like a Intel Pentium D or older) that would need extra drivers. I can help you find the driver you need if I have more information on what you’re trying to install windows on.

@Kami Can you please boot the client your are trying to capture into Windows and take a picture of the disk management dialog? While you are there make sure fast boot is disabled (a lot of the Windows updates to enable fast boot over and over again).

@timo You can restart apache2, the effects won’t last long though. When you can get into the web gui, you should go to Storage Management -> your storage node -> Max Clients and set this to something like 1 or 2. This will limit how many snapins run at once - and will allow your fog server to operate normally while the snapins run.

You were correct, using DCC is not an option. I did find that by using the CMD prompt and entering bcdedit.exe /enum it will display your working Windows Boot Manager but not the extras. However, if you use bcdedit.exe /enum firmware it will display all the different WBMs, even the faulty ones. I am currently trying to build a script that will remove the false entries.

Here are the log when I try to list scheluded tasks in /var/log/httpd/ssl_error_log [Mon Jun 04 08:24:48 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:27:09 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:36:00 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:47:45 2018] [error] [client 192.168.1.10] PHP Warning: trim() expects parameter 1 to be string, array given in /var/www/html/fog/lib/fog/fogbase.class.php on line 1316, referer: https://fogus.univ-rennes1.fr/fog/management/?node=task&sub=active [Mon Jun 04 14:10:47 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 54, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 14:11:18 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 14:29:39 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 15:18:51 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active Arnaud

@george1421 nope I haven’t because I don’t know that it slows everybody down, and even if it is slow, it’s not broken.

I’m so close to getting this working The only issue now is that i get now is a “no viable macs to issue” I re-ran the installer 15 min ago and that did not help per this thread https://forums.fogproject.org/topic/12006/fog-perform-full-host-registration-no-viable-mac-to-use/5 I renamed the .fogsettings file and re-ran the install still getting No Viable Macs to issue So close yet so far :)

@sutra Sorry for the late reply! Can you provide the contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions? You find those files on your FOG server in /images/Alienware-i9-010618.

I haven’t added such a thing for one main reason. Multicast sessions are intended to be things you’re sitting in front of the systems for. I’ll see about adding a feature like this however as I can see the value in it, and didn’t think much about it 3.5 years ago when I created the session capability. If that tells you how long before, as far as I can recall, anybody asked for such a thing.

@john-l-clark If your image was from a machine that was in BIOS mode and the media to initially install was BIOS media as well, then the image is being deployed to the HDD/SSD with BIOS partitioning and not UEFI boot partitions. In this case the UEFI/BIOS would not consider it a UEFI bootable device (as it has no UEFI boot partition). Presuming your image is whole disk and not a single partition. I have seen posts around about converting images that are BIOS to UEFI, but didnt pay much attention to them. If the process of setting up that machine with a new image isnt too much of a burden, that may be your best bet. Fresh install OS with UEFI settings/media, setup what you need and capture. Hope this helps

Our master server and one storage node is on 1.4.4 the two newer storage nodes, both having the same problem as described, are on 1.5.2 We have had issues in the past upgrading hence the mixed versions. Thanks.

@sherder For me I had similar troubles with Windows 7. I came to 2 conclusions. sysprep + unattend is very finicky. If things are not perfect you get all kinds of odd behavior. The other was that many parts of it seem to not function as they should, the computer name being one of them. The CD key is another, many sites/articles say to use 00000… or XXXXX… repeated, but mine would fail unless I put a valid key in (ended up using the Windows generic install key that MS provides on their site, doesnt activate just gets install done). Are you making your unattend by hand or using a tool to generate it? @sherder said in Windows 10 Unattend file issues: It skips the setup but doesn’t implement the changes that I put in with sed Not clear on the above, could you elaborate what you mean here? When the syspreped image boots back up, are there some things that have been applied by unattend and some that have not, or does it appear to not have applied any changes specified?

@george1421 This is just a very bad guess since I can’t test this at all. net0.dhcp/43:hex = 6010B080FAAAA03C0A802C8C0A80368C0A8016600 net0.dhcp/60:string = PXEClient I’m more confident that net0.dhcp/60:string = PXEClient will work than the the option 43 one. net0.dhcp/43:hex = 6010B080FAAAA03C0A802C8C0A80368C0A8016600 net0.dhcp/60:string = PXEClient set altiris-server:ipv4 10.96.50.15 set net0/next-server ${altiris-server} cpuid --ext 29 && set arch x64 || set arch x86pc iseq ${platform} efi && set plat efi || set plat 0 chain -ar tftp://${altiris-server}/BStrap\\${arch}\\BStrap.${plat} boot || goto MENU

Thanks a lot guys ! Let(s go updating ! :)

I follow with my problem :( I think that the best option is ask this new feature :)