9 Replies Latest reply on Apr 11, 2013 6:48 PM by Laszlo

    Not Joining Domain


      I am using landesk 9.5  I have read through the forums and have seen this problem in the past, however all responses were from 2010 and pointing towards a patch. I have stopped the firewall on the source image, there is no MPS process running in the services.  When syspreping, I am Choosing, Audit mode, with NO Generalize clicked and shutdown. When I deploy my image everythign works great except that it it either 1) doesn't join the domain, or 2) is unjoining at the end.  I can't figure out how to tell the difference.  My image loads, the accounts log in fine (I've verified those independently) and LD client loads from the server with out fail.  However, when it's all said and done, it's in a workgroup and I get that network selection dialogue box.  Below is the XML (with PW"s removed)





        • 1. Re: Not Joining Domain
          Frank Wils ITSMMVPGroup

          You have the section to join the domain a bit wrong:



          You already specify Domain in the line above it. When trying to join the domain it will try now with the user NCE\NCE\Sysprep


          Remove NCE\ from the username and it will work a lot better.




          1 of 1 people found this helpful
          • 2. Re: Not Joining Domain

            I'm certain the response above had something to do with my problem, but the condition persist.  When I load an image created by a former admin here with using my deployment script, it works excellent!  When I try and load any other image, it doesn't.  I've double checked the firewall service but alas, nothing works!  I can get all teh way to the end, the Workgroup carries the Domain name and that is what joins, the workgroup.   Everything else works great!  I just can't get it to stay on the domain?


            Is there something more in the windows load you have to do in order to get it to work correctly? (besides shut down the firewall)?

            • 3. Re: Not Joining Domain
              MrGadget Expert

              I would like to ask, are you saying you deploy a image made by a former admin using your osd script AND your answer file and it works?

              If this is the case then it points to your answer file and osd script being good. However if the image is a .TBI use TBIVIEW and see if there is a answer file in the windows\panther or windows\system32\sysprep folder or windows\system32\sysprep\panther folder. It could be running that and not your answer file.

              • 4. Re: Not Joining Domain

                Using LD 9.5 am I to capture the image using Audit (no Generalize) or am I to use OOBE with Generalize?    I referenced an older doc that said to use Audit and No Generalize.

                • 5. Re: Not Joining Domain
                  MrGadget Expert

                  We tryed using Audit and had problems with drivers not being installed on the deploy side. We are using OOBE with generalize on the capture side.

                  We are using LD 9.5

                  • 6. Re: Not Joining Domain

                    I use ODBE with Generalize and I didn't have any problems joining it to the domain until I used the option to move the computer into a specific OU in AD. If you are using that option then you may want to first try it without. I am currently trying to figure out how to get that working.

                    • 7. Re: Not Joining Domain
                      marcel Specialist



                      Using Full-Qualified-Domain-Name can help too:



                      • 8. Re: Not Joining Domain
                        Frank Wils ITSMMVPGroup

                        Also check the netsetup.log in Windows 7 (c:\windows\debug), it should give you an error as to why the join domain fails.




                        • 9. Re: Not Joining Domain
                          Laszlo Apprentice

                          Saw simaler thread..... Here is the section we use. The catch is that if you do not supply a MachineObject domain join will attempt to in default Computer OU. Which begs the question. Does your account have access to that OU?


                                  <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">