Since the latest update, FOG seems to not be renaming.
-
@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.
-
@x23piracy I don’t think this was because of a “bug” persay. Considering everything was working fine, then one day it just stopped.
-
@Tom-Elliott ok roger that. Thanks so much.
