HostnameChanger question


  • Developer

    @chunter2 While I am not exactly sure I’d still think this has nothing to do with Samba NT 4 vs. Samba AD!

    I’d suggest you try this:

    • Start the client, login as admin, open services.msc and set FOGService to manual start
    • Reboot the client
    • Login as admin again, open cmd shell and run net session, take a picture and post here
    • Try to disconnect all open sessions net del ...
    • Open services.msc, start FOGService and keep an eye on the log to see if it still fails with the same 1219 error


  • @Sebastian-Roth I’m still running an NT4 domain not an AD domain so I’m pretty sure I don’t have any GPO’s? I’m not sure where I’d look for any other tools or scripts on my server. Or are you thinking in the Windows 7 images itself? I’ve been putting off figuring out how to migrate a Samba NT4 domain to a Samba AD domain although I know I need to do that soon.

    Thanks


  • Developer

    @chunter2 said in HostnameChanger question:

    Does the join happen without someone logging into the newly imaged host? I’m assuming it would? And would a logon.cmd script run on the join attempt? I figured it would only run on a user login.

    Absolutely right, the join happens without someone logging into the machine! And logon.cmd shouldn’t cause trouble in that case. Do you have other scripts like machine startup scripts in your AD GPO? Or other special tools or scripts running on bootup?



  • @Sebastian-Roth I read through your reply a few times and I think the settings all makes sense now. The Host Registration one explains why I kept getting “new” MAC addresses for a couple machines even though I would remove them from the pending list. These machines had wifi modules that we don’t use. I also read through the link you posted to the other forum thread about the 1219 error. I’m wondering if I may have something similar in a way but I’m not exactly sure how to test. We have a logon.cmd script that runs to map a bunch of drives for the user logging in. Originally this wasn’t working because of linux file permissions on the logon.cmd file itself. I wonder if when “joining the domain” was working I hadn’t fixed that script yet. The strange thing is if I manually join the domain now and reboot it works fine. I checked and the fog service is set to delayed start like it suggested in that thread but that 1219 error still happens. Does the join happen without someone logging into the newly imaged host? I’m assuming it would? And would a logon.cmd script run on the join attempt? I figured it would only run on a user login.

    Thanks


  • Developer

    @chunter2 said in HostnameChanger question:

    Could you maybe explain the difference in the following settings in fog?

    I will try to. :-)

    Under a hosts Active Directory section what’s “join domain after deploy”? Is that different than what the fog client tries to do?

    This is more or less just the switch to enable AD join. As well there is another feature behind this. When global AD settings are set (FOG Configuration -> FOG Settings -> Active Directory Detfaults) then enabling the checkbox will also populate the default settings for those fields that were empty before. See here: https://wiki.fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting#Syntax

    What does “Name Change/AD Join Forced reboot?” in the Active Directory section do?

    In case a user is logged on the so called HostnameChanger module of the fog-client software won’t do anything unless you have this checkbox enabled. In that case it will still try to do the rename and schedule a reboot within 60 seconds.

    What’s the “Domain Password Legacy” for? Certain types of domains? We’re still running a Samba NT4 domain.

    No, legacy means the old (legacy) fog-client software. Back when this was used the password needed to be stored encrypted using a special tool. This is history - make sure you don’t use the legacy client anymore!

    Under Service Settings for a host, what’s “Host Registration” do?

    Find information on this in the wiki - I am not exactly sure but I think this is still valid: https://wiki.fogproject.org/wiki/index.php/Managing_FOG#Host_Register

    Under Service Settings what’s “Hostname Changer” do? I’m pretty sure this is the one that I’m getting the error message in the fog.log file from.

    Yes, this is the actual module doing the work (check hostname matches the one set for this host in FOG web UI/DB, if not rename, check if should do domain join and try joining).

    As far as I see it all of that has nothing to do with the 1219 error code you got in the fog-client logs. Have you read this whole topic yet? https://forums.fogproject.org/topic/2175/join-domain-error-1219



  • @Sebastian-Roth This may all just be confusion on my part. I’m learning this system that was already set up as I go. One thing I had to do was change the Domain Password from what looked like a guid to the actual password for the join to work from the fog client. I think this had to do with my 1.2.0 to 1.5.6 upgrade.
    This was on the image that “worked”. This different image I just tried has the error message. Could you maybe explain the difference in the following settings in fog?

    Under a hosts Active Directory section what’s “join domain after deploy”? Is that different than what the fog client tries to do?

    What does “Name Change/AD Join Forced reboot?” in the Active Directory section do?

    What’s the “Domain Password Legacy” for? Certain types of domains? We’re still running a Samba NT4 domain.

    Under Service Settings for a host, what’s “Host Registration” do?

    Under Service Settings what’s “Hostname Changer” do? I’m pretty sure this is the one that I’m getting the error message in the fog.log file from.

    Thanks


  • Developer

    @chunter2 The error 1219 literally means that there is a SMB/CIFS connection from this particular client to the same server (where the AD join is supposed to happen) but using different user credentials.

    ERROR_SESSION_CREDENTIAL_CONFLICT
    1219 (0x4C3)
    Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

    https://forums.fogproject.org/topic/2175/join-domain-error-1219

    Do you have some other tool running on your client that might open a SMB/CIFS connection to the server - e.g. to load drivers or something??


Log in to reply
 

541
Online

6.6k
Users

14.0k
Topics

132.4k
Posts