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 ...
17th June 2011, 01:16 PM #1
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
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...
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.
IDG Tech News
17th June 2011, 01:28 PM #2
are the machines xp or 7?
what version of fog?
Thanks to bart21 from:
jonny_2010 (4th July 2011)
17th June 2011, 02:00 PM #3
17th June 2011, 02:22 PM #4
You have encrypted the domain password with (iirc) fogcrypt haven't you?
See HostnameChanger Could not find any recognizable digits
17th June 2011, 02:56 PM #5
17th June 2011, 03:05 PM #6
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.
17th June 2011, 03:15 PM #7
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.
17th June 2011, 03:15 PM #8
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.
17th June 2011, 06:12 PM #9
Originally Posted by mats
Yes. not recently. We've been using join domain for years, fine.
17th June 2011, 06:25 PM #10
have you tired adding a computer to the domain with out this fog program ?
5th August 2011, 12:49 AM #11
- Rep Power
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.
5th August 2011, 10:27 AM #12
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.
Originally Posted by EdTheGreek
11th August 2011, 02:13 PM #13
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.
Originally Posted by EdTheGreek
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.
Thanks to ChrisMiles from:
sjatkn (12th August 2011)
11th August 2011, 05:58 PM #14
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.
18th March 2013, 01:15 AM #15
- Rep Power
Originally Posted by Chad
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?
By THERADIOTUBBY in forum Windows Server 2008 R2
Last Post: 2nd July 2010, 09:32 AM
By Matty5225 in forum O/S Deployment
Last Post: 11th June 2010, 06:58 PM
By Gatt in forum MIS Systems
Last Post: 26th May 2010, 10:18 PM
By Nick_Parker in forum Windows 7
Last Post: 24th August 2009, 02:13 PM
By pod in forum Windows Server 2000/2003
Last Post: 14th February 2009, 04:04 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)