HostnameChanger

[plegrand]

Server

• FOG Version: 1.4.2
• OS: Debian Stable

Client

• Service Version: 0.11.12
• OS: Windows 10

Description

Hello,
i’ve got a question : On a windows 10 computer i’ve got around every minutes this error message : NetJoin event id 4097.
It seeems that it’s corresponding with the fog client which test if computer is already joined to domain : HostnameChanger attempting to join domain.
Is there a way to avoid this ?

Thanks for your help

[Wayne Workman]

We need more information. Please answer the following:

• Is the system already domain joined?
• Is the system configured in FOG to join the domain?
• Are the credentials set in FOG for domain joining correct?
• Do other Windows 10 systems throw this error?
• Do Windows 7 or 8 or 8.1 systems throw this error?
• Can you copy/paste the complete error message from Windows Event viewer please? We don’t want a screen shot, We want text.

[plegrand]

Is the system already domain joined?
Yes

Is the system configured in FOG to join the domain?
Yes

Are the credentials set in FOG for domain joining correct?
Yes

Do other Windows 10 systems throw this error?
Yes

Do Windows 7 or 8 or 8.1 systems throw this error?
Not tested

Can you copy/paste the complete error message from Windows Event viewer please? We don’t want a screen shot, We want text.

Log Fog :

HostnameChanger

 15/06/2017 17:23 Client-Info Client Version: 0.11.12
 15/06/2017 17:23 Client-Info Client OS:      Windows
 15/06/2017 17:23 Client-Info Server Version: 1.4.2
 15/06/2017 17:23 Middleware::Response Success
 15/06/2017 17:23 HostnameChanger Checking Hostname
 15/06/2017 17:23 HostnameChanger Hostname is correct
 15/06/2017 17:23 HostnameChanger Attempting to join domain
 15/06/2017 17:23 HostnameChanger The machine is already joined to the domain, code =  2691

Log WIndows at the same time

Nom du journal :System
Source :       NetJoin
Date :         15/06/2017 17:23:09
ID de l’événement :4097
Catégorie de la tâche :Aucun
Niveau :       Erreur
Mots clés :    
Utilisateur :  Système
Ordinateur :   GEII-102-TMP
Description :
L'ordinateur GEII-102-TMP a essayé de joindre le domaine samba_domain mais a échoué. Le code d'erreur était 2691.
XML de l'événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetJoin" Guid="{9741FD4E-3757-479F-A3C6-FC49F6D5EDD0}" />
    <EventID>4097</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-06-15T15:23:09.251539000Z" />
    <EventRecordID>4521</EventRecordID>
    <Correlation ActivityID="{00000000-0000-0000-0100-000000000000}" />
    <Execution ProcessID="480" ThreadID="1556" />
    <Channel>System</Channel>
    <Computer>GEII-102-TMP</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DomainName">samba_domain</Data>
    <Data Name="ComputerName">GEII-102-TMP</Data>
    <Data Name="NetStatusCode">2691</Data>
  </EventData>
</Event>

2691 This computer is already joined to a domain. NERR_SetupAlreadyJoined

[Sebastian Roth]

@plegrand I don’t know the fog-client stuff well enough but looking at the code it seems like this is intended. Every time the HostnameChanger module is called it checks the hostname and tries to join the domain if hostname is correct.

Though I am not sure how often the HostnameChanger module is meant to be executed. @joe-schmitt or maybe @Tom-Elliott can surely give a better answer to this question.

[Tom Elliott]

@Sebastian-Roth You are correct.

@plegrand It is checking every cycle. This is so that if there is a change it will happen the next time the client runs its checks. Is there some worry in regards to the client performing this every check?

[plegrand]

@Tom-Elliott Not really. It’s only because windows see it as an error

[Sebastian Roth]

@plegrand I just stumbled upon the FOG_ENFORCE_HOST_CHANGES setting in the FOG web UI and remembered your post:

This setting only operates with the new client. Default value is 1 which allows the new client to enforce name changing on every cycle it checks in, so any change on FOG will take place on the next cycle. If unset (value 0) it will only perform hostname change and/or AD Joining on host restart.

You might want to give this a try to get rid of the messages.