@george1421 yes

@aziraphale I have to ask you do you use the linux user account fog for system maintenance AND you change the password on that account? If so that linux user account is an internal system account used and managed by FOG. We find that sometimes people will change the password on this account and then capture fails. There is a process to fix this condition if that is what happened.

@amir3161 Are you still interested in this? I’ve lost track of this issue. Or maybe you figured it out yourself?

@Lebowski Did you upgrade to 1.4.4? Does it still throw the error?

@Jphipps Sorry this got somehow lost. Is this still an issue or did you get this solved on your own?

I am marking this solved now as there hasn’t been any response and my guts say that this is not a general issue. Not with FOG and not in iPXE. Possibly this is a very specific hardware related issue but we won’t be able to fix this as there is not much information that we could work on.

@entr0py Tom was saying that there was an issue with resizing in 1.4.4, would you try out upgrading to the latest RC9 version and see if this is solved.

@bigjim Could this be an issue with fast shutdown being enabled in Windows?

@sgwk Sorry, couldn’t find the time and resources to try this out. Anyone having this setup at hand out there?

@msi said in Remove and stop FOG to act as a DHCP server:

[root@localhost dnsmasq-2.76]# sudo make install
/bin/sh: cc: command not found
/bin/sh: cc: command not found
Package dbus-1 was not found in the pkg-config search path.

I am not sure about the dnsmasq stuff but usually there is the magic three steps when compiling software on linux: ./configure, make and make install. Not for dnsmasq?

@msi Did you install dnsmasq as rpm now. Shall we mark this solved?

@natsufiree Please let us know about the current state of this! Will mark this solved fairly soon as George’s suggestions should put you on the right track.

@kvrprasad Any news on this issue?

@CoxM Please post the log as requested or we will close this.

@zingaro Please let us know if you could follow the description in the other post and got it setup on your system as well or if you need any more help with this.

@ENorum Did you give George’s suggestion a try. Please let us know if you could make this work or if you need further assistance with it.

So I am marking this solved now. Feel free to open a new post in case you run into another issue.

@markus1204 With FOG there are 2 parts to the images. The first part is the raw data files stored in /images/<image_name> (this is what you have today). The second part is the meta data that is stored in the data base (what you are missing). If you know the settings you can manually recreate the meta data by filling in the proper settings to point to the raw physical files you have in /images/<image_name> directory.

@CBO Just in case you are still interested in this. I just pushed changes to the current working branch (see here and here) to make the installer do a better job. Upgrade to the very latest and give it a go if you like.

PS: Sorry for taking so long to get back onto this.

I have tried many ways and it seems that powershell can’t do this or i missed something.

What i have tried now is to make a snapin pack with psexec.exe and a batch file.
Also in this batch i can’t write to HKCU.

I used now the following code to store the key and this works for now. It’s not a nice solutions but it works.

If anyone can give me the trick to do this in powershell, let me know.

PsExec.exe -i -s -u %COMPUTERNAME%\%username% -p -nobanner -accepteula -i REG ADD "HKLM\SOFTWARE\Test" /v "Machinenummer" /t REG_SZ /d %COMPUTERNAME% /f

@azureeyedtech Ok, let’s take this one step at a time.

First off: If you’ve used the image type “Multiple Partition Image - Single Disk” only (are you sure about this ???) then it’s near to impossible that FOG has done anything harmful to your source disk! But if you’ve switched over to “Single Disk - Resizable” somewhere along the way then might have changed anything on disk, although we haven’t seen it do anything harmful on upload in a long time. So please tell us, have you ever run an upload task on this machine when image type was “Single Disk - Resizable”? We need to know.
Keep in mind that you cannot switch image type between uploading and downloading the image. If you change the type you need to re-upload the image again!

The PC had secure boot disabled, UEFI disabled Legacy Boot enabled […] I switched the PC host back to UEFI and secure boot and it failed to load Windows

You cannot just switch from UEFI to legacy BIOS and back as you like. These setting needs to be set prior to installing an OS on disk hand have to be left alone after that. UEFI is looking for a FAT32 formated partition to find the boot loader file(s), while legacy BIOS on the other hand tries to find the boot loader code in the MBR. So again, you need to decide which way you wanna go UEFI or legacy BIOS and then leave things as is. In your case it sounds as if the OS was (pre-)installed in UEFI mode. Then you need to run FOG in UEFI mode for this client as well!! FOG can do this. On PXE boot the FOG DHCP server is handing out the correct boot binary to the client depending on it being set to UEFI or legacy BIOS. But if you use a different DHCP server then you need to set this up yourself: Instructions see here…
Secure boot setting is different. You actually need to and should be able to disable secure boot as FOG is not able to handle this. Most people just leave it disabled but AFAIK you may enable it after having uploaded/downloaded an image from/to a client.

So what to do now?

First and foremost find the image on your FOG server (hope you have not overwritten it by several uploads) and make a backup copy of the whole directory. Should find it in /images/<IMAGENAME>. Hope we never need it but you never know. Might be the last copy of your original partition layout we have. While you are there, post the contents of the text file d1.partitions that you find in the image directory. Plus run ls -al /images/<IMAGENAME> and post listing here. Change image type to “Multiple Partition Image - Single Disk” and leave it like that for now! Set UEFI/legacy BIOS on your initial source machine to whatever it was before you played with it (I suspect UEFI) and see if it boots up Windows properly again. Setup your DHCP server to serve both UEFI and legacy BIOS machines with different boot binaries (see the wiki article above). To see if the UEFI boot partition is still there boot the machine up using a Linux live CD/DVD open a terminal window, become root/sudo and run the following commands: mkdir -p /mnt/boot mount -t ntfs -o ro /dev/sda1 /mnt/boot find /mnt/boot umount /mnt/boot gdisk -l /dev/sda

Take a picture of the output on screen and post here.

By the way, are you sure you can actually do what you are trying here? Cloning one image to several Alienware machines with a pre-installed OS that cannot be activated through normal windows keys. Maybe I get you wrong here but this sounds as if it is going to cause much trouble anyway.