+ Post New Thread
Results 1 to 15 of 15
O/S Deployment Thread, unable to join domain with new computers in Technical; For the first time ever we're imaging workstations fully windows-up-to-date, service pack 3. Never had a problem before with domain ...
  1. #1
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40

    unable to join domain with new computers

    For the first time ever we're imaging workstations fully windows-up-to-date, service pack 3. Never had a problem before with domain joining.

    the error in the fog log is
    Code:
     17/06/2011 11:17 FOG::HostnameChanger Hostname is up to date
     17/06/2011 11:17 FOG::HostnameChanger Attempting to join domain if not already a member....
     17/06/2011 11:17 FOG::HostnameChanger netdom output: The system cannot find the file specified.
    
    
    The command failed to complete successfully.
    
    
     17/06/2011 11:18 FOG::DirCleaner Starting directory cleaning process...
    which means....nothing...

    Thing is recently we also upgraded the domain to 2008r2. I would normally have time to test a bunch of things to isolate the problem but I've got a pile of 50 new computers to image and more coming :-S I'm hoping one of you knows what this means and can point me in the right direction. Thanks.

  2. #2
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    404
    Thank Post
    77
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    are the machines xp or 7?

    what version of fog?

    nick

  3. Thanks to bart21 from:

    jonny_2010 (4th July 2011)

  4. #3
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40
    They're XP

  5. #4

    Join Date
    Nov 2010
    Posts
    433
    Thank Post
    58
    Thanked 66 Times in 57 Posts
    Rep Power
    27
    You have encrypted the domain password with (iirc) fogcrypt haven't you?

    See HostnameChanger Could not find any recognizable digits

  6. #5
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    404
    Thank Post
    77
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    what version of fog?

  7. #6
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    816
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    39
    If you set the 'AD joining' username by setting it through a FOG group then there is a bug which will remove the backslash, that might be worth checking. Are you adding these via a PXE boot or are you creating the host defintions yourself? Also the last few releases of FOG don't use netdom so if you think you have the newest one then something is amiss.

  8. #7

    bladedanny's Avatar
    Join Date
    May 2009
    Location
    Sheffield
    Posts
    1,268
    Thank Post
    188
    Thanked 298 Times in 224 Posts
    Rep Power
    130
    I've had problems in the past when setting the OU for them to go into. Leaving it blank has worked for me. May or may not affect you but is something to check.

  9. #8
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    404
    Thank Post
    77
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    if it is fog version .28 or below you will need netdom installed as part of support tools, what version of fog are you using?

    as @morganw says, if you are using .29 or .30 in the ad username box there needs to be domain\username. if when entering this slash it gets turned into a double slash then you need to turn magic quotes off in php.ini and restart apache.

    nick

  10. #9
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40
    Quote Originally Posted by mats View Post
    You have encrypted the domain password with (iirc) fogcrypt haven't you?

    See HostnameChanger Could not find any recognizable digits

    Yes. not recently. We've been using join domain for years, fine.

  11. #10
    kevin_lane's Avatar
    Join Date
    Mar 2007
    Location
    Derby
    Posts
    505
    Thank Post
    23
    Thanked 20 Times in 20 Posts
    Blog Entries
    5
    Rep Power
    19
    have you tired adding a computer to the domain with out this fog program ?

  12. #11

    Join Date
    Feb 2007
    Posts
    6
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Does the computer you have imaged have .NET Framework 4 Full (ie Client Profile & Extended) installed? We are having problems with computers renaming and joining the domain at the moment and it seems to stop working when we install .net 4. The computers will rename and join the domain only when you restart the Fog service which is obviously a bit of a pain.

  13. #12
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    816
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    39
    Quote Originally Posted by EdTheGreek View Post
    Does the computer you have imaged have .NET Framework 4 Full (ie Client Profile & Extended) installed? We are having problems with computers renaming and joining the domain at the moment and it seems to stop working when we install .net 4. The computers will rename and join the domain only when you restart the Fog service which is obviously a bit of a pain.
    I've also has this happen when .NET Framework 4 was already installed, sometimes it would work properly but most of the time it wouldn't. I guess you could install it as a snap-in afterwards but it takes about 15 minutes to install. The latest version of FOG should open your sysprep.inf file from the init system and rewrite the hostname. You can then use sysprep to join the domain and the host rename and domain join functions of the FOG service should be redundant.

  14. #13

    Join Date
    Mar 2011
    Location
    Bournemouth
    Posts
    280
    Thank Post
    16
    Thanked 74 Times in 64 Posts
    Rep Power
    21
    Quote Originally Posted by EdTheGreek View Post
    Does the computer you have imaged have .NET Framework 4 Full (ie Client Profile & Extended) installed? We are having problems with computers renaming and joining the domain at the moment and it seems to stop working when we install .net 4. The computers will rename and join the domain only when you restart the Fog service which is obviously a bit of a pain.
    We had this exact same problem with the fog service. Its a timing issue of some kind. My investigations showed that the fog service started before the network was fully up for some reason and this caused it to not function correctly.

    In the end I fixed it by changing the fog service to Automatic (Delayed) which delays the start of the service by approx 2 mins.

  15. Thanks to ChrisMiles from:

    sjatkn (11th August 2011)

  16. #14
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    18
    We have .net 1.1, 2.0, 3.0, 3.5 and 4 on our image and I've not had any problems in joining the domain (FOG v0.31)

    I've recently patched FOG with a mod from the site which modifies the sysprep file immediately after imaging. This populates the correct hostname and the domain join instructions in the sysprep file, which means that the PC has the correct name and joins the domain without the need for the usual additional 2 reboots.

    As a start, I would try updating the FOG client on your image, as it looks like you're using an old (netdom required) version. Note that the client auto-register was removed about the same time as the dependency on netdom, so be bear this in mind if you need this feature.

  17. #15

    Join Date
    Jul 2012
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by Chad View Post
    I've recently patched FOG with a mod from the site which modifies the sysprep file immediately after imaging. This populates the correct hostname and the domain join instructions in the sysprep file, which means that the PC has the correct name and joins the domain without the need for the usual additional 2 reboots.

    I have started to run into some problems recently after we started sysprepping our images. After deploying the image the machines aren't joining the domain. Not sure if it is a sysprep issue or a Fog one, but I noticed you mentioned being able to patch FOG with a mod to write the computer name and domain join info directly into the sysprep files. Do you still have a copy of this mod or know where I can find it?

SHARE:
+ Post New Thread

Similar Threads

  1. Script to join new domain
    By THERADIOTUBBY in forum Windows Server 2008 R2
    Replies: 4
    Last Post: 2nd July 2010, 08:32 AM
  2. FOG 0.29 AD join domain error
    By Matty5225 in forum O/S Deployment
    Replies: 4
    Last Post: 11th June 2010, 05:58 PM
  3. [SIMS] Join server to new domain
    By Gatt in forum MIS Systems
    Replies: 6
    Last Post: 26th May 2010, 09:18 PM
  4. No Domain Join during Setup
    By Nick_Parker in forum Windows 7
    Replies: 19
    Last Post: 24th August 2009, 01:13 PM
  5. Cannot join domain, dns problems
    By pod in forum Windows Server 2000/2003
    Replies: 0
    Last Post: 14th February 2009, 03:04 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •