You can use the quick image function, but in the FOG UI your quick image will need to be set to whatever image that machine needs.
Or like Junk said, you can install the capone plugin.
[url]http://fogproject.org/wiki/index.php/Capone[/url]
[url]http://fogproject.org/wiki/index.php/Plugins:_Capone[/url]
Found the issue, resolved in revision 1717. Please update your FOG version.
It seems like there is a bad call somewhere as the actual name for the printer class is PrinterAssociationManager.class
We are looking into this right now.
I have updated the wiki to avoid further confusion. The 192.168.1.1 that you chose at the beginning of the install IS the ip you want to use, not 192.168.1.5.
Make sure to put
[QUOTE][FONT=monospace][COLOR=#000000]/fog/management[/COLOR][/FONT][/QUOTE]
after the ip or you will just get a “It works!” page from Apache(the web service).
[QUOTE][FONT=Consolas]Access denied for user ‘www-data’@‘localhost’ (using password: NO) in /var/www/fog/lib/db/MySQL.class.php on line 253[/FONT][/QUOTE]
That is your problem, that’s also what is generating 95% of those error messages.
Basically it has no connection to your MySQL database.
The database is running as it gives the access denied, did you set a MySQL password when you originally installed?
If so you need to enter that password in /var/www/fog/commons/config.php
The error in red means you need to change your FTP password under the fog UI in the storage management section.
Is MySQL running? If no password is set my guess would be that MySQL failed to start for some reason.
Instead of checkout run an update for SVN and install again. It will use the same settings you used the first time but update to the latest release.
One of the last few releases had some issues with the init files but that is resolved now.
[CODE]svn up /opt/fog_1.0.0[/CODE]
[FONT=Arial][COLOR=#000000][SIZE=12px]then[/SIZE][/COLOR][/FONT]
[CODE]cd /opt/fog_1.0.0/bin/
./installfog.sh[/CODE]
What revision are you on, can you try the latest?
Is this on any host you try or just one host/model of machine in particular?
According to the iPXE forums that is the new error message for DHCP failing. I myself have never encountered that error.
[url]http://forum.ipxe.org/showthread.php?tid=7142[/url]
Is there a switch between the FOG server and the client, if so has this server worked previously to image clients?
Did you tell Linux to install as LVM? FOG will only work with EXT formats for Linux.
If you install as EX3/4 33b will work.
To see if LVM is set up type lvdisplay into a terminal window and if it displays anything it’s set up as LVM.
Make sure you do not have the user listed as domain\user. 33b already adds the domain onto the user for you.
Check all of your AD settings under fog settings AND that host.
And after that, did you use FOGCrypt to set the AD password, if not:
[url]http://www.fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting[/url]
IF you were able to have the server configured for pxelinux.0 in what situation would a user not be able to get it updated to undionly.kpxe?? I don’t know of any organization that locks out their DHCP server, and if they did I doubt they would have the ability to use FOG as a PXE server to begin with.
There is always SOMEONE who can access and change the DHCP server, if not, you have bigger problems to worry about than the FOG install script.
What kind of image did you use for the upload(single disk/part resizeable, multipart single disk, raw, etc), what version of FOG are you on, and what is the OS for the server?
Don’t use fog .32, use SVN to install fog 33 1.0, check the wiki for SVN setup and it will walk you through everything.
I wouldn’t recommend using Ubuntu 14.04 as it’s very very new…
My uploads run about an hour on full compression on any of my machines, but it then allows for 11-13 minute deployments.
It’s worth the wait so i’d leave the compression maxed unless there is some reason you need to upload faster.
You only upload once in a great while, you deploy regularly.
Definitely. That is what i’ve already done, just wanted people to know they don’t have to build a new one to deploy, they can use the old one. But yes, they should definitely upload a new image after that.