Ahhh okay. That would explain why I’m not seeing them - I currently have a deployment VM as a local guest on my personal machine. I have it bridged, so it would be using my Intel NIC drivers, I believe.
I actually have been intending on pushing this VM to our vSphere ESXi host as well at some point - If I find time I’ll do some troubleshooting, but I haven’t done any uploading from there yet.
Any chance there are some VLAN/QoS settings which are throttling the upload speed?
Really? I haven’t had a problem using VMWare to handle the uploads.
What version of VMWare are you using? And is it player or workstation?
On a side note, you actually can use non-SCSI drives. Getting to that point is anything but intuitive, though.
Upon VM creation, VMWare will force you to start with a SCSI drive. However, before booting, you can open up the configuration for the VM, delete the SCSI device, and upon re-adding a hard disk, you can select IDE – which FOG detects and handles innately with the Kernels it has built in. I tried both ways, and found that just using a VMWare IDE disk was the best solution for us.
Haha good stuff. That’s actually a lot better speed than I was expecting.
unattended.xml should not be required for the FOG system (I think).
If you want to join the domain during the sysprep process, then yes, you will need to set up an unattended.xml file and use sysprep (not necessary for Windows 7, but can still be beneficial).
I’d suggest adding in the following lines right after “ntfs-3g -o force,rw $part /ntfs”:
[CODE]printf “Error Message: $?\n”;
sleep 10;[/CODE]
Or use echo instead of printf. Just to see if there’s anything useful in there.
Tried finding the exit codes online, but it looks like the fastest way to find them would be to pull up the ntfs-3g man page from the console to see what the exit codes are (here’s the reference page which suggests doing that):
[url]http://www.tuxera.com/community/ntfs-3g-manual/#9[/url]
Interesting… $? checks for an error thrown by the previous statement, right? (I don’t have a ton of experience in bash). Maybe the mount succeeds, but technically has an error? $? could have useful information that could be printed. Hopefully, haha.
There is logic to remove the hibernation and page files:
[LIST]
[]FOG_UPLOADIGNOREPAGEHIBER is a constant defined in config.php
[]createUploadImagePackage from functions.include.php makes use of this constant to determine how to set $ignorepg
[]$ignorepg is used by init.gz/bin/fog at about line 746 (search for $ignorepg, I have edited this file a couple times. not sure what line exactly it will be for you)
[LIST]
[]If $ignorepg has been set to 1 by createUploadImagePackage, then the drive should be mounted with ntfs-3g, and pagefile.sys and hiberfil.sys should be removed by rm -f
[/LIST]
[/LIST]
Good luck! Sorry for the wall of text.
If you feel like getting in to it, in order to get the boot package to get sent to the right location, you could take a look at the following lines (for example, inside function createInventoryPackage() in functions.include.php):
[php]
$ftp = ftp_connect(getSetting( $conn, “FOG_TFTP_HOST” ));
$ftp_loginres = ftp_login($ftp, getSetting( $conn, “FOG_TFTP_FTP_USERNAME” ), getSetting( $conn, “FOG_TFTP_FTP_PASSWORD” ));
[/php]
If you feel like getting in to a more “correct” way of doing this, I think the issue with getting the boot files pushed to the correct locations is that $conn is (correctly) looking at the master node since that’s where MySQL lives, so the “FOG_TFTP_HOST” information it receives are the master node settings. I [I]think[/I]. I’m not positive on that. I was thinking of switching it so it gets its information from the config.php file located on the service, but there are a [I]lot[/I] of calls to the MySQL based getSetting function. It might take a lot of changes to rework that.
Alright. Got home from classes, and switched computers so I could grab my notes. Of course I have to say be really careful with all of this: if something goes wrong, it will most likely make your production system not functional. Try to do all this on a test system instead of a production system, if at all possible. At least make backups/take notes of what you all changed.
I have attached the list of my notes of what I all had to change to get it working. I’d attach the files themselves… but I have a lot of other changes inside these files as well, so I tried pulling out the only changes you’d need to get subnet / location based image push.
Couple of things:
[LIST=1]
[]The subnets I’m working with are 192.168.4.0-192.168.7.255, 192.168.14., and 192.168.24.* – make sure you change the instances of this to match your subnets.
[]When FOG determines where to put the boot file named after the client’s MAC address, it is still placed on the master node. With the synchronization methods put forward by that guide, it will be duplicated across all nodes and this isn’t technically an issue.
[]Any changed files need to be sync’d (or at least copied) to the remote nodes from the main node.
[]Here’s the part I feel could be done better: Inside functions.include.php the line “$command=”/sbin/ifconfig eth0 | grep ‘inet addr:’ | cut -d: -f2 | awk ‘{ print $1}’“;” is actually executed on the server side. When I started working on this, I thought it would execute on the client side. The end result is that it still finds the correct subnet, but there has to be a better way to do this. At the very least, all of the array functions wouldn’t be necessary. You could probably just compare full IPs. I have a couple ideas for more sophisticated changes, but I haven’t gotten to test them yet. The joys of being a full time student and trying to do all this in the middle of an IT support internship…
[]So, in order to get this to run correctly, I ran into a few problems – since the folder containing the boot file “default” is being mounted on remote nodes, and since the boot files for specific MAC addresses are also in this location on the main node, I had to keep this mounted. The change involving overriding the “web” variable in S99fog inside init.gz is a workaround. A bit strange, but it works. I need to work out a solution to unmount those drives, and get the specific boot files placed in the right location in the first place. Shouldn’t be too difficult, but I haven’t had the time.
[/LIST]
Let me know if you run into any issues, and I’ll help you the best I can. I’m definitely not a FOG expert, by any means, but I’ll try.
[url=“/_imported_xf_attachments/0/303_fog_location_changes.txt?:”]fog_location_changes.txt[/url]
Yup! … Well, sort of. I don’t really do the delegation - it just picks it automatically based on the subnet. I’m actually at school right now, and all my FOG notes / custom changelogs are stored on my work computer which I don’t have with me. It actually ended up being slightly more complicated than just a few changes.
[url]http://www.fogproject.org/wiki/index.php/Multiple_TFTP_servers[/url] <---- this is a good place to start. I have two remote nodes that both started with this setup (almost - my rsync setup is slightly different as I have more files I want to synchronize than suggested).
Off the top of my head, I know it’ll take edits of about 3-4 PHP files, as well as a change somewhere to ensure that the bash WEB= variable set by the boot files is correct. Maybe. Currently I have it set up so the node you PXE boot through is the node that gets chosen, but it gets chosen in a strange roundabout sort of way. I might actually do some rework to get it working in a way that makes more sense, now that I actually know what’s going on.