6 Replies Latest reply on Jul 7, 2011 10:38 PM by Andy_M220

    Windows 7: unable to join the domain

    Rookie

      Hello,

       

      Using Landesk 9 SP1, we try for several days now to configure our Landesk OS deployment tool to join our domain.

      We have found a few articles describing what to do, but nothing seems to work. Here is the what we have last tested:

       

      1- Install Windows 7 on a PC, configure it with the options we want, install the windows 7 patches, updates, etc.

      2- Sysprep the PC with the command "sysprep /audit /shutdown". I have read in an article that we should proceed that way

      3- Create the OSD object in the Landesk Management Console

      4- Edit the associated xml file and verify/modify the sysprep command inside it: "c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /reboot"

       

      We have used several administrative accounts for the join process but nothing happens: the PC still remains in the workgroup.

       

      It's the really last thing that does not work, so we would be very happy to solve the problem.

       

      What have we missed ?

       

      Kind regards

      Nicolas

        • 2. Re: Windows 7: unable to join the domain
          Rookie

          Hello,

           

          I thought the Patch was already integrated in the SP1. But I installed it this morning and tried it once again, with the same bad result.

          We did following, perhaps will you point out the error:

           

          - Install Windows 7 from the DVD

          - sysprep /audit

          - after the restart we ignored and closed the window with "oobe", and shutdown the PC

          - capture the image with image w2

          - create the OSD object in the Landesk Management Console and verified the xml file: here is the xml file...

           

          --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

          <?xml version="1.0" encoding="utf-8"?>
          <unattend>
            <settings pass="auditSystem">
              <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
                <DriverPaths>
                  <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\windows\LDDriverStore</Path>
                  </PathAndCredentials>
                </DriverPaths>
              </component>
              <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                <UserAccounts>
                  <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>xxxxxxx</Value>
                  </AdministratorPassword>
                </UserAccounts>
                <AutoLogon>
                  <Enabled>true</Enabled>
                  <Username>Administrator</Username>
                  <Password>
                    <PlainText>true</PlainText>
                    <Value>xxxxxxxx</Value>
                  </Password>
                  <LogonCount>1</LogonCount>
                </AutoLogon>
              </component>
            </settings>
            <settings pass="auditUser">
              <component name="Microsoft-Windows-Deployment" 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">
                <RunSynchronous>
                  <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>c:\windows\System32\sysprep\sysprep.exe /oobe /generalize /reboot </Path>
                  </RunSynchronousCommand>
                </RunSynchronous>
              </component>
            </settings>
            <settings pass="generalize">
              <component name="Microsoft-Windows-PnpSysprep" 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">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
              </component>
            </settings>
            <settings pass="oobeSystem">
              <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                <OOBE>
                  <HideEULAPage>true</HideEULAPage>
                  <ProtectYourPC>1</ProtectYourPC>
                  <SkipMachineOOBE>true</SkipMachineOOBE>
                  <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxxx</ProductKey>
                <RegisteredOwner>Regent</RegisteredOwner>
                <RegisteredOrganization>Regent AG</RegisteredOrganization>
                <TimeZone>(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna</TimeZone>
                <UserAccounts>
                  <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>xxxxxx</Value>
                  </AdministratorPassword>
                </UserAccounts>
                <AutoLogon>
                  <Enabled>true</Enabled>
                  <Username>Administrator</Username>
                  <Password>
                    <PlainText>true</PlainText>
                    <Value>xxxxxxxx</Value>
                  </Password>
                  <LogonCount>1</LogonCount>
                </AutoLogon>
                <FirstLogonCommands>
                  <SynchronousCommand>
                    <CommandLine>c:\ldsleep.exe 30</CommandLine>
                    <Description></Description>
                    <Order>1</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>cmd /q /c del /q c:\ldsleep.exe</CommandLine>
                    <Description></Description>
                    <Order>2</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>cmd /q /c del /q c:\unattend.xml</CommandLine>
                    <Description></Description>
                    <Order>3</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>net use \\rbs-w14\ldlogon xxxxxxxxx /u:regent\landeskosd</CommandLine>
                    <Description></Description>
                    <Order>4</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>cmd /q /c \\rbs-w14\ldlogon\wscfg32.exe /F /L /STATUS /NOREBOOT</CommandLine>
                    <Description></Description>
                    <Order>5</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>net use \\rbs-w14\ldlogon /d /y</CommandLine>
                    <Description></Description>
                    <Order>6</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>cmd /q /c del /q c:\ldiscan.cfg</CommandLine>
                    <Description></Description>
                    <Order>7</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>cmd /q /c c:\windows\regedit.exe /s \\regent.local\ldlogon\landesk.reg</CommandLine>
                    <Description></Description>
                    <Order>8</Order>
                  </SynchronousCommand>
                  <SynchronousCommand>
                    <CommandLine>cmd /q /c c:\windows\system32\shutdown.exe -r -f -t 120</CommandLine>
                    <Description></Description>
                    <Order>9</Order>
                  </SynchronousCommand>
                </FirstLogonCommands>
              </component>
            </settings>
            <settings pass="specialize">
              <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                <ComputerName>%COMPUTERNAME%</ComputerName>
              </component>
              <component name="Microsoft-Windows-UnattendedJoin" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                <Identification>
                  <Credentials>
                    <Domain>regent.local</Domain>
                    <Username>regent\landeskosd</Username>
                    <Password>xxxxxx</Password>
                  </Credentials>
                  <JoinDomain>regent.local</JoinDomain>
                </Identification>
              </component>
            </settings>
          </unattend>

          ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

          We saw when deploying the image that sysprep was used with the options /generalize /oobe /reboot as mentionned in the xml file but

          the join to domain did not work or take place...

           

          Is there a log file that we could read to find out what happens during the deployment ?

          Or have you already the solution to our problem after reading what we did and consult the xml file ?

           

          Thanks for your reply

          Nicolas

          • 3. Re: Windows 7: unable to join the domain
            Expert

            FYI, your product key is listed. You may want to edit this to remove anything private.

            • 4. Re: Windows 7: unable to join the domain
              Rookie

              Thanks, was in a hurry this morning when sending the message....

              Should have cleaned every password, key-code and so...

              • 5. Re: Windows 7: unable to join the domain
                Rookie

                The solution for us has been to use a powershell script and the "add-computer" command.

                 

                Now it works... we did the same in XP with the netdom command, that does not work anymore...

                • 6. Re: Windows 7: unable to join the domain
                  Rookie

                  Where did you inject the script? I tried using the powershell scipt in the Run Once command box of the OSD script and it doesn't work.

                   

                  $username = “COATES\IA_Landesk”

                  $password = ConvertTo-SecureString “*********” -AsPlainText -Force

                  $myCred = New-Object System.Management.Automation.PSCredential $username, $password

                  Add-Computer -DomainName COATES -Credential $mycred

                   

                  I am resorting to scripts to have the machines join the domain as nothing else is working. Patches and the OSD script itself does not work. If anyone can help it will be greatly appreciated.