@Tom-Elliott
Strange. What’s even weirder is it started working once I entered into a forum thread… Now it’s working fine. LOL!
For what it’s worth, I’m running Ubuntu 19 and the Chrome Browser…
I’m OK with it since it’s working now. Can’t explain it though! Ha!
Thanks Tom!
@phishphan Did you read this? Looks similar to what you’re experiencing.
I ran into the same issue with FOG version 1.5.4. But I believe it was due to the BIOS setting and not FOG specifically. We have several HP laptops in our district that have SSD drives and or mechanical drives. I use the same image on all of them. The only thing I do differently is I sysprep them first.
My procedure is to sysprep all of my machines before I capture the HOST image. Sysprepping certainly has helped insure that you don’t have any issues with deploying images to host machines with unlike hardware. I know sysprepping or not will get into a huge debate. But it hasn’t hurt any of my images.
If you are able to deploy just fine to another host, I would think FOG is working just fine and it’s a setting issue within your BIOS.
@Wayne-Workman Any thoughts?
I just remembered the issue we had dealt with the the setting for the SATA operation in the BIOS. If that doesn’t match from machine to machine it will fail.
You might check those things out.
It definitely sounds like the drive is functioning correctly and that it is a setting issue. I have been able to push SSD images to mechanical and vice versa with Windows 10.
I experienced the same issue last year but was able to resolve it.
Check your BIOS settings. Make sure that it’s set correctly for the new SSD drive. I had an issue with that.
What’s the OS on the HOST you are trying to re-image?
What version of FOG are you using?
What version of FOG Server are you on?
Did you use sysprep before you captured the original image?
Hi Tom,
Here is the example of the issue. I actually was able to get to the search feature another way. I had to go into a forum and then I could search.
Thanks!
What exactly did you end up doing to fix this? I am experiencing the exact same issue with my installation.
I"m running Debian 9.9
FOG 1.5.5
Thanks!
Cheers!
Hi all,
I just noticed that the search feature on the forum is not working. It says page not found when you click on the magnifying glass to search.
Thanks!
I was recently asked to give a presentation on FOG by one of the State tech groups (in education) I am involved with in Montana. We have a strong Linux / Mac community here. They are very open source driven and many of the districts here use FOG. Many would like to make the jump into FOG but haven’t taken the leap. I may end up giving a talk here this summer.
I like the idea of setting up a server on a VM. Creating a host image and pushing said image to a new host.
Off topic – At a recent event one of the presenters did a presentation on PFSense. He actually set things up from the ground up. That’s how the conversation arose for me to do the same thing but only with FOG at the State conference.
Good luck!
@astrugatch
Thanks for the input!
@george1421
Thanks for that info. I’m looking into setting up a server with MDT on it. Hopefully that will help these issues.
Hi all,
I’m curious what others are doing for keeping their images up to date. I have noticed an issue with Windows 10 and not allowing to update in Sysprep / Audit mode. I can get my images up to 1709 and that’s as high as I can go without resealing Windows. I would rather create an updated image and just push the entire updated image instead of having hundreds of computers downloading updates all the time.
Also we use Deep Freeze on our publicly used PCs. The Windows 10 updating is a PITA with those. I was hoping I could pull a new image every couple months to keep them updated but that’s looking to be difficult.
What are you doing to handle Windows 10 updates? Is everyone just using WSUS?
Thanks!
Cheers,
Joe
You are a trooper! We certainly appreciate all of your contributions to the FOG project. I agree with @Sebastian-Roth , take some time for yourself buddy. You have been an amazing asset to the FOG project. I don’t know how many times you have bailed me out in the past. Get settled in and get your life in order first. Thank you for making FOG what it is!
Best of luck with your new en-devour!
@Sebastian-Roth
It’s doubtful it is directly linked to FOG. I believe it has to do with SYSPREP…
To update this:
We were able to isolate 2 registry entries that were causing the issue. The entries were for the DVD drive itself. Windows 10 was not recreating these entries after it ran sysprep and installed the new devices on the host system.
I have since ran a fresh install of Windows 10 on a separate machine (similar hardware). The DVD issues were not apparent after the fresh install. We were able to create new registry entries for the DVD drive based on the ones on the “good working” install of Windows 10. I was able to merge those registry keys onto a non-working Host. After that I removed / added the DVD drive. WIN10 recognized the DVD drive. DVD drive stayed installed after reboot. FTW! Hopefully that’s the fix for the rest of the machines we have with the issue.
Thanks for the moral support. Sometimes that’s all we need!
So, we have ran into an issue with multiple types of laptops and desktop computers that we have imaged using FOG and sysprep, where the DVD drive disappears or shows up in Device Manager with an exclamation point on it. This occurs no matter whether the machine is the same as the original host. On all devices, the OEM does not have any drivers available for the DVD ROM, as Windows 10 is supposed to recognize the device. You can remove the device from device manager and let Windows find it. When you reboot the device, the issue is right back again. This problem only seems to be on sysprep imaged Windows 10 machines. We have rolled some of these devices back to Windows 7 and the problem disappears.
We have followed this websites advice (many of these have been found on other websites as well including many from MS…):
https://www.easeus.com/backup-utility/cd-dvd-missing-or-not-showing-up-in-windows-10.html
Has anyone else experienced this issue?
Thanks!
Multicast fails to start on hosts… Again. I resolved my other issues. I purged php from my server and re-ran the FOG installer. Now I can see multicast sessions appear on my server just fine.
I followed:
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_Downloading_-_Multicast
And successfully sent my laptop the fogsettings file. Nothing else multicast seems to work.
Any help is appreciated. Thanks!
@tom-elliott
OK that would make since. I’d say that is not an issue.
I was jumping back and forth from 1.5.4 to 1.6 yesterday trying to get some kind of stability. Currently I’m on 1.5.4 and have moved on to other projects. But… Would love to get things going again to multicast. PM me if you have any ideas please.
Thanks!
I went to check out the serviceconfigurationpage.page.php in /var/www/html/fog/lib/pages/ directory and did not find the file. It appears that the code should be pointing to serviceconfigurationpage.class.php.
root@fog-server:/var/www/html/fog/lib/pages# ls
clientmanagementpage.class.php imagemanagementpage.class.php reportmanagementpage.class.php storagemanagementpage.class.php
dashboardpage.class.php index.php schemaupdaterpage.class.php taskmanagementpage.class.php
fogconfigurationpage.class.php pluginmanagementpage.class.php serverinfo.class.php usermanagementpage.class.php
groupmanagementpage.class.php printermanagementpage.class.php serviceconfigurationpage.class.php
hostmanagementpage.class.php processlogin.class.php snapinmanagementpage.class.php
You can mark this one solved.
I deleted ALL power management entries. (Regardless of seeing any listed.) I haven’t had any hosts shutdown since.
Thanks again!