@george1421 Yes, you are a wordy son of a gun.
But, if you look at the existing wiki article about dnsmasq, it’s sort of a disaster - and epically long.
The length alone is a turn-off.
I think this is why my Troubleshoot TFTP article isn’t so popular. Too long.
@apathetic_admin said:
found a command (./installfog.sh --recreate-CA --recreate-keys) that I believe would take care of my issue IF I could get the correct hostname configured, assuming in .fogsettings.
That’s a super dangerous command… very very dangerous.
Imagine having 6,000 hosts with the FOG Client installed… and then suddenly NOT being able to control them through the FOG Client anymore… that’s what that command does.
If the CA is created, but hosts are already deployed using the old one, you WILL loose control of those hosts, and to regain control, you must reinstall the FOG Client on each and every one of them.
If those two things are the only modifications, I don’t see why the installer can’t just support Raspbian?
Either way, very good work George. I messed with this for a little bit and quit after a while. I must have been very distracted.
Here’s the git link for the mobile script - I don’t it will be too much work to get going, the tool now works on Fedora, CentOS, Debian, and presumably Ubuntu.
@Vasahond said:
I am in the root directory – there seems to be no /images path.
Really? If that’s the case, that’s almost surely the problem. Can you please post the output of find / | grep /dev/.mntcheck
Also, what output/errors do you get when you re-run the installer? You’ve also not specifically stated what version of FOG you’re using, we need this information as well.
Here’s an example that uses FOG Trunk (1.3.0): https://wiki.fogproject.org/wiki/index.php/DBAN_(Darik’s_Boot_and_Nuke)
There is no one way to add an ISO, it just depends on what it is… and in some cases there are much more superior options than trying to use FOG to deliver an ISO… for instance, a Windows ISO is a bad idea when you can use WinPE to initiate a Windows installation.
Here’s instructions on upgrading to trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
@ManofValor It’s not a fog question. It’s a Linux question. If CentOS 7 supports it (or any other distro of Linux), then fog can use it.
The installer sets most of those things for you, they work for probably 95% of environments. The exceptions to the rule are the really, really large environments where FOG services over 6,000 hosts.
@StevenT Yes. in FOG Trunk it’s just a checkbox on the upload confirmation page. In 1.2.0 you have to go into advanced tasks and find the debug upload task.
We won’t be doing anything to change the disk at this point. We’re just trying to gather information that will hopefully lead us to the next step.
@need2 said:
And Linux system’s won’t use up any licensing at all, because Linux.
+1
Really I do not understand why more Enterprise users running predominantly Windows environments do not use Hyper-V and instead go with less flexible and more expensive solutions.
I hear you brother.
In fact, why not just use CentOS 7’s integrated hypervisor? I’ve ran Windows Server 2012 in it before with no issue, and I’ve ran linux inside it too, naturally. Then you have NO licensing, and ALL the power to do whatever you want!
That said,
Hyper-V comes with a Windows Server 2008 and higher product key… USE IT!!! You’re life will be easier! Seperate out all of your major “things” so that the failure of one “thing” won’t affect all the other “things” you have!
I can’t stress how invaluable virtualization is. there is a REASON why a virtualization specialist job pays 80K a year.
This has been added to the wiki here:
@msimpson said:
I am definitely more comfortable with Windows which is why I was tossing around the idea of just installing Win7 Pro x64, installing Virtualbox, and then create the VM for FOG on that to take snapshots
CentOS 7 Hypervisor supports snapshots, it works, I’ve used it for FOG and for Server 2012.
If performance really sucks, I’ll install on bare metal.
SAS 12gig can easily keep up, Sata 6gig can’t really… There’s not a comparison really between server and consumer hardware. However FOG will work, it’ll just be really slow. I virtualized FOG in CentOS 7 hypervisor using an Optiplex 9020, when I imaged with it the HDD light was just solid lit and the speeds were not that great in comparison to FOG running in Hyper-V with SAS 12 gig drives, but the speeds probably was great given the setup and hardware.
I will also look at CentOS as well, it will have to be GUI though.
People at my work ask why I choose to not install with a GUI. I ask them to find FOG documentation that uses a GUI on the backend… there isn’t. The installer is CLI, all of our documentation for troubleshooting is CLI, the management of services documentation is CLI, adding drives and moving images around is all documented in CLI. And any help you get on the forums for back-end and troubleshooting will be commands you run in the CLI. Why? Because it’s too hard to create documentation for 10 different GUI versions. CLI provides more consistency across the flavors of Linux - and consistency is a good thing.
If you choose to install a GUI, you will find yourself clicking a user name, logging in, and then you will find yourself opening the terminal.
But I won’t knock anyone for this, if it makes you feel better and adopt Linux faster, then awesome.
I might also add that many of the GUIs for Linux sorta suck and are really limited in what they can do (in comparison to what CLI can do, i.e. everything).
I believe everyone will love it when it comes time to build/rebuild a PC.
Everyone always does.
Following up here (a year later, yes I’m terrible).
I did this at work, it went fine.
Also, here’s a related thread that deals with the same issue but had problems:
https://forums.fogproject.org/topic/8762/change-image-id-number
#wiki worthy
@Scott-B said:
Is there a way to scan or test a partclone image to see if its corrupt?
Yes. I want to make a snapin just for this actually, but the snapins creation process is really confusing to me. I’ve rigged together a little thing-a-mo-bob that you can use to manually check image integrity… although it’s labor intensive to check (but then again, you’d only check if you have issues with a specific image).
https://forums.fogproject.org/topic/6318/image-file-integrity
I can do better, I just need to find the time to do it.
@Rusty My understanding for creating an image that works with multiple hardware makes/models is to include every driver you can (around 75GB worth I think), sysprep the machine, and then capture your image as a single disk - resizable type.
It’d be benificial to setup a Windows KMS server for windows activation, meaning you’ll need to setup your image to activate through this using a unattend file. There are various driver packs on the web, I think @Jbob knows of one that is pretty good.
But you must also consider that making images that work on almost everything is going to result in an image that is 100+ GB in size, and will be substantially slower to deploy.
I build an image for every model of computer in my building, my images on the host average about 40GB (for windows), and when captured and compressed are about 16GB on the fog server. It takes me 5 minutes to deploy an image to a single host.
My images are lean and mean, they deploy fast, boot faster, and run good.
I had a need for getting a list of computers that could possibly be having problems with the FOG Client. @Joe-Schmitt gave me an idea on how to do it conceptually, and I was able to build some things that did exactly what he suggested.
Install samba and samba-client, start and enable the smb service.
Create a share folder that everyone has access to:
mkdir /readwrite$
chmod 777 /readwrite$
Configure samba:
Configuration file is: /etc/samba/smb.conf
Here’s the configuration I wrote:
map to guest = Bad user
guest account = nobody
security = user
passdb backend = tdbsam
unix charset = utf-8
dos charset = cp932
[readwrite$]
path = /readwrite$
read only = no
# The below line defines what IP ranges are allowed. They are space delimited.
# For instance, if you wanted local loopback address, the 10.0.0. range,
# and the 192.168.1 range, and a specifc public IP of 50.50.50.50,
# It would be this:
# hosts allow = 127.0.0.1 10.0.0. 192.168.1. 50.50.50.50
hosts allow = 10.2.
create mode = 0777
directory mode = 0777
writable = yes
public = yes
Note: There’s a nodeBB bug that is currently affecting how scripts are displayed. Be aware that after double left brackets [[ and before double right brackets ]] there should be a space.
#!/bin/bash
#----- MySQL Credentials -----#
#Here, we just source the fogsettings file because creds are in there.
source /opt/fog/.fogsettings
#----- Begin Program -----#
selectHostname="SELECT hostName FROM hosts"
options="-sN"
if [[ $snmysqlhost != "" ]]; then
options="$options -h$snmysqlhost"
fi
if [[ $snmysqluser != "" ]]; then
options="$options -u$snmysqluser"
fi
if [[ $snmysqlpass != "" ]]; then
options="$options -p$snmysqlpass"
fi
options="$options -D fog -e"
mysql $options "$selectHostname" | while read hostName; do
if [[ "$hostName" != "" ]]; then
echo "$hostName" > /readwrite$/$hostName
fi
done
After running this script, here’s what I see in my /readwrite$ directory below. There should be a file per registered host, here’s a clipped sample of my output:
[root@mb-fog ~]# ls /readwrite\$/
r0006502230WLMB r0105508030WDMB r0129008514WDMB r0150508359WDMB r0206510494WDMB r0212510525WDMB R0219502510WLMB r0224004875WDMB R0225508043WDMB R0232510478WDMB
r0009508526WDMB r0106008038wdmb r0129008524WDMB r0150508360WDMB R0206510511WDMB r0213005683WLMB r0219502542WLMB r0224004876WDMB R0225508056WDMB R0232510479WDMB
[root@mb-fog ~]#
Next, we use Windows to create a batch script designed for FOG Snapins, to run on each host, and each host delete it’s file in this share. Create this as a .bat file and create a snapin for it on the fog server, associate it with all hosts, and run it on all hosts.
set "folder=\\10.2.1.11\readwrite$"
pushd "%folder%" && (
for /d %%i in (%computername%) do del "%%i" /Q
popd
)
When deployed via FOG Snapins to all hosts in the environment, you are left with files that are the hostnames of all hosts that have not run yet. it may take hours or even weeks depending on your environment for this test to completely finish accurately. hostnames that remain can be assumed to be offline, having network issues, windows issues, or fog client issues.
You can compile all these leftover hostnames into a single file as often as you like with the following BASH script:
#!/bin/bash
#path to files.
FILES=/readwrite$/*
#where you want it to go:
output="/readwrite$/problemHosts.txt"
rm -f $output
for f in $FILES
do
if [[ "$f" != "$output" ]]; then
echo ${f##*/} >> $output
fi
done
@EAHarvey The compression setting is only used for image upload/capture. He would need to re-upload to try a different compression setting.