BigDaddyTeemoe

Glad it worked out. Let us know if/how you get the broadcast groups going.

I'm not up to speed on IGMP snooping, but I do know a lot of switches let you organize particular ports into a group with group specific settings for things like multicasting. If these devices are dedicated to those ports on the switch, you might want to look into the documentation of the switch and see if you can enable this type of setting.

http://www.youtube.com/watch?v=qHeHTaB9LTg

Our network configuration is put together with duck-tape and popsicle-sticks. The way I have to set it up is with multiple Linksys 8-port switches on a stand alone network which means no AD integration. So, yes, I can get it to work across multiple switches, BUT, they're pretty basic switches. So if you had something where you can make certain ports only talk to specified other ports, you might want to check that out. It's been a while since I've had this problem, but when it runs the stdin.001 error, is it after the image has downloaded to the machine and at 99% it shows this error? Or does it happen before it even tries to download the image when its mounting drives and what not? If it's the former, it's probably a image type issue. If it's the later, it's probably an ownership issue.

BUT, to answer the solution to my previous problem, yes, I fixed it. It was a combination of two things: 1. Image type - I had the image type set to "Multiple Partitions - All Disks" instead of "Multiple Partitions - Single Disk." I don't know why, but in 0.28, All Disks worked. But in 0.29, we had to change it to single disk. 2. File Permissions - My supervisor came in one day and said he, "Changed some stuff on the server." Which typically means he broke something. His solution when something goes wrong is to completely format the whole thing instead of tracking down the problem. He would then copy the compressed image files into the image directory, BUT when he did that, he didn't change the ownership of that directory to /root. I think it's something like: or The first changes only the image folder you specify, the second changes anything in the /images directory. If you try to do this from the "properties" menu GUI instead of in the command terminal, it probably won't work. Also, a lot of people said they used "chmod 777." This also didn't work for me.

I've tried a couple of different scenarios. But it was always in Win7 where the netdom path either wasn't installed or the fogservice netdom filepath was set for xp rather than Win7. This was in the first month I had ever been introduced to FOG or anything like this, before I understood how it all worked. I'm going to start trying it again, as I have to re-image some of the machines for updates, this time on a static network with Fog0.30, which doesn't use netdom. I'll update whatever I figure out.

At the time we were using 0.28. I have since upgraded to 0.29 but have not attempted to set-up a FOG server on the Network. Do you know what the fix is or what it does to join the domain?

I haven't seen a post to this, so I'm assuming it worked? However, I could use some help with this issue as well. We were deploying a whole gaggle of netbooks to our School district that came loaded with XP. For whatever the reason, my Boss decided he wanted to run Win7 instead (not accounting for the fact that Win7 doesn't like single-label DNS, which some of our older Win2000 Servers have). We have always been able to image Win7 no problem, but have never been able to run it on our network, only as a stand-alone server on its own network...which means no AD integration. Here's what I've found. Win7 has NETDOM, it's just not installed. This guy has a pretty good article on how to install it. However, that's only half of the battle because the file path for NETDOM is different between XP and Win7. I suspect this matters because I stumbled upon a config file by accident when rooting through an XP hard-drive looking for something else. I do not know exactly what procedure FOG goes through when joining a workstation to a domain. BUT, I do know that the following file exists in XP after you have installed the FOGClient: In that file,on or about line 95, is: Since I have never seen Hostname Changer in action, I don't know if this has anything to do with it. My second issue is that, the FOGClient will not install onto Windows7. When we attempted to installed, an error popper up stating the Fog service had already been installed and then the install canceled itself. So, unfortunately, on a Win7 workstation, I couldn't even mess with the aforementioned issue. If anyone out there in Internet-Land happens across this post, please let me know of any similar issues!

FOG 0.29 running on Ubunutu 10.10 I ran in to this error while deploying a multicast image to about 4 workstations. It gets to 99% and then: Volume not found Can't read the following volume file: /stdin.001 Enter another full path (directory & name) After that, there's a field where I guess I'm supposed to enter the new file path and options for "Ok" or "Cancel". Kind of stuck. Don't know where to go from here.

Having the same issue. We use a portable FOG Server (Ubuntu on a Laptop) and had just reinstalled about two weeks ago. I even just loaded an image last night, went to load another this morning and I got this error. Ubuntu 9.10 running Fog 0.28