@astrugatch So I enabled the plugin system in FOG Settings, but the actual webpage for Plugins does not load. Do I have to enable anything else?
Posts made by jveronese
-
RE: Active Directory info gets cleared when joining a host to a group
-
Active Directory info gets cleared when joining a host to a group
So I have a bunch of new desktops that I am working on getting imaged. However, whenever a new host is added to my group for them via Quick Registration it clears the information to automatically join AD, so I have to put it in every time. Is there a way to stop the information from getting cleared when the host is assigned membership to the group?
-
RE: Windows Could Not Finish Configuring the system Error (1809)
I think I hunted down the culprit. I installed each piece of software one at a time and it looks like it is the new cloud version of Sophos that is giving me the error. Removed it from the image and everything seems to have went through without an issue.
-
RE: Windows Could Not Finish Configuring the system Error (1809)
Still having the issue. If it is a driver issue is it possible that the drivers from VirtualBox’s guest additions are the cause?
-
RE: Windows Could Not Finish Configuring the system Error (1809)
Sorry, yes it is Windows 10 version 1809.
I have tried not installing the FOG client at all as well as trying other people’s answer file. I am thinking the issue might be caused by installing Windows ADK, so I am starting from scratch to see if that is where the issue is. Will update if it works.
Thanks everyone!
-
Windows Could Not Finish Configuring the system Error (1809)
Currently running: FOG 1.5.4
So I am trying to build a generic Windows image for the next school year, following the same guides I used to do this last year. However, when the image is deployed through FOG (sysprep and capture look good) I get the error that “windows could not finish configuring the system”. I know this is a common issue with the FOG service (so to be sure I removed the client all together). However, I am still getting this error when Windows is setting up. I was wondering if anyone here had any other ideas what might be causing this issue? Bad answer file maybe and this isn’t a FOG issue at all? Was hoping maybe someone here could help me figure out where I am going wrong.
My answer file
customize .txt -
RE: Cannot PXE boot on new fog server
@tom-elliott Ok, we have a 255.255.252.0 subnet mask. How can I make sure these devices are on the same subnet then?
-
RE: Cannot PXE boot on new fog server
@george1421 Yes, when the device boots into Windows DHCP gives it an address. Both subnet masks are the same, so does that mean they are on the same subnet then?
-
Cannot PXE boot on new fog server
I recently setup a new installation of Fog on an Ubuntu server VM (64-bit) on our VMWare esxi host (5.5). I have it installed and told it to not use the DHCP service through Fog as we have a Windows DHCP server. In the DHCP server I have option 66 set to the ip of the server and option 67 set to undionly.kpxe. However, when I boot to the NIC it spins on DHCP for several minutes before giving up and booting to the hdd. Does anyone have any ideas where my issue might be? If you need logs or additional info please let me know and I will do my best.
-
RE: NTFS is inconsistent error. Cannot get it to image properly
How do I update fog without having to reinstall and recapture all of my images?
-
RE: NTFS is inconsistent error. Cannot get it to image properly
It happens when we deploy the image.
-
NTFS is inconsistent error. Cannot get it to image properly
Server
- FOG Version: 1.3.5
- OS: Ubuntu Server 16.04
Client
- Service Version: n.a
- OS: Windows 10 EDU
Description
So when I try to image some of our HP laptops, it errors out at the end of imaging and gives the error that NTFS is inconsistent and I need to run CHKDSK /F and restart twice. I tried this with a Windows Install USB recovery tools, since fog wipes out windows so I can’t run chkdsk. Even after running chkdsk and restarting twice, the error still occurs. This only seems to be happening to our HP laptops, as our Dell laptops have seemed to image just fined. I have also tried a new HDD and disabling Fast Boot with no luck. Is there any other way to fix this error?