FOG Wont change hostname or add to domain

cojohnson

Hello all,

I upgraded to trunk a few months ago. Now, my windows computers are not being joined to the domain or getting there hostname changed by FOG. ( It was working before. ) I am running Trunk 7410 and have the FOGService.msi installed on my clients. They are not talking nicely.

I have the FOG_AD_DEFAULT_PASSWORD set to the plaintext password in FOG Settings --> Active Directory Defaults. I also have our Domain, and Domain Account configured as well.

Any suggestions?

Here is my fog log

 6/6/2016 8:08 AM RegistryHandler 64 bit registry detected
 6/6/2016 8:08 AM Middleware::Communication URL: http://10.21.0.105/fog/management/other/ca.cert.der
 6/28/2016 10:54 AM Bus Became bus server
 6/28/2016 10:54 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 6/28/2016 10:54 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 6/28/2016 10:54 AM Client-Info Version: 0.9.10
 6/28/2016 10:54 AM Middleware::Communication URL: http://10.21.0.105/fog/management/other/ssl/srvpublic.crt
 6/28/2016 10:55 AM Middleware::Authentication ERROR: Could not get security token
 6/28/2016 10:55 AM Middleware::Authentication ERROR: Could not find file 'C:\Windows\system32\token.dat'.
 6/28/2016 10:55 AM Data::RSA FOG Server CA cert found
 6/28/2016 10:55 AM Middleware::Authentication Cert OK
 6/28/2016 10:55 AM Middleware::Communication POST URL: http://10.21.0.105/fog/management/index.php?sub=authorize
 6/28/2016 10:55 AM Middleware::Communication Response: Success
 6/28/2016 10:55 AM Middleware::Authentication Authenticated

 6/28/2016 10:55 AM Bus Registering ParseBus in channel Power

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 6/28/2016 10:55 AM Client-Info Version: 0.9.10
 6/28/2016 10:55 AM ClientUpdater Running...
 6/28/2016 10:55 AM Middleware::Communication URL: http://10.21.0.105/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=8C:A9:82:7B:85:00|8C:A9:82:7B:85:01|E8:9A:8F:2F:69:1F|&newService=1
 6/28/2016 10:55 AM Middleware::Communication Response: Success
 6/28/2016 10:55 AM Middleware::Communication URL: http://10.21.0.105/fog/service/getversion.php?client&newService=1
 6/28/2016 10:55 AM Middleware::Communication URL: http://10.21.0.105/fog/client/FOGService.msi
 6/28/2016 10:55 AM Data::RSA FOG Project cert found
 6/28/2016 10:55 AM ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 6/28/2016 10:55 AM Bus {
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 6/28/2016 10:55 AM Bus Emmiting message on channel: Update
 6/28/2016 10:55 AM Service-Update Spawning update helper
 6/28/2016 10:55 AM Bus Registering ParseBus in channel Power
 6/28/2016 10:55 AM Update Helper Shutting down service...
 6/28/2016 10:55 AM Service Stop requested
 6/28/2016 10:55 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 6/28/2016 10:55 AM Bus Emmiting message on channel: Status
 6/28/2016 10:55 AM Update Helper Killing remaining FOG processes...
 6/28/2016 10:55 AM Update Helper Applying MSI...
 6/28/2016 10:55 AM Update Helper --> msiexec /i "C:\Program Files (x86)\FOG\tmp\FOGService.msi" /quiet USETRAY="1" HTTPS="0" WEBADDRESS="10.21.0.105" WEBROOT="/fog" ROOTLOG="1"
 6/28/2016 10:55 AM Update Helper Starting service...
 6/28/2016 10:55 AM Main Overriding exception handling
 6/28/2016 10:55 AM Main Bootstrapping Zazzles
 6/28/2016 10:55 AM Controller Initialize
 6/28/2016 10:55 AM entry Creating obj
 6/28/2016 10:55 AM Controller Start

 6/28/2016 10:55 AM Service Starting service
 6/28/2016 10:55 AM Service ERROR: Could not clear last session data
 6/28/2016 10:55 AM Service ERROR: Access to the path 'FOGUpdateHelper.exe' is denied.
 6/28/2016 11:05 AM Main Overriding exception handling
 6/28/2016 11:06 AM Main Bootstrapping Zazzles
 6/28/2016 11:06 AM Controller Initialize
 6/28/2016 11:06 AM entry Creating obj
 6/28/2016 11:06 AM Controller Start

 6/28/2016 11:06 AM Service Starting service
 6/28/2016 11:20 AM Main Overriding exception handling
 6/28/2016 11:20 AM Main Bootstrapping Zazzles
 6/28/2016 11:20 AM Controller Initialize
 6/28/2016 11:20 AM entry Creating obj
 6/28/2016 11:20 AM Controller Start

 6/28/2016 11:20 AM Service Starting service

Wayne Workman

The log shows the client updating from 0.9.10 to something else and failing with an access denied error.

What version and bit of windows?

Also alerting @joe-schmitt

cojohnson

64 bit and windows 10. I am signed in as the local administrator

Is there a way to get the updated client?

Thanks for your speedy reply!

Joe Schmitt

Well this is odd. The access denied is of no concern. What’s odd is that the service is starting back up, somehow fails, and retries starting back up. If you restart the machine does the service run?

cojohnson

@Joe-Schmitt

OK. I just restarted the computer and the FOGService is stopped. The startup type is set to automatic so it should be running.

I also cant just click start it pops up and says Error: 1067 The process closed unexpectedly

cojohnson

@Joe-Schmitt

0_1467204738332_fog.log

Joe Schmitt

@cojohnson First thing, that is v0.10.0. Secondly, if you haven’t already, update your server. There was a patch server side to prevent those null object reference errors.

cojohnson

@Joe-Schmitt

OK. Thank you. What is the latest version of the FOG Client and can i get it when i update my server?

Tom Elliott

@cojohnson Simply update your server and you will get the latest version automatically.

Joe’s coded the fog client so it auto updates, which is checked first on the server.

You won’t (hopefully) have to do anything special to get updated. Simply update to the latest trunk version and your clients should start auto updating themselves to the current FOG Client version (0.11.2 as of this writing).

Joe Schmitt

The important thing is that you upgrade your server. Until you do that the clients won’t be able to talk to it. When you do update it, your clients will automatically upgrade to 0.11.2 if that feature is enabled.

FOG Wont change hostname or add to domain

218

11.7k

17.2k

154.7k