Posts made by Fernando Gietz

Really, I don’t understand very well. Both methods of deployment are unicast.
If you use a snapin to deploy or inject the drivers, the deploy time increases.

• deployment + sysprep process + FOG client connects with the server (~5 minutes) + deploy snapin [unicast process] + run SAD
  If you use a Andrew’s method
  *deployment + deploy driverPack (mount a temp folder, mount NFS , download uncompressed model’s drivers [unicast process]) + sysprep

If you put the driverPack into the image, the driverPack’s deployment is multicast process.

• deployment + sysprep process + run SAD
  My driverPack’s size is 84 MB for HP7700, HP7800,HP7900, HP8200, DELL GX620, DELL Optiplex 745, DELL Optiplex 755, DELL Optiplex 760 and DELL Optiplex 780.

This idea is really useful. We have modificated the fog code to make this (we use fog 0.30). We use one only FOG server to deploy images in the different high schools. We have 40~50 technician in the different high schools. Those technicians access to the WEBUI in this new role, they can only see his High school images and not other ones.

I recommend you read the following tutorial:
[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380[/url]
It’s fine…and works.

More interest information:
Tutorial about SAD: [url]http://forum.driverpacks.net/viewtopic.php?id=1449[/url]

Tutorial How to create a 3rd party driverPack :
[url]http://forum.driverpacks.net/viewtopic.php?id=5[/url]

We’ve got to inject the drivers in the c:\drivers folder using a script that is executed after the download process. But this process is unicast.

Sorry for taking so long to respond, I’ve been on vacation.
I did not know that something similar was implemented in FOG. This is the first news I have about it. I’m glad.

Please, Todd, paste your mc_checkin.php code. I try to know where is the problem.

Hi,

I have located where is the problem. When the client runs the fog script, this script call to a web service: mc_checkin.php
[CODE]fog: line 108

else
echo -n " * Checking In…";
queueinfo=wget -q -O - "http://${web}service/mc_checkin.php?mac=$mac" 2>/dev/null
echo “Done”;
while [ “$queueinfo” != “##” ]
do
echo -n " * $queueinfo ";
queueinfo=wget -q -O - "http://${web}service/mc_checkin.php?mac=$mac" 2>/dev/null
sleep 5;
done

fi[/CODE]
In the line 110 calls to the web service:
[I]queueinfo=wget -q -O - "[url]http://${web}service/mc_checkin.php?mac=$mac[/url]" 2>/dev/null[/I]
Print “Done” in the screen, but queueinfo variable is empty. This is the problem.

The mc_checkin.php web service doesn’t work fine. Put checkpoints in the code using “echo” to see where is the problem.
The mc_checkin.php is in /var/www/fog/service directory

Obviously if you make unicast tasks, the kernel shouldn’t be the problem.
I use fog 0.30, probably fog .032 or your version works in the same way.
Life cycle of a multicast task (short version
[LIST=1]
[]You ask to the server to do a multicast tasks (in the web interface)
[]In the fog database:
[LIST=1]
[]tasks table: one registry per client. tasksType=C, taskState=0
[]MulticastSession: one registry. msSTate=0
[]MulticastSessionAssoc: this table links one MulticastSession with “M” client tasks. (1:M relation)
[/LIST]
[]FOGMulticastManager service. This service makes a query, every 5 seconds, to know if there are new multicast tasks. (you can see the FOGMulticastManager log in /opt/fog/log/multicast.log). If the tasks is new:
[LIST=1]
[]Update the MulticastSession.msState=1
[]Create a udp-sender command (see the multicast.log). Create a multicast session in the server.
[/LIST]
[]Send a WOL to the clients
[]The client is awake
[]The client connects with the PXE server
[]the client downloads the kernel
[]the client loads the kernel
[]the client downloads the init.gz file
[]the client loads the init.gz file
[]the client runs “fog” script. This script is in /bin
[LIST=1]
[]the script checks some parameters: OS, image file, …
[]The client update DB, via webservice, and tasks.taskState=1
[]the script mount the /images directory in the server
[]the script makes some thigs more
[]the script runs udp-receiver command
[]Blue screen “Please Wait”
[]All clients links with the multicast session. The download process begins.
[]The download process ends.
[]The client updates DB, via webservice, and tasks.taskState=2
[/LIST]
[]FOGMulticastManager service updates the DB, and now multicastSession.msState=2
[]Multicast task ends
[/LIST]
some questions:
[LIST]
[]Is FOGMulticastManager ON?
[]FOGMulticastManager log?
[]The udp-sender command, is running?
[*]When crashs the client?
[/LIST]

and you can deploy the image using unicast?

[quote=“MadX, post: 1345, member: 456”]

• • • • • • • • … ad. infinitum …
                [/quote]
                And the previous messages??

And permissions? have 192.168.2.5:/media/FOG-Images 777 permissions? The error is “Permission denied”.

I use FOG 0.30, and we schedule tasks every day. Your scheduled tasks appear, not in Active Tasks Section, in Schuduled Tasks section. When the FOGTaskScheduler service detects a scheduled tasks, the tasks appear in Active Tasks Section with the name Scheduled xxxx.

If your scheduled tasks not appear in active tasks section, please check and be sure if the FOGTaskScheduler service is running.

[quote=“SirTimbit, post: 1235, member: 447”]It tries to connect then reports “Failed to connect to DefaultMember.” [/quote]

is the firewall enabled??
Please upload a screenshot.

[quote=“MadX, post: 1203, member: 456”]
Then, the default view for All hosts - can we get a view that filters by group perhaps ?
[/quote]
We use FOG 0.30, and I supose that FOG 0.32 works in the same way. You can solved it:

When you import computers using a cvs file, add in the description of the computer the name of the group. That way if you do a search by the name of the group, you will all PC associated with that group, because when FOG performs a search using the description field of the team.

The official version of FOG, fog project, hasn’t a client for Linux, only for Windows.
Well, we have developed a limited client for FOG, only change the hostname and restart the PC if is necesary.
You can download a rpm version from [URL=‘http://www.ehu.es/fogenehu/download/client/linux/fogservice-0.2-2.noarch.rpm’]here[/URL], Ubuntu version [URL=‘http://www.ehu.es/fogenehu/download/client/linux/fogservice_0.2-1_all.deb’]here[/URL]. You can see the install documentation is [URL=‘http://www.ehu.es/es/web/instalaciones/fogehu/-/wiki/main/guia#Instalación_del_cliente_para_sistemas_Linux’]here.[/URL]
You can download the install document from [URL=‘http://www.ehu.es/fogenehu/doc/client/linux/InstalacionFOGehuLinuxClient.odt’]here[/URL].

OK. When you deploy an image, FOG create a PXE file in /tftpboot/pxelinux.cfg. The filename is =01-XX-XX-XX-XX-XX-XX, where XX-XX-XX-XX-XX-XX is the MAC address of the PC. The file is like this:

[CODE]# Created by FOG Imaging System,
DEFAULT fog
LABEL fog
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=
type=down img=aula-sc-carlos-santamaria-lab-idiomas-tmm mc=yes port=63162 storageip=158.xxx.yyy.zzz storage=158.xxx.yyy.zzz:/images/ mac=xx:xx:xx:xx:xx:xx ftp
=158.xxx.yyy.zzz web=158.xxx.yyy.zzz/fog/ osid=1 imgType=n shutdown= loglevel=4 fdrive= chkdsk=0 hostname=U008298
[/CODE]

FOG uses this file to obtain the configuration variables. Let’s go to see:
[LIST]
[][B]type[/B]=down. This is the tasks type, a download task.
[][B]img[/B]=aula-sc-carlos-santamaria-lab-idiomas-tmm. This is the image name.
[][B]mc[/B]=yes. This tasks is a multicast task.
[][B]port[/B]=63162. This is the port of the multicast task.
[][B]storageip[/B]=158.xxx.yyy.zzz. IP of the storage node.
[][B]storage[/B]=158.xxx.yyy.zzz:/images/. The path where the image is.
[][B]mac[/B]=xx:xx:xx:xx:xx:xx. The mac of the client.
[][B]ftp[/B]=158.xxx.yyy.zzz. IP of the storage
[][B]web[/B]=158.xxx.yyy.zzz/fog/. The path of web interface. FOG uses it to know where the webservices are.
[][B]osid[/B]=1. Type of OS.
[][B]imgType[/B]=n. Image Type.
[][B]shutdown[/B]=
[]loglevel=4
[]fdrive=
[]chkdsk=0
[][B]hostname[/B]=U008298. PC Hostname.
[/LIST]
This PXE file is setup by FOG when you make click in the web interface. To setup it, FOG uses some parameters, those parameters are in the databese “fog”, in the table globalsettings. You can also see them in the interface web “about it” -> FOG settings. Check them. I’m sure that your problem is there.

Sorry, i forget it.
[quote=“giammy, post: 1148, member: 362”]
I imagine that the part of the script fog which prepare the disks miss something:
you say you use a personalized version?
Can you make available the modifications? do they include the script “fog”?
Do you declare the OS in the fog WebUI as Windows or Linux?
[/quote]

[LIST]
[]We use a personalized version, we have modificated the script “fog” but not this point, multisystems deploy. We use fog 0.30.
[]We have reduced the number of options in the web interface. All our images are defined, by default, as windows Multipartition [type = mps and OS = 1]. The script “fog” is clever , and does not trust what we have said. When we upload an image to the server, this script checks again what type of system is: windows XP, windows 7, linux …
[/LIST]

[quote=“giammy, post: 1148, member: 362”]

The image deploy are done correctly, and the MBR is correctly dded on destination PC,
but the system do not boot: if I start with a live CD and do a grub-install everything starts
correctly.

[/quote]

Yes, we deploy multisystems, but when you deploy only a Ubuntu 11.xx system, it crash. The PC reboots constantly.
The solution is simply (you can see it [URL=‘http://www.ehu.es/es/web/instalaciones/fogehu/-/wiki/main/conocimiento#Despliegue_de_imágenes_con_Ubuntu_11.04’]here[/URL] in spanish). Using Google Traductor :
[I]Deployment of images with Ubuntu 11.04
Although FOG not support Linux-based systems, the tool can deploy images with these systems. With the latest release to date, Ubuntu 11.04, we have encountered a problem when displaying images with this system only installed. With dual systems is not presented.
Symptoms: The computer after deploying an image of Ubuntu 11.04, reboots constantly.
Solution:[/I]
[LIST]
[*][I]Create or modify / boot / grub menu.lst file[/I]
[/LIST]
[CODE] timeout 0
Grub title
root (hd0, 0)
kernel / boot/vmlinuz-2.6.38-8-generic root = / dev/sda1 ro quiet splash
initrd / boot/initrd.img-2.6.38-8-generic
quiet
savedefault
boot[/CODE]
[I]

Note: Verify that there initrd and vmlinuz files makes referred to in the menu.lst[/I]
[LIST]
[*][I]Run: (install and configure grub-legacy)[/I]
[/LIST]
[CODE]$ sudo apt-get install grub
$ sudo grup-install / dev / sda[/CODE]
Try it and say, please, if it works.
[I][/I]

Possible solutions:

• Check if the client configuration is well. IP FOG Server
• During the client instlallation process, you set the client to enable restart PC service?
• In the server configuration, you have enabled restart PC Service?

If you make a reinstall of FOG, the installer search the /opt/fog/.fogsettings to see the server configuration. Please, see it and change the file configuration with the new parameters.

Hi,
we deploy Centos and (K)Ubuntu sistems without problems. Are you try to upload a Ubuntu 10.xx image?
If you need deploy a ubuntu 11.xx image, you need make some changes:
*create or modify the menu.lst file
*install and configure the grub-legacy
See the next documentation (sorry only in spanish, but you can use Google traductor )
[url]http://www.ehu.es/es/web/instalaciones/fogehu/-/wiki/main/conocimiento[/url] (see Despliegue de imágenes con Ubuntu 11.04)