So I have discovered using the debugger.exe that the string I used for my password was causing the characters to change in the database.
Specifically I narrowed it down to “$c” (which is what my password started with) and then any character after that would change the stored password to show “r” in the database.
I have since changed the password I use and the domain join works fine. I assume it has something to do with the fact that maybe the hostnamechanger file thinks the beginning of the string is a variable.

To be clear this same password worked on Running Version: 8169 SVN Revision: 5712.

But I needed to upgrade and it would no longer work.
So this is solved for me but maybe this is a bug in 1.5.4

Re: Active Directory Join Failing

New build - 1.5.4 (Ubuntu 18.04.1)
Client - 0.11.16 (Windows 10)

I am having the same problem as above…went through the commands of the debugger.exe and the domain password is totally wrong as in the above thread.

I put the correct password in the domain password box (not the legacy) and it is plaintext.
This is from the AD global settings and I changed it on the host AD itself too.

I have an older FOG server that the credentials work with but with this it states bad password - because the password it being sent wrong I guess (according the the dump file from the debugger.exe).

Any help would be very much appreciated.

Thank you

@Sebastian-Roth sorry forgot to say when i run the snappin manually the sophos installer does not restart itself

@Sebastian-Roth I dont think so as I can run the snappin successfully after the image is deployed manually. But for automatic snappin run right after deploy it tries to run but the hostname changer starts its reboot and the snappin install fails. Then the snappin will not run again

Just realized this is in the wrong thread, as I created this post by linking from another post in Feature request. I can’t move it where it needs to be or delete it. Can someone please help move this?
Thank you

Re: Fog Client - Snapins run after computer rename/domain join

FOG service= 0.11.0
SVN Revision: 5712

I am having the same issue as thread above - where the snapin works fine if I run the snapin on an already deployed image. However when the snapin runs and tries to install a program automatically after a deploy task the hostnamechanger creates a reboot task and then the snapin client tries to run but then instantly fails the install stating ‘User ERROR: A system shutdown is in progress.’

Any help please?

---------------------------------SnapinClient---------------------------------

22/08/2018 18:57 Client-Info Client Version: 0.11.0
22/08/2018 18:57 Client-Info Client OS: Windows
22/08/2018 18:57 Client-Info Server Version:
22/08/2018 18:57 Middleware::Response Success
22/08/2018 18:57 SnapinClient Snapin Found:
22/08/2018 18:57 SnapinClient ID: 7
22/08/2018 18:57 SnapinClient Name: Sophos Install
22/08/2018 18:57 SnapinClient Created: 2018-08-22 16:45:58
22/08/2018 18:57 SnapinClient Action: reboot
22/08/2018 18:57 SnapinClient Hide: False
22/08/2018 18:57 SnapinClient TimeOut: 0
22/08/2018 18:57 SnapinClient RunWith: cmd.exe
22/08/2018 18:57 SnapinClient RunWithArgs: /c
22/08/2018 18:57 SnapinClient File: SophosSetup_NE.exe
22/08/2018 18:57 SnapinClient Args: --quiet
22/08/2018 18:57 Middleware::Communication Download: http://(FOG-server-here)/fog/service/snapins.file.php?mac=(MAC-here)&taskid=7
22/08/2018 18:57 SnapinClient C:\Program Files (x86)\FOG\tmp\SophosSetup_NE.exe
22/08/2018 18:57 Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Installing Sophos Install”,\r\n “message”: “Please do not shutdown until this is completed”\r\n}”
}
22/08/2018 18:57 Bus Emmiting message on channel: Notification
22/08/2018 18:57 SnapinClient Starting snapin…
22/08/2018 18:57 SnapinClient Snapin finished
22/08/2018 18:57 SnapinClient Return Code: 1
22/08/2018 18:57 Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Sophos Install Installed”,\r\n “message”: “Installation has finished and is now ready for use”\r\n}”
}
22/08/2018 18:57 Bus Emmiting message on channel: Notification
22/08/2018 18:57 Middleware::Communication URL: http://(fog-server-here)/fog/service/snapins.checkin.php?taskid=7&exitcode=1&mac=(MAC-here)|&newService&json
22/08/2018 18:57 User ERROR: Unable to get logged in users
22/08/2018 18:57 User ERROR: A system shutdown is in progress. (Exception from HRESULT: 0x8007045B)
22/08/2018 18:57 Power Creating shutdown request
22/08/2018 18:57 Power Parameters: /r /c “Snapin requested restart” /t 0

Yes, it was indeed the permission problem, all it working now as expected, thank you so very much

@Joe-Schmitt Right good to know, I will see if I can get permissions to create and hopefully that should sort the problem (I’m sure it will) thanks for the info, I will get back here once done.

I downloaded and put the legacy client back on the host and entered my FOGCrypted password in the appropriate field and it joined the domain no problem. Does the legacy client not verify that it is joined? There must be somthing that I am missing when transitioning over to the new client?

So my account has permissions to join machines but cannot create new accounts, or take them off presumably. Would this cause a problem with the new client? Would it be trying to remove and then create the account on the AD again? There shouldn’t be a problem if I can manually join through Windows right?