Fog Domain join issues



  • Hello all,

    I have recently run into serious issues getting fog service to rename/join my domain.

    I have tried everything I can think of to fix it… Reinstalled fog service, rebuilt my images, checked all settings in fog including my credentials and host settings, ect. I am beginning to believe it may be related to my domain controller/DNS but I cant be sure. This is a newly updated fog server to 1.0.1 and I have never had issues with fog service before. One thing that is relatively new is that I have started sysprepping. Hoping for some advice. It appears to change the NetBIOS name but not the actual host name (see image). It also see’s the username as the host it should have changed the name to, but the actual host name remains unchanged.

    The hostname of my image (which should be changed to the hostname listed in fog) is CHSCLASSHHE8Q8
    The hostname of THIS host that was imaged (which is not being properly renamed) is CHSCLASSHHE93S

    Here is some gathered information:

    6/3/2014 2:16 PM FOG::DirCleaner Attempting to connect to fog server…
    6/3/2014 2:16 PM FOG::DirCleaner Module is disabled on this host.
    6/3/2014 2:16 PM FOG::GreenFog Starting green fog…
    6/3/2014 2:16 PM FOG::GreenFog Attempting to connect to fog server…
    6/3/2014 2:16 PM FOG::GreenFog Module is active…
    6/3/2014 2:16 PM FOG::GreenFog No actions were found.
    6/3/2014 2:16 PM FOG::GreenFog No tasks found after validation!
    6/3/2014 2:17 PM FOG::MODDebug Reading config settings…
    6/3/2014 2:17 PM FOG::MODDebug Reading of config settings passed.
    6/3/2014 2:17 PM FOG::MODDebug Starting Core processing…
    6/3/2014 2:17 PM FOG::MODDebug Operating System ID: 6
    6/3/2014 2:17 PM FOG::MODDebug Operating System Minor: 2
    6/3/2014 2:17 PM FOG::MODDebug MAC ID 0 00:24:81:98:19:04
    6/3/2014 2:17 PM FOG::MODDebug MAC POST String: 00:24:81:98:19:04
    6/3/2014 2:17 PM FOG::MODDebug A user is currently logged in
    6/3/2014 2:17 PM FOG::MODDebug Username: [B]CHSCLASSHHE93S\RRPSadmin[/B]
    6/3/2014 2:17 PM FOG::MODDebug Hostname: [B]CHSCLASSHHE93S[/B]
    6/3/2014 2:17 PM FOG::MODDebug Attempting to open connect to: [url]http://10.64.100.64/fog/service/debug.php[/url]
    6/3/2014 2:17 PM FOG::MODDebug Server responded with: Hello FOG Client
    6/3/2014 2:17 PM FOG::MODDebug Module has finished work and will now exit.
    6/3/2014 2:18 PM Service Stop requested
    6/3/2014 2:18 PM FOG::AutoLogOut Shutdown complete
    6/3/2014 2:18 PM FOG::ClientUpdater Shutdown complete
    6/3/2014 2:18 PM FOG::DirCleaner Shutdown complete
    6/3/2014 2:18 PM FOG::DisplayManager Shutdown complete
    6/3/2014 2:18 PM FOG::GreenFog Shutdown complete
    6/3/2014 2:18 PM FOG::GUIWatcher Stopping…
    6/3/2014 2:18 PM FOG::HostnameChanger Shutdown complete
    6/3/2014 2:18 PM FOG::HostRegister Shutdown complete
    6/3/2014 2:18 PM FOG::MODDebug Shutdown complete
    6/3/2014 2:18 PM FOG::PrinterManager Shuting down
    6/3/2014 2:18 PM FOG::SnapinClient Shutdown complete
    6/3/2014 2:18 PM FOG::TaskReboot Stopping…
    6/3/2014 2:18 PM FOG::UserCleanup Shutdown complete
    6/3/2014 2:18 PM FOG::UserTracker Shutdown complete
    6/3/2014 2:18 PM FOG Service Engine Version: 3
    6/3/2014 2:18 PM Starting all sub processes
    6/3/2014 2:18 PM 14 modules loaded
    6/3/2014 2:18 PM * Starting FOG.AutoLogOut
    6/3/2014 2:18 PM * Starting FOG.SnapinClient
    6/3/2014 2:18 PM FOG::AutoLogOut Starting process…
    6/3/2014 2:18 PM FOG::ClientUpdater Starting client update process…
    6/3/2014 2:18 PM FOG::ClientUpdater Sleeping for 224 seconds.
    6/3/2014 2:18 PM * Starting FOG.DirCleaner
    6/3/2014 2:18 PM * Starting FOG.DisplayManager
    6/3/2014 2:18 PM FOG::DirCleaner Sleeping for 36 seconds.
    6/3/2014 2:18 PM * Starting FOG.GreenFog
    6/3/2014 2:18 PM FOG::DisplayManager Starting display manager process…
    6/3/2014 2:18 PM * Starting FOG.GUIWatcher
    6/3/2014 2:18 PM FOG::GUIWatcher Starting GUI Watcher…
    6/3/2014 2:18 PM * Starting FOG.HostNameChanger
    6/3/2014 2:18 PM FOG::GreenFog Sleeping for 47 seconds.
    6/3/2014 2:18 PM * Starting FOG.HostRegister
    6/3/2014 2:18 PM FOG::HostnameChanger Starting hostname change process…
    6/3/2014 2:18 PM FOG::HostRegister Starting host registration process…
    6/3/2014 2:18 PM FOG::HostnameChanger Yielding to other subservices for 9 seconds.
    6/3/2014 2:18 PM * Starting FOG.MODDebug
    6/3/2014 2:18 PM * Starting FOG.PrinterManager
    6/3/2014 2:18 PM FOG::MODDebug Start Called
    6/3/2014 2:18 PM FOG::MODDebug Sleeping for 100 Seconds
    6/3/2014 2:18 PM * Starting FOG.SnapinClient
    6/3/2014 2:18 PM FOG::PrinterManager Starting interprocess communication process…
    6/3/2014 2:18 PM * Starting FOG.TaskReboot
    6/3/2014 2:18 PM FOG::TaskReboot Taskreboot in lazy mode.
    6/3/2014 2:18 PM FOG::TaskReboot Starting Task Reboot…
    6/3/2014 2:18 PM FOG::SnapinClient Starting snapin client process…
    6/3/2014 2:18 PM FOG::PrinterManager interprocess comm startup: OK
    6/3/2014 2:18 PM * Starting FOG.UserCleanup
    6/3/2014 2:18 PM * Starting FOG.UserTracker
    6/3/2014 2:18 PM FOG::UserCleanup Sleeping for 13 seconds.
    6/3/2014 2:18 PM FOG::UserTracker Starting user tracking process…
    6/3/2014 2:18 PM FOG::SnapinClient Sleeping for 421 seconds.
    6/3/2014 2:18 PM FOG::HostRegister Exiting because only 1 mac address was found.
    6/3/2014 2:18 PM FOG::DisplayManager Attempting to connect to fog server…
    6/3/2014 2:18 PM FOG::PrinterManager Attempting to connect to fog server…
    6/3/2014 2:18 PM FOG::UserTracker Attempting to connect to fog server…
    6/3/2014 2:18 PM FOG::DisplayManager Module is disabled globally on the FOG Server.
    6/3/2014 2:18 PM FOG::AutoLogOut Module is active…
    6/3/2014 2:18 PM FOG::PrinterManager Module is active…
    6/3/2014 2:18 PM FOG::PrinterManager Starting printer manager…
    6/3/2014 2:18 PM FOG::PrinterManager Yielding to other services for 34 seconds.
    6/3/2014 2:18 PM FOG::UserTracker Module is active…
    6/3/2014 2:18 PM FOG::AutoLogOut Timeout value is Zero, disabling module.
    6/3/2014 2:18 PM FOG::AutoLogOut c:\program files\fog\images\alo-bg.jpg
    6/3/2014 2:18 PM FOG::AutoLogOut at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
    at FOG.AutoLogOut.doWork()
    6/3/2014 2:19 PM FOG::HostnameChanger Attempting to connect to fog server…
    6/3/2014 2:19 PM FOG::HostnameChanger Module is active…
    6/3/2014 2:19 PM FOG::HostnameChanger AD mode requested, confirming settings.
    6/3/2014 2:19 PM FOG::HostnameChanger Hostname is up to date
    6/3/2014 2:19 PM FOG::HostnameChanger Attempting to join domain if not already a member…
    6/3/2014 2:19 PM FOG::UserCleanup Starting user cleanup process…
    6/3/2014 2:19 PM FOG::UserCleanup Attempting to connect to fog server…
    6/3/2014 2:19 PM FOG::UserCleanup Module is disabled globally on the FOG Server, exiting.
    [B][COLOR=#000000] 6/3/2014 2:19 PM FOG::HostnameChanger Domain Error! (‘Unknown Error’ Code: 2725) [/COLOR][/B]
    6/3/2014 2:19 PM FOG::PrinterManager Management level = 0
    6/3/2014 2:19 PM FOG::PrinterManager This host is set to NO MANAGEMENT, we will exit now.
    6/3/2014 2:19 PM FOG::PrinterManager Major printing operations complete, moving to tracking mode.
    6/3/2014 2:19 PM FOG::DirCleaner Starting directory cleaning process…
    6/3/2014 2:19 PM FOG::DirCleaner Attempting to connect to fog server…
    6/3/2014 2:19 PM FOG::DirCleaner Module is disabled on this host.
    6/3/2014 2:19 PM FOG::PrinterManager New user detected: [B]CHSCLASSHHE93S\RRPSadmin[/B]
    6/3/2014 2:19 PM FOG::PrinterManager Waiting for tray to load…
    6/3/2014 2:19 PM FOG::GreenFog Starting green fog…
    6/3/2014 2:19 PM FOG::GreenFog Attempting to connect to fog server…
    6/3/2014 2:19 PM FOG::GreenFog Module is active…
    6/3/2014 2:19 PM FOG::GreenFog No actions were found.
    6/3/2014 2:19 PM FOG::GreenFog No tasks found after validation!
    6/3/2014 2:20 PM FOG::MODDebug Reading config settings…
    6/3/2014 2:20 PM FOG::MODDebug Reading of config settings passed.
    6/3/2014 2:20 PM FOG::MODDebug Starting Core processing…
    6/3/2014 2:20 PM FOG::MODDebug Operating System ID: 6
    6/3/2014 2:20 PM FOG::MODDebug Operating System Minor: 2
    6/3/2014 2:20 PM FOG::MODDebug MAC ID 0 00:24:81:98:19:04
    6/3/2014 2:20 PM FOG::MODDebug MAC POST String: 00:24:81:98:19:04
    6/3/2014 2:20 PM FOG::MODDebug A user is currently logged in
    6/3/2014 2:20 PM FOG::MODDebug Username: [B]CHSCLASSHHE93S\RRPSadmin[/B]
    6/3/2014 2:20 PM FOG::MODDebug Hostname: [B]CHSCLASSHHE93S[/B]
    6/3/2014 2:20 PM FOG::MODDebug Attempting to open connect to: [url]http://10.64.100.64/fog/service/debug.php[/url]
    6/3/2014 2:20 PM FOG::MODDebug Server responded with: Hello FOG Client
    6/3/2014 2:20 PM FOG::MODDebug Module has finished work and will now exit.
    6/3/2014 2:22 PM FOG::ClientUpdater Attempting to connect to fog server…
    6/3/2014 2:22 PM FOG::ClientUpdater Module is active…

    When I try to MANUALLY add this computer the domain after fog is unsuccessful in doing so, I get this error:
    This only happens after I image with fog, I can add other machines to my domain manually with no issues.
    [ATTACH=full]895[/ATTACH]
    [ATTACH=full]896[/ATTACH]

    [url="/_imported_xf_attachments/0/895_domain join error.PNG?:"]domain join error.PNG[/url][url="/_imported_xf_attachments/0/896_netbios.PNG?:"]netbios.PNG[/url]


  • Senior Developer

    [quote=“Dave Bagwell, post: 29466, member: 5315”]That is what I was trying to say, I removed the domain name from the username and the domain “.com” from the domain name under AD setting.

    Thanks again[/quote]

    No problem, but you shouldn’t (necessarily) need to remove the .com part of the domain. If the base image is already attached to the domain, changing the domain name field would help.



  • That is what I was trying to say, I removed the domain name from the username and the domain “.com” from the domain name under AD setting.

    Thanks again


  • Senior Developer

    [quote=“Dave Bagwell, post: 29462, member: 5315”]I’m not sure if i’m in the right place but anyway. I was having trouble after I upgraded to Fog 1.1. The Windows 7 64 images would join the domain. I messed around with some setting but still didn’t work. I changed the domain name from local.local to local and the user name from local\username to username and it joined without issue. Sorry if i’m not in the correct place.

    Thanks for everything you have given us with the Fog project[/quote]

    Take the “domain” part out of the username entirely or you could have issues down the road.



  • I’m not sure if i’m in the right place but anyway. I was having trouble after I upgraded to Fog 1.1. The Windows 7 64 images would join the domain. I messed around with some setting but still didn’t work. I changed the domain name from local.local to local and the user name from local\username to username and it joined without issue. Sorry if i’m not in the correct place.

    Thanks for everything you have given us with the Fog project



  • My real goal with sysprepping was to have an image that is capable of being deployed to multiple computer models. What I was hoping to do (and maybe this is a flawed thought process) was to have an image that is sysprepped (to remove hardware unique drivers, add in activation keys, ect) so I could deploy it to the 20 different computer models I have. Then for each model I intended to install any missing/needed drivers and upload an image to fog for that model with drivers in-tact so when I deploy it, it is ready to go without being touched. Then I would end up with the following:

    1. “golden” sysprepped image that I can use for all computer models - current and future (always have an image ready)
    2. A “complete package” image (not sysprepped) for each model of computer I have (HP Elitebook 8440, HP Compaq DC7900, HP Elitebook 850, ect) this also allows me to have unique software added to these images so they are customized for the location (some software on these is as big as 50GB and does not work for group policy or snap-ins).

    So really i’m not deploying sysprep to install drivers, in fact i’m doing quite the opposite. Really all the sysprepped image is for is to prevent having to pop a windows 8 disc into every model of computer and build an image from scratch. It gives me a good base that only needs drivers and miscellaneous software.

    Does this sound like a reasonable approach, or am I going about this all wrong?


  • Developer

    [quote=“Dekar, post: 29363, member: 19775”]After some more tinkering I seem to have a little more information that might help to narrow this down.

    1. After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
    2. If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
    3. I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)

    Hopefully this helps to narrow the problem down. I’ll continue to look into it.

    Thanks[/quote]

    That’s probably because after the sysprep process occurs, it intends to stay with that machine and those hardware unique identifiers, the purpose of the sysprep is to generalize the installation so it can be prepared for a new machine with different hardware unique identifiers. Yes also put it in an out of the box state and that is where Unattend files come in handy to get your installation back to how you intend the end user to see it.

    I’m willing to bet that if you install the base windows 8 image and don’t sysprep you may run into the same issue. If not, it could be one of the drivers or programs you are installing after the sysprep process and before uploading again. Before you try to narrow down a problem driver, I have another solution, read on.

    To join a machine to an active directory domain, it likes things to be unique.

    I’m willing to bet that if you ran the sysprep process on image listed in step 2, and then push, you might see success in deploying and joining to a domain again.

    Sysprep doesn’t REMOVE drivers, it just freshens the install so it is acceptable to drivers again so if you move it to a new hardware it is less likely to have problems, provided that windows is still able to supplement a driver for its use. So deploying the sysprepped image to install drivers is actually a wasted process. I set up a path variable for C:\Drivers and pack all my driver files and install files there so when Windows looks for drivers, BAM it find the right ones, if not I install them manually after installation (this is a specific and quirky model and there are few of them so I don’t waste my time to fix the driver in the folder… possibly laziness.)


  • Senior Developer

    [quote=“Dekar, post: 29363, member: 19775”]After some more tinkering I seem to have a little more information that might help to narrow this down.

    1. After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
    2. If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
    3. I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)

    Hopefully this helps to narrow the problem down. I’ll continue to look into it.

    Thanks[/quote]

    That would make a LOT of sense. Probably why I can’t replicate as I didn’t think to “sysprep” and test.



  • After some more tinkering I seem to have a little more information that might help to narrow this down.

    1. After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
    2. If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
    3. I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)

    Hopefully this helps to narrow the problem down. I’ll continue to look into it.

    Thanks



  • I have tried it both with the domain name and without the domain name with the same result. Currently I have removed the domain name and am just using the username. I will keep troubleshooting and let you know if I come up with anything.

    Thanks for the reply!!


  • Senior Developer

    I’m aware of some issues with Windows 8 and hostname changer, though all tests I’ve been able to perform say it works. Other’s seem to only change the netbios name. I don’t know why this is. I can’t narrow it down either.

    That all said,

    As super chicken states, are you sending the domain name with the username? I’ve made it so you don’t have to do this anymore. This shouldn’t have any effect on hostname changing, but as I said, I don’t see the issue on Windows 8 as others are.



  • A common problem I see people having when moving to 1.0.1 from an earlier version is the username no longer needs the domain prefix. Try checking your AD settings for the host and verify that it shows just the username and domain in the respective fields.


Log in to reply
 

453
Online

38940
Users

10697
Topics

101497
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.