Thanks for the suggestion, I’ll look into this.

hahaha thanks for the award. I checked the cabling and switching, things seem fine. I had to reboot the machine for some OS updates to take effect and that ended up fixing the issue for now. I’m still curious as to why it was happening. I will definitely poke around in syslog like you suggested next time.

I missed this thread somehow when searching for issues but I’m running into the same problem. I have FOG 0.32 installed on Ubuntu 12.04.

Update: After following the instructions on:

[url]http://fogproject.org/forum/threads/wiki-troubleshooting-an-image-deploy.20/[/url]

I was able to get a screenshot of what I see.

I’ve had FOG .32 installed and running fine for a few weeks now. Today, however, I’m having an issue where when deploying an image to a client, the deployment will stop before it hits 100% then it flashes a different screen briefly. From a video I recorded, it looks like ntfs-3g is complaining that no mountpoints are defined. The weird thing is that this happens with both my WinXP image and Win7SP1 images on different machines. I have to go through multiple attempts to reimage both of my machines before it will successfully complete the reimage process. Right now I’m the only person using the FOG server and have not changed either the images or the client or the server.

I did a quick search to see if anyone else is running into this issue and did not find any. If there are threads that I missed, please post.

[url=“/_imported_xf_attachments/0/171_fog_incomplete_restore_error.jpg?:”]fog_incomplete_restore_error.jpg[/url]

Would it be possible to have the ability to specify parameters to a snap-in per host instead of per snap in? For instance, I have a powershell script snap-in that will set the IP on the machine according to what is returned by corporate DNS. However, since some machines need to join certain domains that corporate DNS does not know about, it needs to have it’s DNS server set to a specific IP. The powershell script has the capability to accept this entry as a named parameter. But not all of my machines need to have it’s DNS server set to a particular IP, and of the machines that need to have it’s DNS server set, there are different IPs for different domains.

Thanks.

I believe I figured out the problem. FOG uploads the script <FOG install dir>/tmp/ since I used the default path, <FOG install dir> equates to \program files\fog, assuming that FOG sends the full path to the executing command, there will be a space in the script name, which would cause (powershell at least) it to croak. I uninstalled and reinstalled into \FOG and that seems to have fixed my issue…

Hi folks, I hope someone can help me with this. I wrote a powershell snapin script to re-IP a machine according to what it finds for the hostname through nslookup. When I run it manually, it works just fine. When I try through fog, it returns with 1. I tried logging stuff to a file, but the file does not get created.

I’m having the FOG server run it with the following (and confirmed the path is correct):

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

I’ve tried running this (through fog and manually) on a Windows XP and Windows 7 systems and it consistently fails through FOG, but works manually.

Anyone have any ideas?

TIA