Posts made by Wayne Workman

I wonder if there’s any way to make it work if there are no existing partitions…

[quote=“sourceminer, post: 44591, member: 29126”]Sounds good Tom, I was hesitant to use the Development build for obvious reasons. For the record 1.2.0 is the version I downloaded from the Sourceforge link on the home page: [url]http://sourceforge.net/projects/freeghost/files/latest/download[/url]

I will attempt to use the latest development build located here:
[url]http://www.fogproject.org/wiki/index.php/SVN[/url][/quote]

If it wasn’t for the development versions, FOG wouldn’t work in my environment.

[CODE]php -v[/CODE]

Resource used:
[url]http://serverfault.com/questions/296156/how-to-check-my-php-and-mysql-version-on-ubuntu-vps[/url]

#LetsMakeScripts

Maybe just double check to be sure? See if this command will run:
[CODE]sudo ufw status verbose[/CODE]

And, if that works, you could do something similar to turn the firewall off (if it’s on):
[CODE]sudo ufw disable[/CODE]

If those commands don’t work, you can use the iptables command:
[CODE]sudo iptables -L[/CODE]

Resources used:
[url]http://www.howtogeek.com/115116/how-to-configure-ubuntus-built-in-firewall/[/url]
[url]https://help.ubuntu.com/community/IptablesHowTo[/url]

#LetsMakeScripts

Make sure NFS service doesn’t have any errors…
[CODE]sudo service nfs-kernel-server status[/CODE]

Make sure the FTP service doesn’t have any errors…
[CODE]sudo service vsftpd status[/CODE]

You can restart the FTP service like this:
[CODE]sudo service vsftpd restart[/CODE]

Check what’s allowed in/out of your firewall:
[CODE]iptables -L[/CODE]

And, here’s some stuff Tom posted earlier here. I think you should try these commands again to see if it helps.
[CODE]sudo service FOGMulticastManager stop
sudo service FOGImageReplicator stop
sudo service FOGScheduler stop
sudo service FOGMulticastManager start
sudo service FOGImageReplicator start
sudo service FOGScheduler start[/CODE]

#LetsMakeScripts

Where was the log file located? Where on the FOG server?
Is it in a different place than /images ?

[quote=“Tom Elliott, post: 44511, member: 7271”]To be honest I have know idea. I know the undionly files only use the nics PXE driver called undi. The ipxe files use the iPXE drivers but I don’t think there’s any difference using Pxe kpxe or kkpxe of the ipxe named files. I simply build them because why not. I’m glad it works for you. What I do know is we default to undionly files mostly because it works on most nics without needing to know what model of nic you have. The drivers ipxe builds do not include every nic so it’s most likely not going to work for all systems.[/quote]

Which is where DHCP classes and DHCP policies must come into play…
Still working on this… I haven’t looked into it for a good while (spring break, woot!).

But, when I do (and get it working), I plan on writing some very through documentation for the WiKi that is specific to ProxyDHCP and Windows Server 2012 DHCP.

You must also be sure that FTP is actually running on the FOG server.

[CODE]sudo service vsftpd restart[/CODE]

If it’s not configured right, it should give some errors which will help.

This could also be firewall related, potentially.

[quote=“Joseph Hales, post: 44533, member: 18131”]The usual issues are the tech starting the task is not following thru and the machine is shutdown or an image is sent to a group and one of the machines has been removed or similar issues. Its just a basic housekeeping task because we have such a large site and a large number of admins using fog many of which aren’t under my control or very technically orientated.[/quote]

It might be possible to create a separate service that runs independent of FOG, that periodically looks through the active tasks and gets rid of the old ones… based on an expiration amount-of-time set in a .conf file…

I’m learning C++ at the moment, it won’t be long till I’ll be able to write such a thing.

[quote=“Tom Elliott, post: 44517, member: 7271”]I’ll have to take a look at the code.

I do purposely tell the GUI to download the oui.txt from the website. This is done not to make things difficult, but ultimately to try making things simpler. I suppose one method, if you can, is to temporarily connect the fog server to the internet, perform the MAC Address Listing Update, then disconnect.

I didn’t add any checks to see if the file is already present because often times the file is outdated at that point, which is why I attempt to get a new file every time.[/quote]

