Posts made by Kevin

That all looks to be right. Try restarting the TFTP service on FOG [B]sudo service tftpd-hpa restart [/B]

It looks like you pointed FOG to use another DHCP server other than itself, at least from the config above. Is that correct? If you did, you need to specify options 66 and 67 in the DHCP scope of a Windows server. If you use a Linux server, you need to specify the next-server. If you receive a PXE-E32, it’s usually due to your machine not being able to contact the TFTP server due to it not being specified correctly on the DHCP server.

Glad to hear you got it working.

it still looks like it’s not liking the user account that you are running, that you don’t have elevated privileges. Also, are you installing/upgrading software when trying to install FOG?

E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)

That makes me think that something in Ubuntu is trying to update files as well at the same time, and Ubuntu definitely does not like that. But that could also point to a permission issue.

Do you receive the exact same errors from above when you run the command [B]sudo ./installfog.sh[/B]? Or do you still receive the same errors? i.e.

(
This installation script should be run as
user “root”. You are currenly running
as fogclone.

E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

• Checking package: apache2…Failed!
  )

If any of those are different if the command is running as sudo, it may give me a better idea of what’s breaking. If you are running it as sudo, then we may have to change the root password, just to try and see if something got messed up with that account.

Can you run an MD5 check on the fog_0.32.tar.gz file? This will tell you instantly if you have a bad copy of FOG.

The MD5 should be: 45b323d4150690b9c1aa8288c33830c9

to do this type: [B]sudo apt-get install md5deep[/B]

Then just enter: [B]md5deep /path to your fog_0.32.tar.gz file [/B]If even off by 1 byte, that number will be completely different.

Because it’s Windows 8, the Windows ME of the modern era …ok, to be fair, just the interface is a little “different”

you shouldn’t have to install anything when you’re installing FOG. It should install everything it needs. Just to verify, are you running the installfog.sh with the sudo command?

It comes down to personal preference. I personally build all my servers on the latest LTS (Long Term Support) versions of Ubuntu. So my servers are all being built on 12.04 LTS. Being that it’s a dedicated server, I don’t always need the latest, greatest features, so the LTS works for my needs. However, you will find a lot of people here like CentOS. I want to say that this is supported by Red Hat, but is the free version of the enterprise OS. Personally, i’ve tried it, but i’m used to Ubuntu, so that’s what I stick with. I also have a lot of other tools not related to FOG that i’ve compiled and know to work well with Ubuntu which is another reason I pick it. So personally, you could ask 20 people what they use, and you might get 20 different answers. The best answer is, use what you are comfortable with and with what you like. If you are relatively new to Linux however, I would recommend Ubuntu, Fedora, or CentOS for installing FOG.

FOGprep should only be used on Windows 7 machines. For XP, you need to extract sysprep from deploy.cab. This file can be downloaded from here: [url]https://www.microsoft.com/en-us/download/details.aspx?id=11282[/url]. (Going from memory at this point) But you then run the setupmgr and it’s literally a step by step process to setup a generic image for your machines. However, once you are done, make sure you back up the folder these files sit in. The folder with the sysprep info in it is automatically deleted once the computer is re-imaged. If you need more help, I can try and get a write up done tonight or tomorrow on how to get an XP system sysprepped.

That’s a known issue. What you need to do is go and download a kernel from here, [URL=‘http://sourceforge.net/projects/freeghost/files/Kernels/’]http://sourceforge.net/projects/freeghost/files/Kernels/ [/URL]then whichever kernel you download, you will need to rename to [B]bzImage[/B]. Once this is done, first rename the original kernel to something like bzImage.backup. This is located in /tftpboot/fog/kernel. Once you rename the kernel you downloaded, move it to this folder and you’ll be all set. Just note that it has to be spelled [B]bzImage[/B], all lowercase besides the I. If a capital letter is not right, it will not boot.

You can try to multicast to the machines. This will push the image 1 time to all 10 machines at the same time, saving bandwidth. But you are correct, you need to have every machine registered in FOG prior to try and multicast. So, for instance, I would take all of those machines and put them in a group, which for example we’ll call Lab A. Once a group has been created, you can then go to the Group management tab, select Lab A and set the memberships, image ID’s etc to the specific group. Once this is done, you go to Task Management > List All Groups and select Multicast from Lab A. From there, imaging would be like normal once all the machines pxe boot.

i’ve run into that once or twice before, each time I just re-installed the OS and gave it another go. Not sure what causes that to happen from time to time.

I would try the chmod command again with 777 this time and see if that makes a difference

not a problem, and nothing to be sorry about. All you would need to do is type:

[CODE]sudo chmod 644 /usr/sbin/sysv-rc-conf[/CODE]

that will for the permissions to change on the file

what OS are you trying to install FOG on? Also, you could try to chmod 644 the /usr/sbin/sysv-rc-conf file since it’s a permission issue and see if that improves the install. What it sounds like is a corrupt Apache install though. Hopefully chmodding the file will help push you past that file.

I don’t know why, but it seems like sometime not being in the directory will cause strange issues, so i’ve learned it’s best to go directly into the /bin directory and sudo the installer from there.

sorry, yes, installfog.sh, sorry was going from memory

So I would do this:

[CODE]cd /Desktop/fog_0.32/bin
sudo ./installfog.sh[/CODE]

and see if that gives you better results

We order all SFF machines, only for special applications do we order towers or USFFs. Our SFF machines have regular HDD’s, but our USFF all have SSD’s. However, I can say that our E6430’s have SSD’s in them, and with the new kernel, we’ve had zero problems with imaging.

have you tried running the install.sh command with sudo? Also, i’ve noticed at times that you need to be in the /fog_0.32/bin/ folder while using sudo to have it install everything correctly.

We’ve had no problems with the 7010’s running kernel 3.6.9. We do have some 7010 USFF, but I personally haven’t tried imaging one of those yet. When we got them, we put our own custom installs on them. Ours also have SSD’s in them, so that could make a difference as well come imaging time. I might be able to snatch another one in a day or two to give it a quick test to check and make sure the images work. But besides running the bypass host registration, we run a very generic setup, so if it works for us when I can get one to test, it should work for you.