This isn’t really a feature request. It’s a bug. I’ve since corrected for this. The only thing you can’t do is set multiples for the same time, but you can set how ever many of any kind. It was only allowing one greenFog entry at all and this was incorrect.

This might fix the issue [url]http://stackoverflow.com/questions/118884/what-is-an-elegant-way-to-force-browsers-to-reload-cached-css-js-files[/url]

Thank you very much! I think that’s it - an ftp password issue. I set the user password and the password in the fog configuration to the same thing and my latest test upload put everything in /images/testimage.

The first two errors derive from FOG trying to check if you clients are up. You can turn this off in FOG Settings -> General Settings -> FOG_HOST_LOOKUP (uncheck and save).

Hi,

Updated to latest version and I haven’t the msi in the client folder.

Regards,
Ch3i.

Edit : Solved using that : [url]http://fogproject.org/forum/threads/latest-development-fog.10556/page-28#post-44440[/url]

I believe its alphabetical what I did was prefix my snapins with a number to force an install order it also helped to put my commonly used snapins at the top of the list.

Seeing as we’re on 3132, I’d recommend updating and seeing if this still occurs.

As far as I remember we changed a couple of things with extended partitions in SVN a few weeks ago. Switching between SVN an older versions could cause trouble I suppose…

Please run a debug session on the client you use to upload the image from, run the following command and copy paste all the output (including warnings and errors) you see:
[CODE]sfdisk -d[/CODE]

3111 fixed it, thanks!

[quote=“Tom Elliott, post: 43684, member: 7271”]inventory.php doesn’t do the registering, only auto.register.php handles this. 3102 should work, but I don’t have multiple macs to test against either.[/quote]

Still figuring out where everything is going. 🙂

I was looking at fog.register, not fog.auto.reg. That would make sense! I’ll see if I can figure out what it is doing for you.

The ideal of FOG is that it works regardless of environment.

It’s also the main reason for the work on the new client. First to make it damn near impenetrable (not wanting others to try but if they have methods to correct and further secure things it’d be much better I guess if we royally screwed it up). Second to make it more efficient (non cyclic based but rather event based) and third just get it more modern and updated. So far the work we’ve done has made sure the client will work at least back to XP but also work properly on 7, 8, 8.1, and hopefully future versions of software all at the same time to attempt a comminized programming experience to integrate with Linux and MAC from a single client point of view.

Also, please try upgrading

You could also try removing them out of the Advanced menu and create individual menu items for each of these, now that you are on a higher revision.

Thank you guys for working on this and making it all run smoothly!

Thank you!

These are expected.

I made a mistake in 3063. 3064 is an attempt to correct those problems, so yes, those errors are totally expected and perfectly fine for the time being.

Thanks Wayne. I will keep an eye on that thread to follow tom’s progresses.

Hi,
thanks to Sebastian, I have found the problem. I haven’t set a password for fog user, and I haven’t put that password in DefaultMember storabe. After doing that, image upload works fine and I have been able to download it.
Other problems remains. But those are other threads.

Thanks a lot Sebastian and Tom.

Issue:
Fog client service will not join AD domain.
…MAC is NULL!
…MAC does not exist!

Cause: MAC class issues

I don t know… I finally reinstall fog from scratch cause i needed to install my clients asap and i gave up svn for the moment.
I red somewhere that it not advice to use svn for prod environment… Maybe i ll try it again but later…