@Wayne-Workman well, it happens on physical machines too. Maybe CentOS is just better than ubuntu for hosting fog?
Posts made by JJ Fullmer
-
RE: Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options
-
RE: Advanced Printer Management Plugin and Fog Service Module
@Wayne-Workman But that involves waiting for functionality I could use now…
-
RE: Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options
@Sebastian-Roth Yeah, our dhcp does have some serious issues actually. We’re working on narrowing it down. Sometimes computers get ips from the ip phone scope, even when they have an ip reservation. Pretty sure it has to do with some incompatible firmware on one old hp switch we’re phasing out. I was just hoping to have found something that just worked around other issues.
And sadly, after trying to boot a different vm a few minutes ago, same esxi server and same type of virtual network adapter E1000 as the other, it took a few tries again to get an address in the initial pxe boot.
Thanks for the input though, just more confirmation that our network needs an overhaul.
I just want to hit reset of the whole data center infrastructure and start again. But that’s not actually a good idea, I know that, people need to do their jobs or something silly like that. -
RE: Storing Images on NAS/Network Share
There are a few different options that oughta work, just off the top of my head, haven’t tested these yet but probably will eventually.
-
You can have a seperate linux server set up as a storage node with the fog installer in storage node mode and link to it in the gui with the fog storage management settings.
-
It would require a little research, but you could utilize esxi’s datastores and clusters and map a NAS there. And then link it to the vm through esxi mounting it like a local drive. Then choose to mount that drive to /images with /etc/fstab, mount it elsewhere and point to it in the fog settings and /etc/exports, or mount else where and make /images a symlink to the mount point
-
There are some other options too, but I think the most important thing to consider is that where-ever you choose to put it, you want it to be an nfs share. I imagine it’s possible to get other types to work, but nfs is what fog uses natively and for good reason. Most NAS’s have some setting in their gui to enable nfs settings.
-
-
RE: Advanced Printer Management Plugin and Fog Service Module
- Ability to add local printers on nul: port with no ip address (.i.e. Send to OneNote, PDF Printers, etc)
- Ability to add usb printers or at least set them as allowed so FOG doesn’t delete them if they aren’t in the printer list and FOG is set to remove all extra printers
-
RE: Changing the directory where Fog images are stored question
Also, if you choose to change the snapin directory and then have problems with the client, here’s a fix
-
ca fog service "error failed to decrypt" when snapins in non-default directory
I had set my snapins to a different directory (/images/snapins with /images being a symlink to /home/fogRootSystem/images)
But the original install had created the /opt/fog/snapins directory and put the ca ssl folders there.
But then it did it put the CA ssl folders with new keys in the new /images/snapins folder.All day today I have been troubleshooting the client wondering why it suddenly stopped authenticating. Uninstalling and reinstalling, re-imaging, modifying the msi, resetting encryption data, running the fog install script with the --recreate-CA and --recreate-keys options. And nothing worked. Then I noticed the duplicate CA and SSL directories and got to thinking that maybe that’s not supposed to be a thing. So I moved the /opt/fog/snapins folder to my /images/snapins directory
mv -f /opt/fog/snapins /images/snapins
then deleted the opt folderrm -fr /opt/fog/snapins
then made a symlinkln -s /images/snapins /opt/fog/snapins
Then I reran the fog installer like this./installfog.sh --recreate-CA --recreate-keys -Y
and now the client is working again (after reinstall on the client).So a fix exists, but it seems that changing the snapins directory doesn’t work for the client and causes weird ca/ssl authentication errors.
It’s possible that something else I did fixed my issue, but I am 99.9% sure that the symlink and reinstall recreating the CA is what solved it.
-
RE: Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options
@Wayne-Workman Thanks
I’m on 2012 R2 dhcp ver 6.3 -
RE: 1.3.0
1.3.0 is really the trunk/“beta” version currently. It isn’t quite yet to release. Granted if every stable trunk was released as a final version, we would be at FOG 5782.2.0 by now.
@Tom-Elliott has been working on gpt partitions recently trying to get it perfect. Give the trunk a go -
RE: Changing the directory where Fog images are stored question
The easiest thing to do is probably just leave it as default /images but then either mount the HDD to the path /images in your /etc/fstab
nano /etc/fstab
or make a symlink withsudo ln -s /path/to/hdd/images /images
I personally use the symlink method. In my case I just wasn’t paying attention when I partition my drive and made a /home data partition of 400 GB and a / partition of 80 GB. I realized too late that this meant that I only had 80 GB for images… Since I didn’t feel like editing the partition table or starting over, I just moved the /images folder to a folder in /home/fogRootSystem and made a symlink to point /images to that folder and it worked like a charm.Otherwise you also would want to edit your /etc/exports and make sure that it is pointing the nfs directory to your /images (Fog might do this for you if you specified it during install or in the gui)
You also would want to consider moving the snapins directory as it would normally be in /opt/fog/snapins and if you have a lot of scripts and large installers, than that directory can get pretty big too. Granted any of these would run faster on an ssd.Hope that helps.
-
RE: Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options
I also made a static A host record for the fog server hostname and ip as well as a cname for fog-server to that A record. Maybe that did something too?
-
Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options
So I think I may have just accidentally discovered a way to increase the effectiveness/speed/reliability of pxe booting in windows dhcp configurations.
Granted I did just change server boxes and OS’s, so sadly this is a discovery with a lot of variables so I’m not 100% sure that it is really a thing.So, on top of the already existing server wide options of 66 and 67 that point pxe boots to the FOG server and specify the pxe boot file I added a couple more configurations.
So before, something that helped a little was having an ip reservation for the FOG server on the same subnet as the workstations it’s imaging. So I was adjusting that reservation whilst migrating my FOG server setup to a new ip address on a new box. I decided to try a couple other options set just to the fog-server reservation.
- option 003 Router - set to the router gateway address with a secondary address of the DHCP server itself (i.e. 192.168.100.1, 192.168.100.3)
- option 012 Host Name - set to the fog server’s host name.
The first time I booted to pxe (on a vm that usually required a few tries before it worked) it booted up with no issues at all just as it should, faster than I had ever seen even.
So my question is for people with a little more network experience than me. People like @Sebastian-Roth @Tom-Elliott @Wayne-Workman Would setting these options make a difference reasonably?
I kinda think that they would since one of the problems I would see with longer pxe boots is repeated discovers and selects of one of the 3 dhcp requests in the pxe boot process trying to find a router. So is this all in my head or did I stumble on something helpful?
-
RE: FOG Compatibility Test Failed
I had a problem with an older raid controller not being recognized by the centos/RHEL 7 kernel just yesterday. Would this happen to be an older hp smart array controller? Like 2008 or older?
You could try adding these host kernel arguments (in the gui for the host, register it manually if you haven’t already)hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1
That might do the trick. These older array controllers are no longer supported by the RHEL kernels, this is where I got that info…
http://serverfault.com/questions/611182/centos-7-x64-and-hp-proliant-dl360-g5-scsi-controller-compatibility -
RE: Best Distro to use for stress-free FOG installation
@Cyrus So you haven’t actually installed any sql services?
I would just add the packages reccomended by the wiki ignoring any errors because some of them are just outdated…rpm --import http://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-6 rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt rpm -Uvh http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org rpm -Uvh http://www.elrepo.org/elrepo-release-6-5.el6.elrepo.noarch.rpm rpm --import http://rpms.famillecollet.com/RPM-GPG-KEY-remi rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
Then manually install these packages
yum -y install htmldoc ttf2pt1 t1utils fltk subversion wget git
Then make a folder for the fog installer git and cd into it, download fog, and install it, for example…
(replace ‘fog’ with your username if you are going to let the installer create the fog user for you)mkdir /home/fog/fogInstalls mkdir /home/fog/fogInstalls/git cd /home/fog/fogInstalls/git git clone https://github.com/FOGProject/fogproject.git ./ #this part will take a little while cd bin ./installfog.sh # follow the prompts # Then configure the firewall per this post (https://forums.fogproject.org/topic/6162/firewall-configuration) for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done systemctl restart firewalld.service
Then whenever you need to update
cd /home/fog/fogInstalls/git git pull cd bin ./installfog.sh -Y
and that’s all there is to it.
-
RE: Best Distro to use for stress-free FOG installation
@Cyrus Having installed it on many flavors, I would say for stress-free installation Ubuntu is a good bet.
However, I found that there are a lot issues that happen later from ubuntu doing silly things that will make things break. Like the re-occurring php package debacle of just a couple weeks ago.I just moved my production fog server to centos 7 yesterday and while the install of centos gave me a little trouble (because of a legacy hardware issue) the install of FOG and subsequent updates and having everything up and running has been a dream. Also, since it is Red Hat, having experience with that looks better on a resume’ to some bigger companies if that’s something you care about.
So I would say stick with centos 7.
As for the mariadb issue, I didn’t have any issue there. From what I understand mariadb is just a new name for mysql (there’s more to it than that I realize, but to simplify it I’d say that)
There are some notes in the wiki about mariadb during centos 7 install you could try, but I think it’s a bit outdated now since FOG installs mariadb now.https://wiki.fogproject.org/wiki/index.php?title=Installation_on_CentOS_7
Did you have any mysql related errors during the fog install script, or was this while trying to install it before hand. The best stress-free solution would be to let the fog install script take care of installing the requirements. If you haven’t actually configured anything yet and you think you broke your mariadb install in some way, I would go ahead and just reinstall centos 7 and follow the instructions in that wiki post. It worked for me just yesterday.
-
Advanced Printer Management Plugin and Fog Service Module
So this isn’t so much as a request for someone else to do this as it is a request for more ideas.
After adding the code for importing printer configurations to the service I had some ideas for improving the fog printer management in the service and the gui.
However, I don’t think that everyone would quite care that much about these ideas enough to add them into the core, but making a module for the fog service and a plugin for the gui would probably do the trick. I intend to start working on this in a few weeks to a month from now after a couple other projects are done first. But I figured why not get some feedback on the idea while it is in the brainstorming phase.So here is some of the stuff I would be looking to add to an Advanced Printer Management plugin/client module
-
Adding printer ports with existing prnport.vbs windows command
(Cscript %WINDIR%\System32\Printing_Admin_Scripts\en-US\Prnport.vbs
)- Option to add SNMP private key for printers locked down with snmp keys
- Option to enable SNMP on port with default public key
- Option to use LPR or RAW port on standard local/TCP IP Printers
- Option to add a usb printer shared on the network through a computer, NAS, or other network device.
-
Installing the inf file to the OS with
PNPUTIL -i -a file.inf
-
Adding printers with Prnmngr.vbs if
RUNDLL32 PRINTUI.DLL,PrintUIEntry /if
fails for any reason
(Cscript %WINDIR%\System32\Printing_Admin_Scripts\en-US\Prnmngr.vbs
) -
Allowing the use of network shares for inf driver files and config files
- Either a checkbox in the add/edit printer menu or auto detect of unc path start \\ would bring up an option for domain\username and auto encrypting password (like the AD password box)
- This user/pass would be used with a
net use %share% /USER:username password
command at the start of adding the printer and a subsequentnet use %share% /delete
at the end. - Also an option to ask (and perhaps detect) if a windows enterprise version is present with the nfs client installed, and if so saying to just put the printer files in a folder in the fog /images nfs share and mounting it in windows with nfs without the need for a password.
- Maybe add the option to autoinstall a third party nfs tool to use the fog nfs share option on any version of windows
- Maybe create a universal printer driver folder structure that can be downloaded to the fog nfs share or other network share
- Maybe even add to that with the option to select from existing printer drivers in a drop down menu when adding a printer
- This idea might require help, and would have the caveat of being difficult to update without some sort of automation of downloading new drivers for every model as they become available. Could just make it publicly accessible and let the community handle that as it happens or something.
Thoughts?
-
-
RE: Can't Edit Exisiting Snapins or Create New ones
@Arrowhead-IT Scratch that, it totally worked after a restart. So if you go breaking your permissions just run the script posted and restart and violia!
-
RE: Can't Edit Exisiting Snapins or Create New ones
@Arrowhead-IT Well it was worth a shot but it didn’t do the trick, maybe restarting would work, I’m backing up before I try that though.
-
RE: Active directory Join issue
@anthonyglamis No, you don’t need to create a new image for a new revision. It’s only if you reinstalled fog completely, regenerating the ca certs.
-
RE: Can't Edit Exisiting Snapins or Create New ones
I found a script to restore permissions here
http://serverfault.com/questions/221447/how-to-repair-restore-ubuntu-10-04-after-sudo-chmod-777#!/bin/bash # Restores file permissions for all files on a debian system for which .deb # packages exist. # # Author: Larry Kagan <me at larrykagan dot com> # Since 2007-02-20 ARCHIVE_DIR=/var/cache/apt/archives/ PACKAGES=`ls $ARCHIVE_DIR` cd / function changePerms() { CHOWN="/bin/chown" CHMOD="/bin/chmod" PERMS=`echo $1 | sed -e 's/--x/1/g' -e 's/-w-/2/g' -e 's/-wx/3/g' -e 's/r--/4/g' -e 's/r-x/5/g' -e 's/rw-/6/g' -e 's/rwx/7/g' -e 's/---/0/g'` PERMS=`echo ${PERMS:1}` OWN=`echo $2 | /usr/bin/tr '/' '.'` PATHNAME=$3 PATHNAME=`echo ${PATHNAME:1}` # echo -e "CHMOD: $CHMOD $PERMS $PATHNAME" # result=`$CHOWN $OWN $PATHNAME` # if [ $? -ne 0 ]; then # echo -e $result # exit 123; # fi echo -e "CHOWN: $CHMOD $PERMS $PATHNAME" result=`$CHMOD $PERMS $PATHNAME` if [ $? -ne 0 ]; then echo -e $result fi } for PACKAGE in $PACKAGES; do if [ -d $PACKAGE ]; then continue; fi echo -e "Getting information for $PACKAGE\n" FILES=`/usr/bin/dpkg -c "${ARCHIVE_DIR}${PACKAGE}"` for FILE in "$FILES"; do #FILE_DETAILS=`echo "$FILE" | awk '{print $1"\t"$2"\t"$6}'` echo "$FILE" | awk '{print $1"\t"$2"\t"$6}' | while read line; do changePerms $line done #changePerms $FILE_DETAILS done done``` It's running right now, hopefully that does the trick.