Well, I was doing it all wrong.
I just installed ubuntu on another server, and created a node.
The instalation gave me the user and the pass for that node, but now when I add another storage to fog it cant connect to the graphics

but I go the info from the server
[CODE]General Information
Storage Node teste
IP 172.17.2.6
Kernel 3.13.0-30-generic
Hostname fognod1
Uptime 16:30:15 up 11 min, 2 users, load average: 0.01, 0.12, 0.14
CPU Type GenuineIntel
CPU Count 8
CPU Model Intel® Xeon® CPU E5335 @ 2.00GHz
CPU Speed 1995.017
CPU Cache 4096 KB
Total Memory 12016
Used Memory 612
Free Memory 11404
File System Information
Total Disk Space 263.95 GiB
Used Disk Space 4.37 GiB
Network Information
eth0 Information
eth0 TX 554.07 KiB
eth0 RX 13.59 KiB
eth0 Errors 0
eth0 Dropped 1284
eth1 Information
eth1 TX 574.5 KiB
eth1 RX 39.71 KiB
eth1 Errors 0
eth1 Dropped 0
lo Information
lo TX 2.92 KiB
lo RX 2.92 KiB
lo Errors 0
lo Dropped 0[/CODE]

What do you mean by the storage password? The Storage Node username/password AND the FOG_TFTP_FTP_USERBNAME/PASSWORD?

I’m going to guess this is what you mean.

You’re probably running a “default” style install of FOG. The FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD are what’s used to download new kernels to your FOG system. The Storage Management Username and Password are what’s used to upload images to your FOG Server. In a “Default” install, these are typically both the same because the Storage Node and the tftp and kernel/init files reside on the same exact host. This is why there’s “two” identical fields. That said, The Node does NOT need to be the same if you’ve separated the node from the FOG Server itself.

The Username and Password in these fields are the *NIX fog user account created during install. This username and password can actually be used to log in to the terminal or console of your FOG server albeit with limited use as it’s not an administrator account nor is it given sudo permissions.

The Config.class.php file holding area for this information is ONLY used during a fresh install. Why they’re blank in your setup I don’t know, but you can get this information from the /opt/fog/.fogsettings file as well. The Username is almost always going to be fog, but the password will be stored in a variable called password within this file.

Hopefully this helps.

I had the same problem.
You must set a correct value for the imageOSID field in the images mysql table.
1 for XP, 5 for Win7, etc…

[quote=“Tom Elliott, post: 31969, member: 7271”]
The path should be different and be set to whatever it is that you mounted the new hdd to: for example /mnt/newFOGImages/

From the command line you’ll need to add the new drive location to the /etc/exports file. Just copy the two lines and paste them below editing the /images /images/dev to match that of the new path for the new drive. Once done save and restart the nfs service.[/quote]

Ok, I formatted the second drive as newFOGImages, and created a folder in there called newImages. So the path should be /newFOGImages/newImages correct?

On the web dashboard I have two storage groups made, one is default, the other is group2. I also have two storage nodes, one is DefaultMember, the other one (I created) is newImages. I created it with the same settings as the default (IP address, etc.) except master node is unchecked, and the path is /newFOGImages/newImages/ instead of /images/

I opened the /etc/exports file and it has this:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

Would I just copy-paste them within that file to look like this:

/newImages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/newFOGImages/newImages/ *(rw,sync,no_wdelay,no_root_squash,insecure)

?

Thank you!!

we have seen somewhat similar issues regarding the reporting of mac addresses before. that is why the undionly.kpxe file now reports the first 3 macs it finds, in case the computer reports network adapters in the wrong order.

batch file should have:

shutdown /r

This will notify all users logged on that in 1 minute the computer will reboot … snapin executes with exit 0 🙂

You could always write a script to uninstall the client service once you’re finished with it and push it out via Group Policy.

“Organizational Unit” now appears to be a drop-down menu (inside Hosts > Active Directory). But putting in the domain admin credentials doesn’t populate the drop-down, and I can’t enter anything in it. Is there a trick?

@deadturtle,

With this methodology, do your systems still talk to boot.php? I thought this was the method I was using for the grub exit system though?

i better answer my question myself. have a look at the wiki

[url]http://www.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options[/url]
[url]http://fogproject.org/wiki/index.php/Include_SystemRescueCD[/url]

That’s excellent news then!

(Was referring to this in 0.32: [url]http://www.fogproject.org/wiki/index.php/Multiple_TFTP_servers[/url])

In that case you could try ipxe.kpxe

Sounds great! Thanks. That’s what I planned to do until I went to go download and saw the FOG VM… that caused me to pause and question.

Thanks for all the replies! Good information to have. I guess what I should probably be more concerned about is the fog server serving up the tftp boot file to every client as they reboot. I imagine at the start of the school year a lot of machines will be booting up at the same time, but only time will tell.

[quote=“Jaymes Driver, post: 30645, member: 3582”]I hit 6 GB/min on 0.32… I have never seen anything image faster than that, but it could be my equipment.[/quote]

on this particular computer, it started at 7MB/min (probably caching and not actual transfer speed being represented here) and it never dropped below 6MB/min for the duration of the imaging process.

you can update right to 1.1.1
make sure you have backups before you try