Since the latest update, FOG seems to not be renaming.
-
@plegrand what does the clients fog.log look like?
-
@Tom-Elliott
It’s little strange as you can see on the picture, echo %computername% give the good name (same as in the fog interface) But it’s not the same in system property
-
@Tom-Elliott I change name manually then i made some tests from fog interface and it seems to work.
Just after that i had a problem to join to samba domain.
I had to rewrite the same password on active directory field to make it works -
-
Does this issue only present itself on freshly imaged machines? Or does hostname changer also not work if you install 0.10.6 on a machine that was not imaged? (The screenshots you showed us can be caused by an incomplete hostname change which can occur during early hostname change during the imaging process. If that occurs, the FOG client will believe it’s already named correctly even if it isn’t. I’m not saying this is the issue, but we need to eliminate the possibility first.)
-
@Wayne-Workman ok i just updated through SVN and am testing a set of laptops now. I’ll let you know if it works.
-
So it looks like it is changing the %computername% but not changing in windows in system properties.
-
There must have been a windows update that changed this.
Early Hostname Changer was working perfectly fine before.
We need to really figure out what’s going on. I’ll see if I can replicate tonight.
-
I am also seeing this issue, however when I look in the fog.log file it says that all modules are disabled on the server, even through i checked both the host and server level settings. I am using the old fog client (I assume this is supposed to work yet).
I also noticed the hostname didnt change when the machine started up, so the early hostname change didnt work, the image is a Windows 7 image. Fog ver 7597
Anything I can provide to assist in fixing this issue?
-
Same here as neo stated. If I can help please feel free to ask.
-
Might help?
-
@EAHarvey I went over the article, and searched for “name” in it. I don’t see anything relevant?
-
@Wayne-Workman OK no problem. I just found that and thought it might be of some service.
-
I’ve been experiencing the exact same issue with the latest FOG build (7649) on Fedora 23 Server and with the latest FOG client on Windows 7 x86 (0.10.6). My hostname would show as changed when echoing %computername% at a command prompt, but it would still display the old hostname in System Properties. This seems to only be a problem with the “early hostname changer” feature, because when I disabled FOG_CHANGE_HOSTNAME_EARLY under General Settings of FOG Configuration, the client was then able to properly change the hostname after a reimage. I’m not sure if this information is helpful at all, but I wanted to clarify the difference for the thread.
-
@cpattersonit I’m going to try this also. I’ll let you know what happens here.
-
Still did not change.
-
@EAHarvey and anyone else having this issue. Please try updating and deploying to see if this is fixed or not?
I can only think key’s aren’t being changed properly (case sensitive and all), but comparing my Windows 10 box to the keys appears all the case is correct. I’ve added another series of keys in hopes of pinning this down.
-
@EAHarvey only FYI with 7645 renaming is working propperly for me. I know that does not solve your problem but may surround the cause tighter. Can you remember on which build you were before you updated to latest?
Regards X23
-
@x23piracy 7597. Let me update and see what happens. I’ve not updated since we started this.
-
@EAHarvey it’s always good to keep an update of the productive machine before updating. My FOG is virtualized and i easily create a snapshot of the machine within seconds.
Regards X23
