No, I detach the uploaded image before creating the image…that has always worked in the past…is that wrong?

I did find this thread: [url]http://fogproject.org/forum/threads/changing-name-works-joining-ad-is-not-but-was-prior-to-upgrade.10568/#post-28063[/url]

So I made those changes - I still had domain\Admin…

Still no dice…

OK, so it seems that the fog client is NOT automatically re-joining to the domain after imaging…any ideas?

Thanks!

Never mind…found the link at the bottom of the page

It seems that my fog client is not connecting since updating to version 1.0.1 from .32. Is there also an update to the client? I cannot seem to find where to download that (I assume somewhere on the fog interface).

Thanks.

Fog 1.0.1
Fedora Core 18

Thanks for all your help and advice! Greatly appreciated guys!

Oh, I assume that now if I want to make a new image of this workstation that I should take the legacy switch off so that it uses partclone going forward?

Thanks!

Well, that was it! Thanks so much for your help!

Thanks! I actually use phpmyadmin for direct dB access, so I’ll log in and change it.

Thanks

The image type is set to partclone. I don’t see an option to change that though. Can you please let me know where to change that?

And yes the image was created with .032

Thanks

I get the message that “this is not a partclone image” when trying to deploy an image to a workstation since upgrading.

Running Fog 1.0.1
Fedora Core 18

Thanks.

OK, apparently nfs wasn’t running, so got it working…but have new problem - will start a new thread.

I am getting the following error when trying to deploy an image to a workstation (have not tried capturing an image from a computer yet).

This was an upgrade from a working .032 install. Checked the logs, and see nothing that relates to that, other than a couple of references to TFTP:

May 22 13:00:09 localhost in.tftpd[1966]: tftp: client does not accept options
May 22 13:15:16 localhost xinetd[853]: EXIT: tftp status=0 pid=1307 duration=2215(sec)

The 13:00:09 log entry is when I started the image, and then I just left it, and on the workstation screen it repeats the error with the number of minutes that it has been running. The second entry is 15 minutes later (and the very next entry). Not sure if it is related, or even anything to worry about, as the imaging process uses NFS, not TFTP

Any help is appreciated.

TIA