Since the latest update, FOG seems to not be renaming.
-
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
-
@x23piracy Fog can be downgraded if i remember well (svn)
-
Downgrading FOG is not supported as the DB schema is changing and we don’t revert those changes when going to later revisions. It might still work in some cases (not too many DB schema changes in between) but you could also run into serious trouble… Don’t do it without snapshot or backup first I’d say.
-
@Sebastian-Roth oups, sorry for bad information…
-
So I have updated this morning and it seems to be renaming correctly. What exactly was the issue?
-
@EAHarvey in trunk there are always bugs, try to find it here: https://github.com/FOGProject/fogproject/commits/dev-branch
Regards X23
║▌║█║▌│║▌║▌█
-
@EAHarvey I can only think of two potential avenues.
My edits to the init to include the ActiveComputerName, or Microsoft pushed another update that fixed a previous update that broke renaming. I really don’t know though. I am going to side with the ActiveComputerName flag for now.