Tom, is this a non-blocking method?

[quote=“Junkhacker, post: 44558, member: 21583”]i’m tracking down why the early hostname change isn’t working and trying to create a fix. you’ll need to update your server to get it when it’s finished.[/quote]

From what it sounds like (to me, anyways) is that the hostname changer (immediately after imaging completes) is looking to change the name on the C:\ partition, where Windows core files are normally located.

Chris Shanks said he changed the location to E:.

I think FOG is just trying in the wrong place…

[quote=“Steven B, post: 44546, member: 24174”]After being told by our network group that multicast was enabled on the production switches on Monday, we found out yesterday that only one of the two switches supports layer three. The ports in the labs are randomly patched into the switches, no documentation. Wire rack is locked, etc…

Ran another test this morning. 15 thin clients using production switches. Start the multicast, all systems pxe and sitting on gray screen. Multicast not starting. Go into the task list the ones in the group that are ready are patched to level three multicast. The ones that are still connecting were patched to the layer two switch. Made bets with network guys. Killed task. Created a new group with thin client members that were waiting in the first job (six computers). Started multicast, executes perfectly. I’m very lucky to have had the fog server randomly patched into the switch with layer thee capabilities. I had given up on multicast last summer.

Four years I’ve been using FOG now, always hear it from the networking group that there is nothing wrong. But they put in all into emails so now it is documented. Getting my own switches this summer.

126GB in 23 minutes is just shy of the 20 minutes (the fastest it could go), the only limitation for the multicast was the GB network cards.

Now if I can figure out the TFTP Boot errors…[/quote]

Well, that’s a big jump from where you were before.
We should be able to help with the TFTP errors. I’ll read through this thread again and update this post if I think of anything.

---

Just read through the thread again. Didn’t see anything about TFTP.
You’ll need to post the errors you’re seeing. A picture of them would be fine, too.

The factory images these things somehow… they should offer imaging services before shipment IMO.

It really sucks that we couldn’t get this going faster…

But, seeing that this IS a windows tablet, your imaging needs for them are not likely to just go away. You’ll probably have to come back to this problem sooner or later. IMO, I think we should work towards a solution for these before then.

Did you experience an image going missing?

What distribution of Linux and what version?

When was the last time this machine was re-booted?

Have you tried this FOG build on a regular machine? Like, a physical machine and not a VM?

Can you walk over to the switch that FOG is using, and plug into (the same v-lan if you have them) a port using a laptop? Try to boot from network and see what happens?

[quote=“sourceminer, post: 44331, member: 29126”]Wayne, ran your commands and didnt change anything.
What is interesting is the messaging from the PXE Boot next server: 10.0.7.1 (what happened to 10.0.7.68?)
[IMG]https://www.dropbox.com/s/co56w10cqkakfjy/2015-03-24_13-19-50.jpg?dl=0[/IMG] [url]https://www.dropbox.com/s/co56w10cqkakfjy/2015-03-24_13-19-50.jpg?dl=0[/url]

I guess I will have to do a wireshark.[/quote]

the next-server should be the FOG server. That’s set with option 066 (i think) in Windows Server DHCP. There should only be a next-server if you’re using ProxyDHCP. (someone correct me if I’m wrong?) But, the DHCP options shouldn’t stop you from getting a file via tftp.

Maybe back to the basics…
[url]http://fogproject.org/wiki/index.php/Unable_to_connect_to_tftp_server[/url]

Double check those fields are right…

I also recommend WireShark, as Uncle Frank suggested.

I am almost positive it’s your unattend.xml file.

Maybe double check your syntax, spelling, spacing, is it case sensitive? Do you need double quotes? single quotes?

I wouldn’t know because I don’t use sysprep… just kicking around ideas for you.

Set permissions on you tftp boot directory:
[CODE]chmod 777 /tftpboot[/CODE]

Restart the TFTP service on Debian:
[CODE]service tftpd-hpa restart[/CODE]

Also, you might wanna check these files to be sure there’s no craziness going on in there:
[CODE]/etc/hosts.allow
/etc/hosts.deny[/CODE]

Have you tried to access the tftpboot directory from another client that has it’s firewall turned off?