Alright, so I found the wiki and reset the password, but I am still getting the same error as above. Any other reasons why this would happen?

Hello…thanks for your reply

I have it installed on Ubuntu 12.2. Fog Version is .032, I just now went to that page and got problem loading page error. ok thanks for the heads up. I know we can use clonezilla along side FOG to get the image done, just didn’t want to have to rely on 2 diff programs.

MYsql is running ‘5.0.51a-3ubuntu5.4’
After modifiying it on the php page, the database also shows the \. If I manually change it in the database SQL throws an error about syntax.
We are going to try username@domain instead. Ill update this post with results.

I would run through all the updates first and see what happens. I would say that upgrading should be your last resort. HOWEVER, depending on what version of Ubuntu you’re running either server or desktop, you may want to look at an upgrade. In my field of work, we have to be on a supported OS or we are fined. I recently upgraded our box from 10.04LTS to 12.04LTS. With 10.04 desktop edition, the support ends in 2 months, April 2013, but the server edition support ends in April 2015. [url]https://wiki.ubuntu.com/Releases[/url] This may not be an issue for you, but it’s a requirement for us, so it may be worth looking into an upgrade.

[quote=“chad-bisd, post: 10842, member: 18”]What Linux are you running? Have you checked /var/log/syslog for clues?[/quote]

it’s running ubuntu 12.10

As far as the logs, i’m not really sure what i’m looking for. I don’t see any errors or anything that failed so i’m not sure what to look for.

We are set up this way because each of our campuses has a different ip range and different domains and it is easier for us to have multiple DHCP servers that have smaller scopes and configurations than one server with large scopes and configurations.

Yes I must add whilst I had a good run with multicasting I now prefer to unicast.

If you use a domain admin account for this, you will most likely fail any kind of security audit including Sarbanes-Oxley if your financial systems are tied to your active directory in ANY way. Even if you aren’t a publicly traded company, it’s not safe to hand out domain admin accounts even if they are easier to deal with in terms of security troubleshooting. While I normally will try a domain admin account during debugging to see if it’s a permissions issue, I do my best to avoid them if at all possible. If I must use one, I must.

If you want to create and use a local account in the workstations administrator group, that will give the FOG service enough rights to the local machine, but may not allow them to access network resources that are not visible to the “Everyone” group on your domain.

There is something special about the local system and network service accounts on Windows in regards to accessing remote service, but I don’t remember them offhand.

Just to let you know of my own personal experiences with FOG setups, I use Ubuntu server 10.04 for the main fog server, I never update it because when I have in the past when I first started using fog I found that things broke (not necessarily to do directly with fog software). I also have a second storage server that I’ve been using that works for me seamlessly on Ubuntu 12.04. I’ve basically stuck to these because I’ve found the platforms solid for what I’m doing.

If you would like help setting up I am sure I could help out and I’m perfectly willing to talk you through the process.

I noticed exactly the same and would just like to add weight to the argument for imaging using the multi-partition single disk option. I think it may be specific to windows 7, not sure.

Hi Rob,

Multicasting does not start on its own. By default if you deploy an image to a group of machines it will unicast. To multicast you will have to go to to “Task Management” and search a group of hosts and there will be a double arrow icon next to the group name that you can click to multicast.

more info here:
[url]http://www.fogproject.org/wiki/index.php/Managing_FOG#General_Tasks[/url]

Cheers

I get this problem sometimes with drives that are brand new following replacement. In my case (Panasonic Toughbook CF19’s) the drives are in easily removable caddies so my workaround is to put them into a machine temporarily and boot the unit from a Gparted live cd, then just create a default MSDOS boot sector. HTH

Glad to hear you got it working.

Disregard, we are cloning a computer right now…I WIN thanks for all of the help!!!

Well I have install a FOG 0.30 in RHEL 6.3, and you must make some changes:

1º) Disable firewall and selinux
[I]#sudo selinuxenabled; echo $?[/I]
if the echo returns 0, the SELinux is enable and you must disable it
[I]#sudo /etc/selinux/confi[/I]g
change the value to disabled
[I]#sudo setenforce 0[/I]
[I]#reboot[/I]
2º) Download the FOG code
3º) You must make some change in some config files:
3.1) Unziped_folder/lib/redhat/config.sh
[I]packages=“httpd [B]php php-gd php-cli[/B] mysql mysql-server [B]php-mysql[/B] tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gcc gcc-c++ htmldoc perl perl-Crypt-PasswdMD5 lftp clamav [B]clamd[/B]”;[/I]
I change the next packages: php53 -> php and add clamd. The php-gettext not exists in RHEL.
4º) download and install the next repositories:
[I]#wget [url]http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-1.el6.rf.x86_64.rpm[/url][/I]
[I]#wget [url]http://mirror.uv.es/mirror/fedora-epel/6/i386/epel-release-6-8.noarch.rpm[/url][/I]
[I]#sudo rpm -i --quiet rpmforge-release-0.5.2-1.el6.rf.x86_64.rpm[/I]
[I]#sudo rpm -i --quiet epel-release-6-8.noarch.rpm[/I]
The EPEL repository is necesary to install htmldoc package.
5º) Run installfog.sh to install FOG
6º) You must config timezone in your php.ini:
[I]#sudo vim /etc/php.ini[/I]
In my case:
date.timezone = “Europe/Madrid”
[I]#/etc/init.d/httpd restart[/I]

Some issues:
*During the install process appears the next error:
[I]Setting up and starting NFS Server…Failed![/I]
Solution:
[I]#sudo service rpcbind start[/I]
*I have config the logwatch to see the freshclam messages, to config it:
Edit the [I]/etc/logwatch/conf/logwatch.conf[/I] file
Add the next line:
[I]MailTo = [EMAIL]miemailaddress@mydomain.com[/EMAIL][/I] (<== your email)
if you don’t want the logwatch messages delete the [I]/etc/cron.daily/0logwatch[/I] file

In logwatch messages appears the ext error:
[I]Notifyclam error[/I]
Solution:
Edit the [I]/etc/freshclam.conf[/I], uncomment and config the next line:
[I]NotifyClamd /etc/clamd.conf[/I]
[I] Error: clamd was not notified can’t connect to clamd through /var/run/clamav/clamd.sock[/I]
Solution: sudo touch /var/lib/clamav/clamd.sock sudo chown clam:clam /var/lib/clamav/clamd.sock

Did you modify the pxe boot menu to add this option? I think in the append line, you could specify that option.

All that HP junk went by the wayside when I had to reconfigure the raid on the laptop anyway. Really don’t know what the issue was sadly, but a new VM and a new install of fog only took a few minutes.

Both Dell and HP laptops seem to be imaging happily with your 3.3.3 kernel.