@Tom-Elliott I don’t know what happened, but due to another issue, I updated to 8440 and the new host joined with no issue. So adding all of the existing hosts to a group and applying AD changes to them took care of those, and the patch to 8440 seems to have changed something that was keeping my defaults from populating on new hosts. Thanks!

I code it but I don’t remember it all, thanks for the assist.

I don’t know how this is a bug.

Things are stored as they were created. The checks are there to prevent people from stealing already in use names. This is intentional. If you really need it case sensitive as a “pretty” factor, delete it and recreate it using the proper case, or manually edit the DB so it is displayed how you prefer.

@Tom-Elliott Yes, it is working now.
Thanks,

It’s ok now, thanks Tom 😉
I add then remove a client to the printer and name didn’t change

Weird… wonder how it got that way?

@Tom-Elliott I do believe that is fixed. As far as I have tested anyway. I will report back if anything changes

Sweet. Ran the delete statement and it fixed the issue. I will pull the latest version down in the morning and rerun the installer.

Thanks for the quick response everyone!

@x23piracy It’s not to be centered on the lines you see, those are just lines. It’s to be centered within the browser dimension.

If the Browser width is too small it will not center, but so long as both sides of the browser are visible, the menu icons will be centered within the browser, not on the lines.

@Quazz

Thanks, it works.

wait… never mind. I’m stupid sometimes.

@Wayne-Workman Likely yes it was working.

@MRCUR 😕 great…

This is fixed - just confirmed it.

@Tom-Elliott
Maybe disable only warnings messages ?
So I mark this resolved
Thanks

@Tom-Elliott Confirmed resolved.

@Matthieu-Jacquart said in Hostname changer is unable to rename computer:

@Tom-Elliott I hope it’s resolved with last client but I can’t be sure…
You can close the case, I couldn’t test more before mid-august…

Yes I can confirm, client 0.11.2 resolves this issue

@Tom-Elliott I will update later today and test again. Load doesn’t seem to be an issue: !(http://imgur.com/fj1wKaU)

Last night Joe and I found a potential issue with the client in regards to the fog client having “bad” data and we patched it. With any luck, bad cycle data should no longer happen and this should be automatically fixed if it was a problem due to the bad cycle data.

@Tom-Elliott Confirmed resolved. Thanks Tom!