ClientUpdater
-
I don’t know that this is how the file updates. I’ll take a look though, but I was under the impression that client updater updates the client files (HostnameChanger.dll, HostnameRegister.dll, etc…) not run the actual msi package, though I could be wrong.
-
[quote=“Tom Elliott, post: 30300, member: 7271”]I don’t know that this is how the file updates. I’ll take a look though, but I was under the impression that client updater updates the client files (HostnameChanger.dll, HostnameRegister.dll, etc…) not run the actual msi package, though I could be wrong.[/quote]
Thanks let me know if that’s the case and i will just deploy it via a snap in
-
I just tested it and this is what is returned:
[code] 6/14/2014 9:35 AM FOG::ClientUpdater File: AutoLogOut.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : ClientUpdater.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: ClientUpdater.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : DirCleaner.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: DirCleaner.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : DisplayManager.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: DisplayManager.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : GreenFog.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: GreenFog.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : GUIWatcher.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: GUIWatcher.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : HostRegister.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: HostRegister.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : MODDebug.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: MODDebug.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : PrinterManager.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: PrinterManager.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : SnapinClient.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: SnapinClient.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : TaskReboot.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: TaskReboot.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : UserCleanup.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: UserCleanup.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : UserTracker.dll
6/14/2014 9:35 AM FOG::ClientUpdater File: UserTracker.dll does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater Checking Status : config.ini
6/14/2014 9:35 AM FOG::ClientUpdater File: config.ini does not need an update.
6/14/2014 9:35 AM FOG::ClientUpdater 0 new modules found!
6/14/2014 9:35 AM FOG::ClientUpdater Client update will be applied during next service startup.
6/14/2014 9:35 AM FOG::ClientUpdater Client update process complete, exiting…[/code]
I basically put all of the dll’s from the fog service into the DB, and none of them needed an update. Why you ask?While none of the files required an update, this shows you exactly which files are checked for and updated.
Just for a simple test, I edited the config.ini file in the db and tested the client updater server to see if things were all well.
The code returned:
[code] 6/14/2014 9:49 AM FOG::ClientUpdater Checking Status : config.ini
6/14/2014 9:49 AM FOG::ClientUpdater File: config.ini requires an update.
6/14/2014 9:49 AM FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\config.ini hash doesn’t match server hash!
6/14/2014 9:49 AM FOG::ClientUpdater 0 new modules found!
6/14/2014 9:49 AM FOG::ClientUpdater Client update will be applied during next service startup.
6/14/2014 9:49 AM FOG::ClientUpdater Client update process complete, exiting…[/code]This is most probably a BUG at the moment.
Where the bug is I don’t know. I’ll keep testing and see if I can come up with a fix for this.
-
This has been fixed in SVN trunk, thank you.
-
Thanks Tom
-
Is it a bug of fog server or clientupdate? I ask because I am preparing a new image I want to deploy in some days and need to know if I can use current clientupdate.
-
There was a bug in fog and is, as such, still present in the “stable” versions. If you upgrade to svn, this has been fixed downstream.
-
I do not want to create a new thread so i add my similar issue on this.
Related to this topic [url]http://fogproject.org/forum/threads/windows-7-activation-proposal.10745/#post-35495[/url]
i want to exchange the “HostnameChange.dll” on all my clients.So i added the modified dll to the ClientUpdater Configuration:
[IMG]http://abload.de/img/22-08-201411_31_21-foswqyw.png[/IMG]
Activated Clientupdater globally and on the client configuration.
Rebooted the client and checked the fog logfile:[CODE]22.08.2014 11:17 FOG::ClientUpdater Attempting to connect to fog server…
22.08.2014 11:17 FOG::ClientUpdater Module is active…
22.08.2014 11:17 FOG::ClientUpdater Checking Status : AutoLogOut.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : ClientUpdater.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : DirCleaner.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : DisplayManager.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : GreenFog.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : GUIWatcher.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : HostRegister.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : MODDebug.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : PrinterManager.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : SnapinClient.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : TaskReboot.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : UserCleanup.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : UserTracker.dll
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater Checking Status : config.ini
22.08.2014 11:17 FOG::ClientUpdater Zero byte response returned
22.08.2014 11:17 FOG::ClientUpdater 0 new modules found!
22.08.2014 11:17 FOG::ClientUpdater Client update will be applied during next service startup.
22.08.2014 11:17 FOG::ClientUpdater Client update process complete, exiting…[/CODE]What i’m missing is the check for the “HostnameChange.dll” file.
Is this a config issue or is the check missing in the code ? -
I believe it was a check missing in the code for the client.
-
[quote=“Tom Elliott, post: 35692, member: 7271”]I believe it was a check missing in the code for the client.[/quote]
So ClientUpdater.dll need to be edited/fixed?
-
Probably, yes.
Though if you already recompiled the hostname changer file, you can just copy the file to the “C:\Program Files (x86)\FOG\HostnameChanger.dll”
Just before you copy it over, run:
[code]net stop “FOG Service”[/code]After it’s copied over, run:
[code]net start “FOG Service”[/code] -
Of course the way via snapin would be the alternative.
I just wanted to try the clientupdater service for the first time and exactly the required file was forgotten in the sourcode ;(
