You know what stinks?

Sneaking into a lab, leaving the lights off so no one will find you, booting up your client to image and MY LAND WHO SET THE BACKGROUND TO RETINA SEAR?

I have made a darker background that I wanted to share that may help with the sizzling retina, it’s a lot harder to find me when there isn’t a bright white screen in front of me

Enjoy! (It’s nothing spectacular, but its something!)

You have one of two options, either
A.) Change the background by using the web gui. You still need to place the file in the {fogwebdir}/service/ipxe folder but you can name it whatever you like, just make the adjustment on the fog settings page under Fog Boot Settings for the FOG_IPXE_BG_FILE option.

B.) Upload this image to {fogwebdir}/service/ipxe and save it as bg.png (I used filezilla to place the image)
This will overwrite the old background file, I highly recommend backing up the previous bg.png JUST IN CASE!

These commands will need to be issued after every SVN or GIT pull. Keep the new background above in a safe place (/home/user/Pictures).
BACK UP
Ubuntu
sudo mv /var/www/fog/service/ipxe/bg.png /var/www/fog/service/ipxe/bg.png.old

CentOS
sudo mv /var/www/html/fog/service/ipxe/bg.png /var/www/html/fog/service/ipxe/bg.png.old

I will put up other commands later when I figure out where the bg is stored in other versions of Linux.

I can confirm personally as I own these devices and use Ubuntu 16.04 on them, they will in fact work with this version of linux installed.

I used a single hard drive in my instances and did not use any of the on board raid configurations or NAS/SAN options.

@Rj_linux

sudo -i
git clone https://github.com/FOGProject/fogproject.git fogproject
cd fogproject
git pull
git checkout working-1.3.5
git pull
cd bin
./installfog.sh

@Wayne-Workman Don’t like Ubuntu?

@Junkhacker I have never had to adjust the compression. 3-5 minutes to image a client machine is well within my acceptance.

@THEMCV What tweaks are you referring to?

I download Ubuntu, apt-get install git, clone the git run the installation and have a FOG server running.

I never have to tweak anything. So I am curious what others are seeing.

I like them both, I have run many web servers on Debian and Ubuntu. Personally I liked Ubuntu better back before they wen all eye candy mode in 12.04. Matter of a fact, that Ubiquity crap pushed me more towards Debian until I discovered the MATE desktop environment version. I have been using the Ubuntu MATE ever sense.

I have no real issues out of the server versions of Ubuntu either. But I don’t test every iteration and in order for someone who is not as use to linux I tend to use the desktop environment so that others can use the box if I happen to move on to better things, kind of as a courtesy.

But nether here nor there. I do think that a Debian Tutorial is in order, I was only poking some fun at Wayne’s expense

Why not code in a script to disable the UAC (or disable it by default in the image) and use a script to re-enable after your snap in is complete.

This way, yes it’s still half hearted, but it seems the issue is on the windows side of things rather than FOG, but you won’t be leaving your systems UAC disabled.

Happy Valentine’s Day (if that’s your thing) from everyone here at the FOG Project!

