@Duncan yes.

Is it possible to solve this thread yet?

I ask because I worked on a few systems last week, and they all seemed to have been getting their information and things appeared to be setting properly.

The noted items was if I manually stopped/started the FOG Service on the machines, the default printer setting would not happen, which is (as I recall it) expected as the default setter happens via the FOGUserService, not the FOGService element. When you manually stop the FOGService, the FOGUserService is closed to, but on FOGService start (manually) the FOGUserService is not automatically restarted.

Aha, that’s why I didn’t find that post in a search. Can’t keyword search attached pictures.

Changing mine to

FOG_URL_AVAILABLE_TIMEOUT = 3000

… fixed it for me. Thank you.

Ok, so the interface name wasn’t showing because somehow it was wrong in the storage node’s settings.

I never changed that… so that’s probably something broken with the auto-registering auto-correcting stuff @Tom-Elliott

< https://youtu.be/If3SXJeZzMQ >

I found the isEnabled issue. This was only present on new snapins. It’s fixed for RC-23 (while annoying it’s not as important as the functionality of the client which I’m more focused on anyway, among the other issues RC-22 was released to help correct).

Excellent! Good to know it wasn’t me! Updating now, much appreciated!

@Tom-Elliott Confirmation was made.

RC-22 officially released. Please update and all should be much more betterer.

Found and fixed for RC-22.

@Tom-Elliott
Yep i ran through your instructions and made any relevant changes but the thing that fixed it was adding the user back to mysql, not sure why it disappeared though.

@Tom-Elliott I think you can close, I had to clean registry on these computers but when my image is clean deployment is ok.

Moved back to Bugs. I wasn’t saying this wasn’t a bug, I just wanted to know what the bug was more cleanly.

The bug was the text being written to the database only showed updated for any deleted item. This was due to an ajax check. When we delete something, we are doing so via ajax. The checks were only allowing writing to the db if the item in use was not coming from ajax.

While this is still valid, the change to more appropriately write data based on the action should have been available through user based ajax calls. (You had to interact to login in order to delete an item).

I set one of my hosts to pending and I see what yo’re seeing.

I don’t know german very well so I didn’t know what was being said there. Now I see it says:

“Requires templates to process”

I fixed it. Will be fixed for RC-21.

@Tom-Elliott Yes solved. We need to make an SQL statement though that will set all images that only have one storage group to make that group primary. Because we have a ton of images that have no primary group but also only have one group.

@Tom-Elliott You’re the man, Tom!

Fixed will be released for RC-21.

@Tom-Elliott

Don’t be sorry! Thanks for all you do!

The storms have passed and all sites are back online. I’m not sure how I can verify that the image replicator doesn’t quit if a node is offline. I guess I could setup a test at home but it might not be the same. Because in the real-world OP, the primary group that had the image was MIA. I’m happy you made efforts to solve it but at this moment I cannot confirm or deny they work.

It seems ok this morning

fix after update

thanks a lot !!