Oh ok I was able to get it back by copying the image the image management page.php file form the old verison I had before It was in the 3000s build and was able to get the page to load but now when i go to edit a image i get a basic page with no formatting lol

@ch3i said:

@Wayne-Workman said:

@ch3i Can you use a virtual machine this time? Snapshots really honestly are lifesavers!

My server is always virtual. I’m a warrior > no snapshot !

lol, no you’re crazy lol.

Because this was seemingly a one off case, I’m going to solve this. I do believe it was cache, and timing related.

@ch3i Good eye.

@Wayne-Workman this is now fixed. Just rerun the installer and all should be corrected for. It was using a bad call that wasn’t in the source. Just changed out with the fog source for the scripts.

Ok thanks

I have software to deploy software (GPO or I prefer PDQ deploy), but I don’t know the tips to remove it, I’m going to search 😉

No, It was Windows

@ch3i Blame Tom. 😉

@Tom-Elliott Thanks again, Tom.

THis isn’t a bug, but the way the system is designed.

We don’t count upload tasks, by default, as posing any real load on the server as most typically you’re only ever uploading one image at a time. You can change which tasks present as, Slots on the dashboard though.

Fix should be out and running now. 4423 is version, SVN commit number: 3892

I’m still working on it but current trunk should have a better mechanism to handle all of this. Hopefully.

@Tom-Elliott Thank you Tom.

@sudburr said:

What didn’t make sense?

I was rushing, it makes more sense now. Today was really hectic, apologies.

I try to summarize what I’ve found in this new thread here.

Update on this.

I saw a boot menu on SOME hosts, not all hosts. Very strange…

@Matt-Rozema said:

Also, I was changing AD settings **after ** the computers were imaged. Should the Fog service recognize that change and attempt to join them?

Yes, long as all the service settings are checked and the “Join Domain” checkbox is checked.

(EDIT) Unless they are already bound to another domain… 😕 I don’t know how FOG would behave then, but I wouldn’t expect it to behave as intended… simply because that’s not something that would normally get tested… sorry…

Perhaps the @Developers and especially @Jbob could elaborate on this topic.
.

Should be fixed in the current. This includes clear, and proper setting of the legacy field based on the settings.

This is now fixed in svn/trunk/git whatever you want to call it.

I confirmed that it stores the IP and knows that it’s valid.

SVN 3861, FOG Version in cloud is: 4353.

Thank you,

@Wayne-Workman Sorry guys, was doing a Core switch replacement at my job. Imaging still works perfectly, in fact just uploaded an image about an hour ago.