We hope your day is filled with love and joy, even if we can’t provide it (sorry love and joy are closed source projects!

In case anyone is in need of a Flux Capacitor:

http://www.oreillyauto.com/flux-capacitor.html?ref=patrick.net

I am trying to find a plutonium supplier

I use:

[code]
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ComputerName>*</ComputerName>
<RegisteredOrganization>Microsoft</RegisteredOrganization>
<RegisteredOwner>CORPORATION</RegisteredOwner>
<ProductKey>FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4</ProductKey>
<CopyProfile>false</CopyProfile>
<TimeZone>TIMEZONE</TimeZone>
</component>
[/code]
This causes the machine to generate a name for itself based off the RegisteredOwner criteria. Then I let FOG rename the machine.

I see where you included the <computername> but in my experience, without a registered owner the naming process fails

I used AutoBVT (Only because when I set up my unattend.xml I used the windows AIK to do so, and it was the default) as the RegisteredOwner and each of my machines started with AutoBVT-(Random Sequence) and then FOG renamed them appropriately.

Hope this helps.

@Rj_linux

sudo -i
git clone https://github.com/FOGProject/fogproject.git fogproject
cd fogproject
git pull
git checkout working-1.3.5
git pull
cd bin
./installfog.sh

@Motech09 said in Fog Server - Database Access Problem:

Nevermind, I fixed it.

What was wrong and how you fixed it really helps others in their troubleshooting/resolution.

In case anyone is in need of a Flux Capacitor:

http://www.oreillyauto.com/flux-capacitor.html?ref=patrick.net

I am trying to find a plutonium supplier

Did you run the installer as sudo?

sudo ./installfog.sh

We also recommend using 1.3.5 RC 11 instead of 1.3.4

Well Hello to you too!

@wlsnfmly said in Lenovo m72 image issues:

The only change I made was to go back to the default undionly.kpxe option

This really is the recommended file.

Please let us know if you experience further issues with your systems pxe booting. I am not exactly certain why you experienced the issues you did, but I am glad you were able to resolve them.

@wlsnfmly I wouldn’t be able to tell you. I have compiled the kpxe in the past to include the drivers for some of the Realtek nics on MSI boards, but that was back in 0.33b days. The all inclusive ones, or the other pxe files in the tftpboot have always been able to serve my purposes since.

It’s a trial and error thing, unless someone else knows which check boxes need to be checked, I built about every relevant looking thing into my kpxe files in order to get them booting, this made them rather large, but I didn’t mind as long as the machine did it’s imaging task.

I’m sorry this isn’t much help, but if you figure out which ones are intrinsically needed, I am sure Tom can start including them, and if you post your resolution(s) here, it’s guaranteed to benefit someone else in the future.

I apologize for not having the information in front of me, but if you can provide the model number of your Realtek nics, I can try to look up the information for you.

@wlsnfmly said in Lenovo m72 image issues:

@george1421 I see the kkpxe in the tftp directory, but when trying to mod it, VI, the coding is all garbled, Is that normal?

Yes, pxe files are compiled, you can’t just pop them open and edit them.

https://wiki.fogproject.org/wiki/index.php?title=Building_undionly.kpxe

This explains how to build your own kpxe files if you are interested.

@Wayne-Workman I’m not disagreeing with you, I am agreeing with you.
Guides should be provided, as well as an explanation as you why, like you have done here.
The more information we can provide the users of FOG the better, filling up the root volume is a common issue that a Linux novice would face, regardless of OS choice. I want to build users up to the point that they learn as well as accomplish their imaging tasks. Guides such as this REALLY help to enlighten our user base!

I am supporting your decision in making the guides, I was merely defending the fact that Ubuntu has issues and needs things done to get the OS ready for FOG as THEMCV had lead to believe in the post under mine. “Posts such as that could easily deter someone from the OS when it would be a better fit for them because they are a novice” is the entire point I was trying to make. That is why I made the defense I did, but still supported your endeavor. Not everyone enjoys the OS, and not everyone will use it. But we still shouldn’t mislead readers into thinking that Ubuntu is a bad OS, has issues, nor should it be avoided. Your personal choice is:
@Wayne-Workman said in Debian 8 tutorial:

Working on putting together a Debian 8 tutorial - because it deserves one - and because I want people to choose Debian over Ubuntu.

I want users to choose the OS that best suits there skill level and needs.

I am sorry for filling up your thread with these posts, I will not post in it anymore as I have said my piece. It was originally to poke a little fun and hopefully enlighten users why your choice is Debian over Ubuntu, but I have seemed to have drug the post off topic instead, so I will wait patiently for your guide.

I did not know that about the CentOS and Fedora and SELinux. I don’t have much experience with those systems, so thanks for letting me know that something has to be done other than just “run the installer” on those OS.

@Wayne-Workman Correct, but this isn’t inherently required in order to get a FOG server running. You can take a bare bones Ubuntu installation and have a FOG server running in ~15 minutes depending on your internet connection. The same can be said for all of the OS that we support.

The information I supplied was a very minimal installation to provide information that nothing needs to be done in order to get FOG working on Ubuntu.

Anything else that is done, that is not inherently required by FOG, would be a modification, whether it is recommended or not. Anything that is broken because of this, regardless of the ease of steps, should not deter someone from using Ubuntu for FOG, nor should it be held against the OS or the user as the steps are extraneous.

Now it seems like I am defending Ubuntu here, I am not. I like how easy it is to use, and for a n00b to Linux, it is a good start. However, I agree that a Debian setup is more pure and would have far less issues. We have seen our fair share of ups and downs with the Ubuntu OS and upstart problems.

I look forward to reading your guide and your recommendations for a happy installation on Debian.