Posts made by Tim.Trageser

I will update to the latest SVN.

I have a generic syspreped image that I use for my imaging and as I said everything was fine before I had updated FOG, I didn’t need to add anything extra.

I am running SVN 4290 on Ubuntu 14.04.

I was running svn 35?? and not having any issues. Two days ago I updated to 4290 and the two systems I have imaged since required me to go into Disk Management and expand the main partition.

What do I need to look at to fix this?

Is there a way to have the .fogsettings file update the parts that have changed since my last install like the storage location?

Just curious to see if I can reduce the things I have to check before updating to trunk.

Is Sourceforge backup? Just want to check as I am still getting the same error as above and want to make sure it is not me.

Okay so I set the default Kernel to 3.0.1:

But now I get this when I try and do a New Registration on teh Win 8 VM:

I have the Virtual Drive set to IDE should I try SATA?

How do I check that it is in fact setting it to default.? The FOG Configuration Screen shows 4.0.4 as the Default Member and none of my Hosts have the Kernel set.

I see where I can download older Kernels and where I can assign a specific one to a Host, but how do I tell FOG to use a specific Kernel for unregistered machines?

When I download an older Kernel FOG Configuration doesn’t change and I can’t figure out where to change it.

Just as an FYI, I am having the same Kernel panic issues with a VM and Win 8 that others on the forum are having, but since the panic happens when I try and register the Host I can’t use the Host screen to specify using the 3.0.1 Kernel.

Make sure your permissions are all set correctly and look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#You_must_first_upload_an_image_to_create_a_download_task

@Wayne-Workman That is great! I will try it and see if it works thanks.

That is what I did. I will say I haven’t rebooted in a while so not sure if it worked for me but that is what I did.

@nengelhardt Sorry, I should have added what you want is to look at the post above Tom’s. It is the link he just posted above. I was trying to give you all the info rather than just the fix.

Look at this post it has your fix: https://forums.fogproject.org/topic/5120/issue-with-fog-server-after-running-updates-on-ubuntu-14-04

In that case I am pretty sure @Tom posted in another forum a potential solution, though I don’t think it covered both of the services you are having an issue with. I will see if I can find it.

I am having a similar issue. With VMware Workstation 11. Are there any significant drawbacks to using the older Kernel? I don’t want to break my Win 7 imaging capabilities.

WHat Linux OS are you running? I am going to Guess Ubuntu. Also just incase it matters what FOG version?

@cmcleod Have tried restarting your FOG Server or the FOG Services? Were you having any issues before you upgraded?

For the time being I am on 3501, once I get through the bunches of systems I have to image I will be keeping up with trunk, just don’t need anything to break right now, so staying put where I got it working.

I will just update to SVN later on and be good to go with the Kernel.

I can’t find much on this so I figured I would ask and get clarification: To upgrade the kernal do I just go to FOG Configuration -> Kernel Update and Download the latest Published Kernel, or is there more I will need to do after that.

Thanks!

I am going to go out on a limb and make a suggestion. If you can use the same image in a different LAB and the FOGService is able to connect then you should compare the Network path between each Lab to the FOG Server. It sounds like something is different.

I had that error the other day when trying to image from my USB connected External Drive. Issue was the exports file. Might be worth looking at.