Posts made by Tom Elliott

@TBuzaTechnician You would need to run the mysqladmin command first, then do the command.

That should set your mysql password and ensure FOG will install using that now set password.

Thank you,

@Sebastian-Roth if I had to guess it’s lvm setup.

@Sebastian-Roth, @TBuzaTechnician

If you run mysqladm --user root password "newpassword", you should not do it as a part of the installation script (eventually yes, but as of right now no.)

After you set the password, then you can run it with snmysqlpass='newpassword' ./installfog.sh -y

Eventually, I know we want to create a separate user and password pair for mysql for security reasons, but in the mean time, the above should work.

run the installer as:

snmysqlpass='newpassword' ./installfog.sh -y

@Bill-Rice
You are safe to run the install in /opt/fogproject as needed.

I’d suggest

1. Copy the current /opt/fog/.fogsettings file to /root/.fogsettings
2. Delete the current /opt/fog
3. Copy the original server’s /opt/fog to the new server into /opt/fog as well.
4. Copy the /root/.fogsettings to /opt/fog/.fogsettings file.
5. Rerun the install to be on the safe side.

When you created the new server, did you copy the original servers /opt/fog folder over to the new server?

@Quazz I don’t know that it’s a bug. Yes, i understand this is unexpected behaviour. But Remember the location plugin is a plugin. It’s not a default element of the core of fog. The Core elements attempt to ping all hosts each iteration. (So this is the expected behavior).

That’s not to say we shouldn’t have this in bug reports and we’ll need to add things to the location plugin to distribute the PING Hosts to enable location specific pinging.

This is not currently coded for or thought of so I imagine this will take a while to work out.

@AdamH From the sounds of things, the storage group item is not set on the image. The GUI tries to correct for this by applying the first storage group to the image, but if there is no actual value set, this message you see will still happen.

I’d suggest updating the image even though it shows as though it is set.

Thank you,

Based on the message make a change to the image in the GUI and set, and make sure to update, the default storage group for the image.

@Sebastian-Roth https://github.com/FOGProject/fogproject/commit/d3a70dd417eb1d08b48a637e26ec8776f4409d29

I commented out the “style” info you put, and moved it to push info out to the left instead of the right so that the form field is still accessible when reading the information.

Snapins do not show whether they were installed or not, because snapins aren’t tracking software and their status. Snapins are a simple means of running scripts on the client machine. We don’t track them. We track the return codes of snapins. Not whether or not that snapin has been installed, if that install succeeded or failed, or any thing else you might think snapins do. They were not designed to do such a thing as it is something relatively complex to work out.

Well, The cron syntax wouldn’t “disappear” unless your web front end translates the date/schedule to a Cron style system automatically.

Yes the idea should be possible, though I don’t know how best to help except to help provide basic syntax of the API so you can process and parse the data that’s returned.

I guess, though, I don’t fully understand the why. Everything (with exception of the scheduled cron tasks) is already available via the GUI we provide as a part of our software. “viewing said Scheduled tasks, view active tasks, and when a system is added to the host list that host will be added to the web page” are already done with the provided interface. Why create a new hen-house when the one you got with the land is also a hen house that does everything you need it to do.

The radio buttons are accurate. If you choose Reboot when Shutdown was chosen, it unselects Shutdown. If you Select Shutdown when Reboot was selected, Shutdown gets unselected.

The reason you can unselect them at all basically means that you don’t require it to restart or shutdown.

@Sebastian-Roth If my memory serves me correctly we did encode all of this for a little while, but too my knowledge we’ve moved away from encoding special characters in preference of using proper sanitization of inputs into the database. That’s not to say everything was fixed, but I’m pretty sure we moved away from this particularly because the & would get encoded as &amp, then the & in the &amp would get encoded, and so on and so forth.

@icescout27 you can disable the compression in 1.5.7.

That said it isn’t quite a dd raw image per say as it’s not using dd in its native form. It’s using partclones imager format which is still a raw copy, just not from dd. The reasoning for this is then our scripts would simply call partclone.restore to place that image on disk regardless of type (raw, btrfs, ntfs, ext, etc…)

If you really need a true sector by sector you can manually run a dd instance if you know how.

Typically, though, fog isn’t really intended for forensic usage.as we typically are capturing images to be used for mass on other systems. This of course is not to say fog couldn’t be used for this, just it’s not something we are familiar with as part of our product.

If you need any help I’m sure we can provide some assistance.

@kralon is there a product key entered for that machine in the fog GUI?

On this host item, remove the C:\ from the host device line and restart the machine.

From the GUI -> Host List -> Win10-Gold -> Host Device, delete c:\ and save. You may need to cancel and recreate the task.

@Mark-krikunov You can enable port 445, and it should work.

That all said, this “feature” isn’t a requirement or indicator of capability of imaging within your environment.

@rogalskij Maybe try setting up the multicast-rendevous with your FOG IP Server? You can use the TCP / IP, or use the Multicast that matches your TCP address.

@Sebastian-Roth Sure:

The new, Version and Kernel Tabs:

Left on FOG Configuration Page:

I haven’t removed them from the page for now.