@sjensen Read this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@eadhor Check your free space with df -h look for partitions that are 100% or 99% full.

Also, inside of /opt/fog/.fogsettings set snmysqlhost to these two things, one at a time: localhost and 127.0.0.1 Running the installer after each to see if the setting works.

#wiki worthy

Bitlocker?

@sebastian-roth We need to clearly define the problem. As I see it, there’s two local interfaces on this FOG Server.

• enp3s1 @ 192.168.100.1
• ens33 @ 10.203.8.31

And we are seeing multicast try to use enp3s1 instead of the one we see defined on the storage node in the picture ens33.

I remember @Tom-Elliott doing work on this, something about auto-selecting the interface if I remember right. But really, the interface that Multicast should use ought to be the defined interface in storage node settings.

@Tywyn you could try to turn the interface off and see if multicast works then? Try this command: ip link set enp3s1 down You can later turn it back on with ip link set enp3s1 up also a reboot would bring it back up too.

@rosscaramell The type of disk you’re using doesn’t cause accounts to be randomly made in Windows. This isn’t related to FOG in the slightest.

A bad FTP password for the storage node would cause this. Also if you’re out of space too.

@chrispy I think you’ve mixed up UEFI and BIOS. This machine really looks like it’s a UEFI machine, and your DHCP server is telling it to use a BIOS boot file. You’ll probably want to go over this document and that should put you on track: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

I think this isn’t the right forums for this problem. This is not a FOG related problem. If I were you, I’d probably throw the hard disk into the trashcan and get a new one.

@eadhor Be sure to set the database username and password inside of /opt/fog/.fogsettings or you’re bound to break stuff later on when you upgrade (promise).

Change settings for fog inside of the fogsettings file, then re-run the installer for those settings to take effect. Here’s documentation about the file:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

The settings you need to change are these:

snmysqluser=''
snmysqlpass=''

Put the correct values into them, save, then re-run the installer.

Install the FOG Server with the DHCP option while online, then take it offline and it should work for you.

Great job man, really! It’s so nice to see people using the API.

Bumping this, it’s a good idea still.

@quinniedid Let’s approach this from a troubleshooting perspective. Create a brand-new VM, install windows 10 on it and nothing else (no updates, no software, no nothing). Then try to capture to a new image using this new VM. Does this work? This test should take you less than an hour. If it works, something is not right with the problem VM.

I ask because most times, a problematic capture can be solved by just rebuilding the golden machine again.

Running through the Troubleshoot FTP article would of course work, but there’s an easier way now-a-days @Sebastian-Roth. The FOG Installer calls a PHP script that connects to the FOG Database and corrects the FTP password for the node it’s running on, based on the password set inside of /opt/fog/.fogsettings

In other words, one only needs to re-run the installer to correct this problem. That is - if your FOG Version is new enough.

you could use powershell & the api to rename everything, but it’d probably be easier to just import all the correct host data as a CSV file.

@unknownhost99 You don’t need to uninstall fog in order to re-run the installer.

@caw001 said in Join domain and rename PC:

I understand it gives it a name, but it does not follow our naming convention.

FOG only names a computer with what you specify. You can change the name of a host in the web gui, under Host Management.

@caw001 FOG by default already renames deployed Windows images during the imaging process. Renaming and joining after the imaging process is performed by the FOG Client.